Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
As Agile adoption is spreading and more software development teams want to adopt an Agile project management approach like Scrum. In this article, Robert Karlsson ask the question the question “Why should your boss let you implement Scrum in your organization?”. Your boss might be satisfied with the current situation...
Managing traditional or Scrum project performance is never easy. This talk aligns two different ways of doing it, the Agile and the traditional. Traditional project management is based on the mostly used project management standard, the Project Management Body of Knowledge (PMBOK). This is not a presentation of Agile and...
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 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.
Agile principles begin with the notion of creating valuable software, but fail to explain what that term means. Value is not defined by process or output, but rather results for the customer and the business. Every member of the agile team should feel like an owner of the term “valuable”.
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...
Last Comments