This article could have been born about a year ago – that's when the PVS-Studio team decided to try agile. However, we wanted to experience it hands-on before we told the world about it. Aside from introducing agile, we decided to switch from Bitbucket to a new task tracker. We also wanted to upgrade many of our internal development processes. No time for an article!
Flexible development methodology
We work using Agile: Scrum, or Kanban, or any other extended project management way. Agile appeared in 2001 as a result of a long discussion between really smart guys. They just formed best practices of management into the shape of short documents - the Agile Manifesto. But what did they want to replace by the Agile way? Most of you may say that they wanted the Waterfall to go to the past. But what would you think if I tell you that the “classical” Waterfall had been a really rare thing even for those days?
Indeed, there were times when everything around scrum was innovative, valuable and efficient: from planning to sprints and so on.
However, recently the number of negative reviews has been escalating.
Ten years ago, a young project manager had a successful experience in implementing something similar to Scrum in one of the insurance companies. There is more than enough enthusiasm. Colleagues from the tech department strongly supported me. The developer's background was helpful too. But at some point, an impenetrable wall appeared: the Agile approach worked inside IT, but it did not work outside. It needed synchronization with other departments and a change in the way the company worked. A full transition did not happen, but a year ago, it was possible to implement Agile transformation on another project in a financial organization with more than 100 people. Is this possible?
My name is Anna and I work for an American company Scentbird NY as a product designer. Prior to that I was involved in developing flagship products in Alfa-Bank design team.
I was probably born under a lucky star but all my life I've been working with the developers who suggest the best product solutions, better than a lot of product managers and product owners. But anyway, my observation is that the earlier you involve developers into working on a particular task, the better off you are.
What you are about to read is actually a blueprint on how to conduct brainstorm sessions and generate not-so-obvious yet effective solutions, which are apparently really easy to reach and not that time-consuming.
There is no need for detailed analytics to understand that Scrum continues to grow in popularity just because of its many benefits and general effectiveness. And the important merit in this belongs to a Scrum Master. In this post, we extol and praise the role of a Scrum Master, without which no Scrum project succeeds.
Today this iterative or incremental method affects various aspects of development and business including project management. What are the best sources to learn Agile? This post covers 10 powerful books that may enhance the skills of project managers and their teams.
In this post, you will learn some basic facts about Scrumban and how to combine two popular Agile methodologies – Kanban and Scrum to make this hybrid approach perform better.
Scrum strongly enforces the goals and time boxes for everything, including the ceremonies. This post covers these outstanding events and identifies the goals for each as well as their necessity. Take 7-8 minutes to figure them out.
In Agile software development, this choice is also challenging, especially if it's about Scrum and Kanban.
A powerful Kanban board is the solution. This excellent project collaboration tool is widely used in software development, digital marketing, construction, innovative solutions and among other cases where there is a steady workflow of tasks. The Kanban approach helps teams to visualize workflow, analyze processes and achieve greater task management efficiencies. In this post, we describe 14 Kanban tools with advanced features. Compare them and choose the best one right for your needs!
What are these powerful practices that make Agile popular and trendy? Here we share the list that is definitely incomplete but foundational.
People go mad about Scrum: many IT blogs write about it, many practical courses promise to teach all Scrum features, many companies want to see a working experience with Scrum in CVs, and so on. Scrum conquers them all. In this post, we define why.
* This heavyweight construct “The work plan of IT teams for the next 3 months” threatens to increase the size of the text significantly, so hereinafter I’m going to replace it with “the commitment”. Accordingly, to draw up and adopt a work plan will be “to commit”.
Why do we need this?
1) Fatigue with analog methods of work. While spaceships are plowing the Space, and Elon Musk is boring his tunnels, we, the IT guys, have been persistently writing with highlighters on sticky notes sticking them on the boards — there is really some kind of dissonance in this, isn’t there? That’s what our commitment looked like a while ago:
Иногда молодые команды разработки охватывает неразбериха.
Это случается в тот момент, когда они ещё не до конца разобрались, что такое эджайл; проджект и продакт спорят, кто из них кто, а задачи каждый ведёт сам по себе. Или все уже всё знают, но планировать спринты не получается — задачи не прорабатываются, демо и ретро проходят нерегулярно.
У нас тоже была похожая история, но мы нашли свой путь.
Это рассказ от команды личного кабинета Яндекс.Кассы, и подробнейшая инструкция для тех, кто хочет улучшить своё планирование.