Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
“Behavior change happens, but it happens slowly. It may take several tries from different angles before a team changes their stand-up behavior. Be patient. Keep trying. They will change when they need to, but only if you don’t shield them from natural consequences that follow from poor stand-ups.” Reference: “Coaching...
Most people try to avoid failure at any cost. However, the real question is how do we define project failure? In most cases, you will hear people talk about the project going over budget, the project being late, or the project being buggy. These three reasons are probably the most...
Glen Alleman writes about 11 criteria should be found on any project trying to be successful and that you should find in any project attempting to use Earned Value Management.
This article “Decomposition of Projects: How to Design Small Incremental Steps” by Tom Gilb gives some guidelines, policies and principles for decomposition of projects for incremental development. It also gives a short example from practical experience.
“Aspects of Kanban” is an introduction to the Kanban workflow Lean project management system.
This happens all the time on projects: assuming there is consensus when none exists. While good teams can roll with these punches and adapt as they go, it’s a form of waste that can hurt or kill the unwary before they even get out of the gate. To nip this...
as a project manager or as business stakeholder how does one determine whether to bring the project back to life or just kill it? Answering this question is not that hard. You will find it in this post “When Do You Kill A Project?“