Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
Adaptive/Lean Portfolio Management (LPM) is key to effectively becoming an agile organization and can be considered one of the pillars of business agility. In this presentation, Shane Hastie introduces the key ideas around LPM, discusses the 12 principles of Lean Portfolio Management.
The book “Lean Integration” by John G. Schmid and David Lyle is the sequel of a first book titled “Integration Competency Center: An Implementation Methodology” and is aimed at taking it “to the next level by adding more specific best practices and a rich collection of case studies”. The book...
The idea of limited work-in-progress (WIP) is coming from Lean methodologies. At its core, it means that software developers should start new tasks only when the current piece of work is done and delivered. Finding the right work-in-progress limit can increase overall system (organization) throughput.
How does a business minimize the uncertainty and risks it faces when launching a new product to market? Markets are full of uncertainties with ever changing demands. New products are entering the marketplace all the time. These products cause severe turbulence and unexpected outcomes.
Learn how to improve your process and to manage Agile basics such as user stories, estimating, backlogs, team velocity, visualizing team activity and reporting on team progress.
Kanban value system can be organised into three layers – a familiar core that drives change, a middle layer that is about giving direction and alignment, and a protective outer layer of discipline and working agreements. Or from the outside in: discipline, direction, and drive.
Even though traditional models and assumptions represent thinking that originated in the 1890s with Taylor (fixation on efficiency and utilisation) and Gantt (of Gantt chart fame) they seem remarkably impervious to change. Our problem is that we need to change otherwise we can never achieve true business agility.
In real world agile teams, traditionally defined rigid roles are rapidly being displaced by a culture of collective ownership of the product. Responsibilities are being decoupled from specialties by a collection of operators with overlapping skills, and chief among them is technical acumen.