Collaboration Games for Agile Teams
Collaboration Games from the Growing Agile Toolbox is a free e-book written by Karen Greaves and Samantha Laing that proposes ten games to build collaboration in Agile teams.
Articles, Blog Posts, Books and Quotes on Agile Project Management
Collaboration Games from the Growing Agile Toolbox is a free e-book written by Karen Greaves and Samantha Laing that proposes ten games to build collaboration in Agile teams.
Absent ScrumMaster, poorly defined requirements, inexperienced team, absent product owner, impossible goals. Sometimes things can go wrong even in projects that use an Agile approach like Scrum. The main issues are absent product owner or ScrumMaster, an inexperienced team, poorly defined requirements or impossible goals. In this article, Avelino Ferreira Gomes Filho shares some of his experience as a replacing ScrumMaster in troublesome Scrum projects.
Whether you follow a Agile framework like Scrum with its planning poker or a traditional project management approach, the estimation activity is always difficult to perform productively and consistently on the long term.
A prevailing belief among Agile and Scrum proponents is that “a great deal of explicit risk management becomes unnecessary when a software development project uses an agile approach.” In my experience, this is a false and dangerous assumption. Project risk is a hungry leopard ready to devour the unprepared. Fleet-footed agilists and die-hard waterfallists alike.
Agile and Scrum project teams can adopt many different structures. In her blog post, Elizabeth Harrin gives a good summary of five structures that could be used by Agile teams based on a presentation made by Catherine Powell at the Oredev conference.
Technical debt a metaphor that refers to the eventual consequences of poor or evolving software architecture and software development within a codebase. The technical debt can be defined of as work that needs to be done to adapt a software to the best practices. In this blog post, Bastian Buch explains the step used in his organisation to reduce technical debt in an Agile way.
The main goal of a sprint review in Scrum is to receive feedback on the product that the team has built in the last sprint. How do you do when the product is created by many different teams and there multiple stakeholders who are involved in the Scrum project? In this article, Stephan Kraus explains how to scale the sprint review in Scrum using the fair concept.
Scrum Expert Copyright © 2009-2024 Martinig & Associates