Remove 2004 Remove SCRUM Remove Software Review
article thumbnail

AoAD2 Chapter: Teamwork (Introduction)

James Shore

To share your thoughts, join the AoAD2 open review mailing list. 1 When the Agile Manifesto was written, people thought about software development in terms of projects. It’s a constant refrain in Agile literature: Software development teams where everyone is alike, while comfortable, are not effective. Beck 2004].

article thumbnail

Scrum by Example – Stop Digging New Holes

Agile Pain Relief Notes from a Tool User

When something small changes in these classes, it ripples through the entire code base. Even after simplification they find the code base still has over 10,000 rule violations. They agree to raise the issue in the next Daily Scrum. In addition they discovered that their existing Unit Tests only provide 10% Code Coverage.

SCRUM 52
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

AoAD2 Chapter: Planning (Introduction)

James Shore

To share your thoughts, join the AoAD2 open review mailing list. The preface of the first Scrum book said that “Scrum reduces risk and uncertainty by making everything visible early and often to all the people involved and by allowing adjustments to be made as early as possible. “ [Schwaber and Beedle 2002] (p.viii) (emphasis theirs).

SCRUM 64
article thumbnail

Agile vs Waterfall: Key Differences And Definition?—?Which Model Is Better?

Codegiant

Agile is also about human interactions, customer collaboration, adapting to change, and producing working software. You observe how the market reacts to the software you create and then make iterations to improve it. The Agile methodology definition was introduced by 17 software developers gathered in Utah back in 2001.

Agile 52
article thumbnail

Grown-Up Lean

LeanEssays

Lean was introduced to software a couple of decades ago. The Nature of Software “Do not go where the path may lead, go instead where there is no path and leave a trail” -- Ralph Waldo Emerson It’s May 27, 1997. I show that these models derive from opposing assumptions about the nature of the software-debugging task.

article thumbnail

No Fighting In This (Agile) Dojo with M. David Green

Marcus Blankenship - Podcasts

How can we train teams to consistently produce quality code without negatively impacting productivity? The results will be more engaged team members, scrum masters, and a way of working that converts skeptics and naysayers into Agile evangelists. Engaged scrum masters are essential for long-term change (26:49). Episode 46.

Agile 59
article thumbnail

AoAD2 Chapter: Ownership (introduction)

James Shore

To share your thoughts, join the AoAD2 open review mailing list. Lean Software Development. This is due to a fundamental Agile principle: the people who are doing the work are the ones who best understand what needs to be done. The “Done Done” practice: Create software that’s ready to be released.

SCRUM 49