Scrum of Scrums is a technique used to scale Agile by dividing the groups into Agile teams of 5-10. Each daily scrum within a sub-team ends by designating one member as representative to participate in a daily meeting with ambassadors from other teams, called the Scrum of Scrums. This article provides some tips on how to succeed with Scrum of Scrums.
Articles, Blog Posts, Books and Quotes on Agile Project Management
Agile software development refers to methodologies and principles of effective, iterative, and collaborative programming. It becomes more and more popular nowadays as suggests a more affordable and client-oriented process. Agile nearshoring means delegating programming tasks to dedicate teams in a nearby country to increase business success and get a project released faster.
In their book “Help Work to Flow”, Samantha Laing and Karen Greaves have explored their Agile working and coaching experience to collect 40 tips, techniques and games that should allow you to work in the state of flow, this situation where you are more productive.
In Kanban, the concept of work in progress (WIP) limit defines the maximum amount of work that can be performed by a team or that can exist in each active status of a workflow. In this article, Gerard Chiva explains why limiting WIP is an important decision for Agile teams.
There are three roles in a Scrum team: the ScrumMaster, the developer and the product owner. This last role might be the most important for a team that uses an Agile project management approach in software development. The product owner has the responsibility of building and prioritizing the backlog. If this is not done properly, you will just not build the right product. This article presents the certifications available for product owners in Scrum.
The values contained in the Manifesto for Agile Software Development might be good for the Agile teams, but most of the senior management in organizations prefer having a defined solution, a detailed planning and a budget that should be respected. This article discusses how to make these two different approaches work together.
In an ideal Agile world, the Scrum Master takes care of only one Scrum team. This is however not always possible and then he has to split his time between many teams. In this article, Alexander Chaves shares some tips on how to lead multiple Agile teams without becoming insane.