Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
This shares a case study of an organization that needed to re-establish itself as a leader in a transformed financial market. This required the early delivery of business benefit from its new channel website, but when the project was planned using the organization’s standard waterfall approach, it showed the requirements...
Teams are not mentioned in the definition of Kanban. In his blog post, Yuval Yeret discusses the impact on team structure when an organization is trying to adopt Kanban. He proposes a categorization of teams modes and an evolutionary approach on how to use them when you adopt Kanban, starting...
David Martin had a problem as a project manager: his projects never came out on time or on budget. He tried to apply all PMBOK best-practice guidelines: taking care of schedules, tracking progress carefully, making sure that the team estimate correctly and ensure requirements stability. It still didn’t work and...
Continuous delivery is a software development strategy that optimizes your delivery process to get high-quality, valuable software delivered as quickly as possible. A common failure mode of software projects is called the large batch death-spiral, whereby product owners, in an attempt to ensure the success of their product, add more...
Is there a relationship between the dependency of project tasks and the achievement of work close to the estimated date? This is the discussion that Assaf Stone carries in his blog post “Do Agile Estimation Techniques Really Account for Scrum Projects’ Successes?“. His conclusion is that a project with multi-dependent...
This video provides a high level overview of Microsoft Project Server 2010 and focuses in on Portfolio Analysis. This area is a major pain point for many organisations and in this video we see how organisations can improve their project selection and approval processes.
This videos shows how to manage the situation of multiple Scrum teams working together with JIRA and GreenHopper. It explains how to manage backlogs and sprints and shares the lessons learned during thir real life project.
A Scrum BurnUp Chart is a specific Big Visible Chart that is used to show progress for a release or iteration. The horizontal axis represents Time and the vertical axis represents Scope. For a release burn up the horizontal axis is used to represent iterations while for an iteration burn...
Last Comments