Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
“The reason that most software developers don’t seem to get excited about meeting cost and schedule commitments is that these usually are not team goals. Although management may think that cost and schedule are important, typically no one ever tells the team why these goals are important, and the team...
The activity of project managers should be to gather requirements, estimates and control the work … or is it? This articles suggests that the main activity of project managers is in fact negotiation. You will learn how to gain influence and power in your organization as well as how to...
This article presents three ways to predict schedules based on historical data with some amount of rigor. Evidence-based project management is a technique that allows you to generate predictions for a release based on historical data—not estimates, but predictions.
In this blog post, Eli Weinstock-Herman proposes a lightweight process for project management and explains that the most critical part of creating a process is to know why your creating it.
Significant growth due to estimation inaccuracy can wreak havoc on a team attempting to stay within cost and schedule while executing its established plan. This article discusses how a software team that uses both proxy-based and size-based estimates is able to accurately plan, launch, and execute their project on schedule.
The most successful projects are those that have a solid foundation and actively supportive sponsors. One key issue that must be addressed during project initiation is the identification of the “right” project sponsor; one who has enough political clout and backing to overcome the obstacles that arise in the lifecycle...
This article proposes a framework where software engineers and project managers can quantitatively manage software projects to improve the software development process applying Six Sigma in conjunction with the Personal Software Process (PSP) and Team Software Process (TSP).
Concrete barriers to Scrum adoption are inevitable. Test cycles will not magically shrink without effort. Most of the challenges in Scrum adoption are not technical, but social.