Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
This article discusses sustainable pace as an essential element to long term well being in project management. In Scrum projects, the team needs to be comfortable speaking up and pushing back; the Scrum Master needs to help shield them and Product Owner, to listen. There needs to be a safe...
Risk management and reduction is an important activity for the project manager. Accidents will always happen and corrective action is then needed to deal with issues encountered during projects. Unfortunately, actions taken to resolve a problem often only address the problem itself, not its underlying causes.
The article “Moneyball for software engineering” explains how metrics-driven decisions can build better software teams. The basic idea is that organizations can use statistical data to build more competitive teams. Most of us work in software project teams, but we rarely use metrics to identify strengths and weaknesses, set and...
In the world of software development, estimates usually don’t hit the mark. This article discusses the need to manage software development projects from a financial perspective and not just with estimates and progress tracking.
In this blog post, Tom Perry shares his thoughts about how the software project team productivity is influenced by change. Finding that combination of what works for a project can take time. However, when this happens, it will often produce a dramatic improvement in performance and not a slow gradual...
The Team Software Process (TSP) provides a framework to predictably and effectively build software-intensive products. It relies on data collected by team members to provide insight into how a software project is operating.
This article explains the usage of Earned Value Management (EVM) in software development projects. EVM is simply a way of calculating two pieces of data for a project: schedule performance and called cost performance.
Jeff Sutherland explains in this video that the Burndown Chart is intended to monitor the simultaneous agile development methods going on within a Scrum team. Like a fighter plane landing, there is no room for error, and the chart is intended to monitor such issues.