Scrum agile project management
Allowing Agile people to form their own Scrum teams, through team self-selection, can be a powerful approach to promote empowerment and to form viable teams with fast transition towards high performance. However, if the process is not carefully facilitated, team self-selection may lead to dysfunctional teams and disgruntled team-members.
In this conversation, Luke Hohmann discusses a new approach to conducting enterprise retrospectives that overcomes the limitations of traditional models used in Scrum projects. A scaled retrospective is a meeting where multiple Agile teams come together to identify critical organizational improvements and create a viable method for delivering and tracking …
Watch and learn how to use Visual Studio Team Services to work with many teams on the same product. This presentation explains how to create a Nexus of 3-9 teams working on a single product with separate team backlogs and separate sprint backlogs while being able to visualise the total …
When teams decide to “go Agile” they invariably decide between Scrum or the Kanban Method. This is often because both Scrum and the Kanban Method provide a straightforward approach to get started. However, our experience has shown us that this leaves several options off the table.
Working in middle to large companies means working with several Scrum teams, different departments and having often far from ideal working communication processes. Product Management usually is only one piece of the greater picture and has to serve multiple stakeholders.
Scrum is by far the most used ( and abused !!) Agile project management framework in use currently across the globe. But is Scrum working for you? Is it making your team more productive or restricting them? You are working on a POC or an R&D project and two weeks …
