How do we deal with bugs in Scrum? Do we size them? Do we add them to a separate backlog? Or do we assign them to a different team running Kanban?
TOOLS TRAINING LIVE WEBINARS USER-GENERATED
|Books Events Links White Papers Wikis|
|Language:||All English Arabic French Japanese Korean Portuguese Romanian Russian Spanish|
|Access:||All Free Premium|
|All A B C D E F G H I J K L M N O P Q R S T U V W X Y Z|
11 items found
Project management and program management are all about managing risks. How do we bring the management of change and management of risk together in an agile project or a program?
The purpose of backlog grooming is to keep the product backlog up to date and clean. Scrum doesn't prescribe how you should do backlog grooming, and different approaches are used by product owners and teams to do this.
Asynchronous applications increasingly facilitate stand-up meetings as agile IT teams spread out, but are you losing the magic of actually standing up?
There is a common perception that co-located teams are better positioned to ensure good communication and deliver more efficiently than distributed teams. But in a world where global collaboration becomes increasingly common, teams often consists of people from different parts of the world working together as distributed teams.
We have more than enough agile methods. The issue is to do an existing one well.
Discovering individual talents and sharing them at the team level can turbocharge interactions and lead to higher productivity.
Did you know that the DOD has made it illegal to do waterfall? For the first time in many years, the Department of Defense (DOD) in the United States had made a major update to its procurement rules.
Thousands of people have tried their hand at pairing in a wide range of circumstances. Some swear by the practice and feel as if something is missing when they must work solo. Others are convinced pairing is pure waste and cannot possibly yield good results. Both opinions are informed by real-world experience. What specific differences in these situations resulted in such radically different outcomes?
Enterprise organizations are beginning to buy in to agile techniques outside of their development teams, to gain company-wide benefits from being agile. Enterprises require scale, and with that scale comes process. But big questions remain unanswered...