Project Management for Software Development
Tutorials and tools for managing, estimating, planning and tracking software development projects: PMP, Agile, Scrum, Lean, Kanban
Finding the right balance in software development organizations is neither an individual task nor is it only a project team’s responsibility. It is an interaction of both and more! Software project managers also play a vital role as they often (still) have a higher organizational lever.
What is the secret of successful agile initiatives and awesome teams? Teamwork and effective collaboration, of course. It is important to set up software project development teams for success, as well as implement continuous improvement processes to ensure antipatterns and difficulties are addressed.
If you want to build a relationship of trust with the team, behave showing the example that you want the team to follow. That means, be present physically and mentally 100% of the time.
Are you interested in learning more about self-managing teams and how to share authority within an organization? This talk discusses the basic patterns and processes of Sociocracy for All, a system of self-governance that can be used in combination with Agile practices to scale self-organization across all decisions made in...
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.
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?