Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
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.
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.
Stakeholder engagement is critical in agile projects. Agile project managers, business analysts, product owners, Scrum masters as well as agile teams must plan their approach to collaborate well with stakeholders and build productive working relationships.
For years the presenter was telling you how awesome self-organization and autonomy are in the context of organizational design and software development project management. Well, he lied.
As software development teams start to grow, some common struggles appear: team members feel like projects go on and on, with no end in sight, and product managers cannot find time to think strategically about the product. In this talk, Ryan Singer explains how the Basecamp team operates.
Team-based software delivery can be very effective, but how can we promote and enable team-based approaches in a “remote-first world” for software development projects? What should teams think about, and what patterns can teams adapt to be effective when no one is in the office?