2002 Process SCRUM Software Engineering 
Scrum.org
OCTOBER 19, 2022
And we share results from our own analyses based on actual data from stakeholders and Scrum teams that we collected through the Scrum Team Survey. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. But adherence to a framework or prescribed process does not guarantee agility.
Herding Cats
MAY 10, 2019
Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. 3, March 2002. 11 November 2002. México, 1 al 3 de Febrero de 2006.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
MAY 11, 2019
Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993. IEEE Transactions on Software Engineering , Vol. 3, March 2002. 11 November 2002. México, 1 al 3 de Febrero de 2006.
Herding Cats
MARCH 11, 2017
This quote demonstrates a lack of understanding of making decisions in the presence of uncertainty and the processes and events that create uncertainty. There is naturally occurring variability from uncontrolled processes. Aleatory uncertainty is expressed as a process variability. First, let's establish a principle.
Epicflow Blog
MAY 14, 2019
Most organizations build structures and processes designed to prevent project failure. However, Muratgali Karimsakov , a Project Engineer at Karachaganak Petroleum, warns that lessons learned must be applied in the right way: “Unfortunately, the lessons learned process in many companies doesn’t work properly.
Scrum.org
FEBRUARY 3, 2020
Their paper provides useful insights into why the Scrum Framework might be so effective when it comes to managing complex work. Their article inspired me to apply the same insights to Scrum and to extend it with my own. Why our brain is not built for software engineering. waterfalls) are very likely to fail.
Herding Cats
APRIL 4, 2019
Probabilistic Risk Assessment and Management for Engineers and Scientist 2nd Edition , Ernest J. Agile Risk Management and Scrum , Alan Moran, Institute for Agile Risk Management, 2014. Project Risk Management: Process, Techniques, and Insights , 2nd Edition, Chris Chapman and Stephen Ward, John Wiley & Sons, 2003.
Expert insights. Personalized for you.
199 
Let's personalize your content