2012 Development Team Review Risk SCRUM 
International Institute for Learning
APRIL 19, 2023
They build on lean-agile thinking, and standard Scrum, Kanban, and DevOps practices. They offer practitioners tools to extend and mature their agility beyond the team to programs and the broader enterprise. DA was developed in 2011 by Scott Ambler and Mark Lines and is based on Scott’s work at Rational Software and IBM.
Scrum.org
FEBRUARY 15, 2020
We all know that Scrum is a framework, but for instance, imagine Scrum to be a gauntlet that holds all the six infinity gems. If so -what could be its infinity stones that could fit the scrum gauntlet which makes scrum so powerful and inevitable? Let’s explore together powers of the Scrum Infinity Stones!
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scrum.org
APRIL 7, 2022
Considering just how popular the notion of fluid teams has become, I think it is important to weigh the evidence that supports it or contradicts it. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. This is also what inspired Edmondson (2012) in her academic work on “teaming”.
Herding Cats
APRIL 16, 2019
Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Risk Management (#RM). The following material comes from conferences, workshop, materials developed for clients. Business, Technical, Systems, Risk, and Project Management. Table of Contents (Click the Name to go to Section).
Herding Cats
JUNE 12, 2018
In a very technical answer, the sample rate can be determined by a Nyquist sample rate analysis of the underlying non-stationary stochastic process processes of software development projects. We assess physical percent complete at close business every single day, with the update of the TO DO field in Rally at the Task level.
Herding Cats
JUNE 12, 2018
We assess physical percent complete at close business every single day, with the update of the TO DO field in Rally at the Task level. At a minimum, at the end of every week, a Scrum team assess physical percent complete and updates their estimate to complete in some field in the Scrum development system.
Project Pulse Journal
APRIL 16, 2024
Conduct the Sizing Session - Team members assign a t-shirt size to each backlog item through discussion and consensus or by individual voting (similar to planning poker). Review and Adjust - Once all items are sized, review the assignments to ensure consistency across the backlog. splitting an XL task into two L tasks).
Expert insights. Personalized for you.
59 
Let's personalize your content