Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
In the Agile world, bottom-up continuous improvement is the new mantra that replace the (rarely done) postmortem reviews of traditional project management approaches used in software development.
This talk explores the practice of nonviolent communication, and how you can use it to build trust, develop better quality relationships and resolve conflicts in your software development team.
This book was written in 2004 by Barry Boehm and Richard Turner, but the fact that it is already on its 6th reprint tells something about its value. This is a very pragmatic book that tries to put in perspective agile and plan-driven software development approaches.
Eric Ries defines a Minimum Viable Product as the version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. Using the Minimum Viable Product concept is valuable, but its effectiveness is often hampered by excessive process.
Small software development projects are easy to manage. GitHub issues or Basecamp todos are more than enough to keep things going. Adding a feature or refactoring a small software development project is also easy, because there aren’t too many moving parts to consider.
Redmine is a free and open source, web-based project management tool written using the Ruby on Rails framework. It allows users to manage multiple projects and associated subprojects. Redmine features issue tracking, project wikis and forums, time tracking, and flexible, role-based access control.
Scaling agile is all the rage these days, and especially popular with laggard adopters who want to broaden their management span of control. Most scaling frameworks are just classical military hierarchies suitable to command-and-control: in a suitably arranged organization of 625 people, the average number of communication hops between any...
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.