Articles, Blog Posts, Books and Quotes on Agile Project Management
If one of the first aim of Scrum was to break the silos between business analysis, development and testing, you can consider that improving the cooperation with the operation side of IT as the next frontier in this journey. What is the point to produce potentially shippable software increment in two weeks if your database administrator doesn’t want more than three new releases windows for the production database?
The first value of the Agile Manifesto is about “individuals and interactions over processes and tools”. Communication is fundamental inside and outside the Scrum team. In his article “Watch Your Words: Feedback Analysis”, Tom Bartel give some hints on how to improve the feedback process especially in a negative context.
If shorter release cycle could be considered as a success for Agile software development teams, they might be considered as an issue if the other parts of the organization are not ready to handle this. In this article, Colleen Johnson shares an experience where the successes achieved implementing the Kanban method at the team level were leveraged to expand them to the enterprise level.
If Scrum is the king of the Agile software development frameworks, Kanban can be defined as a distant cousin. We know that there are some connections through this Lean parents, but we don’t always known what it looks like exactly and when to use it. If you want to have a clear and quick (60 pages) understanding of what Kanban is, then this Kanban Workbook is for you.
When do you need to stop coaching an Agile team? In his blog post “An Exit Strategy for the Agile Coach”, Len Lagestee discusses this question and explains how he will gradually work to be ready to leave and let the Scrum team be ready to carry the Agile values on its own.
Like the notion of technical debt, the concept of management debt relates to the leadership issues that prevent a successful Agile transformation. This article from Agile transformation expert Sriram Rajagopalan discusses the types of waste that can be eliminated using a Kanban approach and the role of management debt in perpetuating wasteful practices.
The notion of product is important in Scrum. Many qualify it as a product development approach rather than a project management framework. The product owner role is responsible that the production of the Scrum team meets the requirements of the customers and deliver value for the organization. This role is often compared to the role of product manager. In his article “Mapping the Product Manager Role to the Product Owner Role”, Sriramasundararajan Rajagopalan discusses if a product manager is the same as a product owner.
Scrum Expert Copyright © 2009-2024 Martinig & Associates