2010 Strategy Technical Review Underperforming Technical Team 
Scrum.org
DECEMBER 23, 2021
Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. Why do software teams?—?despite 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”.
Wrike
MAY 23, 2023
I joined the team as a QAA engineer in 2010, the first employee in this role. Over the past 12 or so years, we have built a super team of brilliant QAA engineers. The team made a complete audit of everything that could be checked and improved by at least 1%. But he was wrong — Team Sky won in just three.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scrum.org
FEBRUARY 16, 2021
From 2010 to 2017, I worked several years in three Berlin-based, fast-growing startups in my capacity as Scrum Master, agile coach, and Product Owner. In my experience, the challenges of becoming a learning organization can only be handled effectively by self-organizing teams. Culture eats strategy for breakfast. ” (Peter Drucker).
Wrike
NOVEMBER 7, 2018
89% of high-performing organizations value project management, 81% actively engage sponsors, 57% align projects with business strategy. [6]. Keys to Project Success: 48% say the team’s technical skills. 26% say effective team communication. Lean & Test Driven Development (TDD) – 11%. Technology.
Herding Cats
MAY 10, 2019
Risk Management is essential for development and production programs. Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. 255, April 2010. 24, 2010. “A Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003. De Meyer, C.
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). Product Development (#ProdDev). Strategy (#Strategy). Agile Software Development (#ASD). Risk Management (#RM).
Herding Cats
MAY 11, 2019
This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. Risk Management is essential for development and production programs.
Expert insights. Personalized for you.
178 
Let's personalize your content