Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
In this article, Chia Wei Cheng discusses the common controversies about story points and task hours during Scrum sprint planning. He defines story point as a high-level estimation of complexity made before sprint planning. On the other hand, he wrote that “the task-hour estimation is a low-level estimation made to...
In this blog post, Bill Nichols discusses the fact that the engineering disciplines needed to apply agility to mission-critical software systems are not as well defined or practiced. His posts gets its title from a from book written by Barry Boehm and Richard Turner in 2003. He summarizes a talk...
In this article, Carlos Eduardo dos Santos Nunes shares some of his experience of situation where an Agile team has to cooperate with a Project Office (PMO). In some situations, you have to take into account the importance of project management, based on the PMBOK (Project Management Body of Knowledge)...
Corey Ladas wrote a classic essay on Scrum-ban where he discusses Scrum and Kanban hybrids. He presents the concept of index card and explains that Kanban is more than just a work request on a card and putting sticky notes on a whiteboard is not enough to implement a pull...
In this interesting blog post, Glen Alleman discusses the concept of competency models for project managers. He lists a set of elements that should be used to assess project managers in the following areas of competence: performance measurement, status reporting, organizational processes, team building, staff development, perspective, negotiation, risk management,...
It has been 5 years since David Anderson and Rick Garber first presented the Kanban Method to a limited audience at small conference in Chicago. This session gives the Lean and Kanban community in the software development domain an opportunity for reflection on how far we’ve come in 5 years...
In this article, Christophe Le Coent discusses shared responsibilities and clear accountability in software development projects. He proposes a RACI+F matrix where the letters have the following meaning: Responsible, Accountable, Consulted, Informed, Facilitate. This allows to create RACI+F matrix for the Scrum project activities for each Scrum roles. This matrix...
In this blog post, Steve Andrews discusses the usage of team velocity to plan the next Scrum sprints and how can we use it to make more informed management decisions. Using a quantitative management approach and Agile methods allows us to actually measure the impact of management decisions on the...