2012 Influencer SCRUM Technical Review 
Herding Cats
MAY 10, 2019
Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. 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.
Herding Cats
MAY 11, 2019
Information about key project cost, (technical) performance and schedule attributes is often uncertain or unknown until late in the program. 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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Project Pulse Journal
MARCH 20, 2024
A systematic review of available data and active input from the team is required here, emphasizing the need to leverage collective expertise and insights to determine development strategies. Regular audits and phase gates help teams review project performance and track progress systematically.
Scrum.org
DECEMBER 23, 2021
Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. So I was pleasantly surprised when Carsten Grønbejrg Lützen pointed at a peer-reviewed academic paper by Michele Tufano and his colleagues (2015), called “When and Why Your Code Starts To Smell Bad”. Technical Debt and Code Smells.
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. Cognitive paradigms, applied to Scrum / Agile. When a Scrum Team starts work on a Sprint (e.g.
Scrum.org
APRIL 7, 2022
Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Edmondson (2012) argues that dynamic teaming is important to share and encourage learning. This is also what inspired Edmondson (2012) in her academic work on “teaming”. This post is my attempt to do this. Bradley et.
Herding Cats
APRIL 16, 2019
Business, Technical, Systems, Risk, and Project Management Briefings and Presentations. Technical Performance Measures (#TPM). Cost, Schedule, and Technical Performance Management (#CSTPM). Business, Technical, Systems, Risk, and Project Management. Table of Contents (Click the Name to go to Section).
Expert insights. Personalized for you.
38 
Let's personalize your content