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.
Articles on Scrum and Agile Project Management
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.
If Scrum and Agile approaches are supposed to increase the chances of success for software development projects, not all the projects that want to use Scrum are successful. In this article, John Yorke shares his opinion on why Agile projects might fail because of the confusion between the roles (ScrumMaster, Product Owner, Developer) of a Scrum Team and the required Agile mindsets.
The ScrumMaster role might be the more difficult to define among the three role involved in Scrum. Starting from a “bad” ScrumMaster job description, Sam Laing discusses errors to avoid when you create such a role specification. As a bonus, she adds at the end a good ScrumMaster job description.
Agile Open Florida is a conference organized by leaders and volunteers from the Agile Florida community who are passionate about building community and advancing all things Agile. Adam Sandman, whose company was also sponsoring Agile Open Florida 2016, has written his personal report about some of the sessions.
Developing large software systems automatically generate some technical dependency issues. If this is often managed by software architects in traditional projects, how do you communicate this technical dependencies when you are organized using an Agile approach? This is the topic discussed in the paper written by a Swedish research group.
The Scaled Agile Framework (SAFe) is one of the best know approach for scaling Agile practices. In a recent article, Al Shalloway proposes his own assessment of this framework, explaining which parts are good and which parts could be counter-productive or difficult to implement.