This page is both to present my series of blogs in an ordered manner and to provide references mentioned in them.
Table of Contents
- Acceptance Test-Driven Development
- Scrum From a Disciplined Agile Perspective
- The Importance of Theory
- Complexity and Simplicity
Acceptance Test-Driven Development
- The Essence of Acceptance Test-Driven Development (ATDD) – it’s not about testing
- Test-Driven Development in the Larger Context: Pt 1. Audience
- Test-Driven Development in the Larger Context: Pt 2. Cadence
- Test-Driven Development in the Larger Context: Pt 3. Automation
- Test-Driven Development in the Larger Context: Pt 4. Synergy
The Importance of Theory
- How to use theory to get past some challenges faced by Scrum teams
- Theory can create a vision for an individual, for the team and for management
- How a little Lean theory can help those doing Scrum
- How to use theory to get past some of the challenges of Scrum
- The Difference Between Inspect and Adapt and PDSA
- Empiricism and Empirical Process Control Are Not the Same Thing
- Random Thoughts on Scrum Guide Based Scrum- Lack of Guidance and Theory
- Using the Theory of Flow to Illustrate Impediments in 2 Hrs Instead of 2 Weeks
- Why we want to focus on flow while using Lean and Agile
- Empiricism and Empiricism With Theory. While all methods use empiricism Scrum relies on it without a theory as to how to improve knowledge work other than to do Scrum. This limits learning to a large extent.
The following are only possible when you use theory
- Dealing with Complexity by Creating a Bias For Simplicity
- The Value Stream Impedance Scorecard (VSIS)
Complexity and Simplicity
- A parallel in Disciplined Agile’s approach to complexity and designing quality software
- A few myths to consider about “simple”
- Is it simple? Depends upon what you mean by “it”
- Understanding simple isn’t simple
Pages on the Portal re Complexity and Simplicity
Resources mentioned in posts
Testability. Read Define Tests Up Front from our book Essential Skills for the Agile Developer: A Guide to Better Programming and Design