"In any team of developers there are testers and devops," - with such a start, anyone would like to feel an urgent need to hang their nose from sadness. Do not give in to provocations, do not believe slides from megastars. In any critical situation, the source of the truth is this post.
Lovers from all over the country gathered to introduce the Ajile, and then the Kanban; in kitchens they usually share sacred knowledge in the evenings. You have already guessed, probably, what is all this text to Kata. Yandex.Money had a Piamnuy, where there were no free places.
Why be a product (or project), the secret of tough teams success, essays were about business life, and how to settle the local hell - for those who were not, everything was written down, there is a mountain of knowledge with experience. Turn the background, as in the TV.
I will talk about the cases and my decisions, which led to failures or victories in building communications between the teams of two corporations. The first case is about how to lose a strong PM due to mutual misunderstandings on the basis of what the business actually needs. The second case focuses on how important it is to explain to the team that the product is needed by the market, and how speed, efficiency and well-coordinated work of all involved teams come with it.
I have repeatedly seen how companies decide to implement the popular Scrum, considering that they have found a “silver bullet” for success. In reality, in companies with large-scale development in the long run, Scrum is not enough. Teams run in different directions, and the result ceases to satisfy the business. I’ll tell you how in Wrike, while remaining flexible to change, we use the strategic planning tool OKR (Objective and Key Results) in conjunction with the tactical framework Scrum, and what changes have occurred.
In the report I will talk about the experience of using the kanban method in the development team of the online lending service. How we managed the flow of work, agreed with the business about quarterly goals and changed our plans as we went along. What problems of scaling during the transition from Scrum to Kanban were encountered and how they were solved. I will also talk about the points of contact and friction between the links in the chain of creating the final product and share the lessons learned. The report will be of interest primarily to project managers from the IT side and product managers from the business side.
Have you fallen victim to the development of development processes and gone out of fashion? Modern experienced team one by one refuse from this post? Product owners have become modern PM? Is this true and what to do to everyone who has linked his career with this profession?
Subscribe to our blog - we talk about what is under the hood of money, and how we live with it. Come to events and follow the news.
Source: https://habr.com/ru/post/442882/
All Articles