Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
Agile methods work beautifully for a single team. But what do you do when you have multiple, interdependent teams, all working on a single product or product suite? How can Agile scale without losing sight of its core principles? In this session, we’ll examine how to apply Lean and Agile...
In this blog post, Thomas Cagley discusses the need to size the scope of a software development project during the estimation activity. His opinion is that the main benefit of sizing is the conversation that this effort generates. But as managers and estimators are numbers people, it is not safe...
This article provides provides 65 rules that should help you running successful software development projects. These hints are rooted both in the classic approach to project management and in the new approaches proposed by Agile project management frameworks like Scrum.
One very important property in Kanban is called “make process policies explicit”. This includes well-defined interfaces to upstream as well as downstream partners. Kanban tries to define these interfaces on a very abstract level, because Kanban is a change management approach that wants to integrate with several possible project management...
In this article, Juan Banda discusses the visions of project management from the PMP and Agile sides. On one side, the traditional project manager follows the PMBok Guide and manage a project trough planning and control. On the other side, Agile project try to empower the team member and produce...
Not everyone is a fan of the self directed self organizing team. It flies in the face of traditional project management, and often conflicts with the traditional organization model. The benefits of self directed teams however are too big to ignore and now we have scientific proof as to why.
This short article provides an approach to adapt the Scrum concept of velocity to traditional project teams that are working without using the sprints/iterations of Agile project frameworks. In Scrum, velocity is how much product backlog effort a team can handle in one sprint.
Inspired by the Gang of Four patterns for object oriented software development, Michael Duell proposes in this article some patterns for dysfunctional project management behavior. He classifies them in the cremational, destructural and misbehavioral patterns categories.