Maintaining an effective rhythm has long been recognized as an attribute of successful architecture. It is easier for the many organizations involved with the architecture if there is a predictable tempo, content, and quality associated with the architecture. Rhythm is also an important quality of many agile software development methods. I define rhythm in this context as “the recurring, predictable exchange of work products within an architecture group and across its customers and suppliers.” This talk argues that rhythm is important for establishing trust in architecture and architects. The talk also presents some ideas on how architects can establish and sustain an effective rhythm. This presentation was given at SATURN 2015 (http://www.sei.cmu.edu/saturn/2015) Video of the presentation is also available (https://t.co/WuGoEKlX2Q)

1. Keeping the Beat:
Rhythm and Trust in
Architecture
David Kane – david.kane@santeon.com
SATURN 2015
April 29th, 2015

2. Definition
Rhythm is the recurring, predictable exchange
of work products within an architecture group
and across their customers and suppliers.
Tempo Content Quality
Software Architecture: Organizational Principles and Patterns –
Dikel, Kane and Wilson

3. More than one beat
Content
Time
Major Release
Rhythm
Milestone
Rhythm
Weekly
Rhythm
Software Architecture: Organizational Principles and Patterns –
Dikel, Kane and Wilson

4. Can Fail with Too Little or
Inconsistent Tempo, Content or
Quality
Content
Time
Content
Time
Content
Time
Abbreviated Processes
Software Architecture: Organizational Principles and Patterns –
Dikel, Kane and Wilson

5. Rhythm and Architecture is Not New

6. Why is Rhythm Valuable?
Aids transition management

7. Why is Rhythm Valuable?
Drives closure

8. Why is Rhythm Valuable?
Every commitment met builds trust

9. Avoid Commitments Based on
Means
21 Points
19 Points
The Power of Commitments (AgileDC 2014) – Nielsen

10. If you have to miss on
something, miss on content

11. Why is Rhythm Valuable?
Drives small batch size

12. Variations
Rhythm Without Timeboxes

13. Resource Optimized

14. Flow Optimized

15. Balance Flow and Resource
Optimization
Resource
Efficiency
Flow Efficiency
Impossible
Balance
resource and
flow efficiency
This is Lean: Resolving the Efficiency Paradox Paperback – Modig and Ahlstrom

16. Predictability Without Timeboxes
Count
Cycle Time
Mean
Median
90%

17. Break Time