Skip to main content

Exercise:: Mapping Engineering Practices to Agile Principles

What are the necessary and sufficient engineering practices that an agile team needs to support the Agile Manifesto's 12 principles?

There is no one right answer - yet there are some very common patterns one sees when this exercise is repeated for multiple teams within an organization transitioning to agile software development.  From this analysis one could derive the set of core practices for your agile organization.





Exercise :: Mapping Engineering Principles to Agile Practices (PDF) by David Koontz

Facilitation Guide
Set up Print all material, one Agile principle per page (enlarge if you wish).
Hang the Agile Manifesto on the wall.
Hang the 12 Principles on the wall.
Hang the suggested list of Practices on the wall.

Have multiple colors of sticky notes & lots of pens/markers.

Introduce the Manifesto and the 12 principles
Discuss the Agile Manifesto - tell the history - describe what a process is and is not. Is “Agile” is a process?  Describe a philosophy - could it be that?

Distinguish between a Principle and a Practice
Switch to the Engineering Practices - describe a few of them - invite participants to read the list, to circle the ones which they currently do very well. 
Invite them to add to the list - debate which practices are redundant (ex: code review & pair programming).

If the group currently has real disciplined practices - use them to map to the principles - however if not don’t waste your time - just to the desired future state.

Dot-vote - each person pick three (2-5 is a nice range for this) engineering practices they wish to use in the future - the best practices to make us an Agile team.

Using those top voted practices (limit to 5 -8 practices to map), have people pair up and map one practice at a time to the 12 principles.  Decide if the engineering practice “supports” the principle - if so put the sticky on the paper - if weakly supporting - put the sticky below - if not at all then no sticky. Same pair do each principle. Use different colored stickies for different practices to create a nice Info-graphic when all done.
Be the example - select two participants and demo the first few principles for something like TDD.

Debrief
Which principle is weakly supported by practices?
What practice would fill this gap?
Which practice supports the most of the Agile philosophy?
Does it work alone - if we just do that one practice - are we Agile?
What is the “neccessary and sufficient” set of practices for Agile?
Which practices should we embrase as a core set?



Engineering Practices
Continuous Integration with Automated Builds
Smoke Testing / Build Verification Tests
Domain Driven Design / Emergent Design / Evolutionary Design Behavior Driven Development
Test Driven Development
Pair Programming
Code Reviews
Automated Software Metrics
Source Version Control
Issue / Bug Tracking
Configuration management
Unit Testing
Integration Testing via Mock/Fake/Stub sub-systems
Exploratory Testing
System Metaphor
Story Testing / Acceptance Tests / Automated Regression Test
Scrum (Process Framework)
Extreme Programming (XP) Framework
Stand-up Meeting
Velocity Based Planning
Team estimation in relative units (Story Points)
Iteration Demo & Customer Feedback
Information Radiators (Big Visible Charts)
Cross-Functional Team
Team based work flow / Teamwork / Persistent Team
Co-located Team / Common Workspace
Design Improvement via Refactoring
Small Releases / Frequent Delivery
Collective Code Ownership
Coding Conventions & Standards
Simple Design (Once & Only Once, YAGNI, etc)
User Stories


See Also:

The 12 Principles Ice Breaker by Gerard Chiva on Oikosofy
What are the Principles - a case study of using this exercise

1 comment

Most Popular on Agile Complexification Inverter

Software Development terms applied to Home Construction

Let's Invert the typically wrong headed view of Software Development project management as a construction project.  We can map it the other way just to see if it works... to have some fun, to explore the meaning of phrases we toss around quite frequently.


Normally Project Management terms come from a construction domain.  We are going to apply the lexicon of modern software to the construction of a home.  We will follow the construction project and meet some of the people doing the work.

This is a very small (8 homes from $600,000 skyward) program in my 30-40 year old neighborhood.

About 6 months ago I saw the programs landing page go up.  It gives casual observers and some of the stakeholders a general idea of the intent of the program.  And most importantly who to contact for additional information if you happen to be interested in their products.

The Refuge program has 8 product projects and has them running independently.  Yet much of their DevOps infrastructure has already b…

Innovation in the Automobile Industry

In the 1900s the automobile industry was the most important and innovation industry in the USA.  But one could question if this was good for our society in the long run.  And one could question if they actually innovated.

In the early 1900s there were few automobiles, very little infrastructure created to support the industry.  For example the road system was still designed for horse drawn wagons and the wagon wheel (remember a steal rim and wooden compression spoke wheel).  The future US Highways, or the 1950s Interstate Highway System at the cost of $425 billion were decades and many innovations away. There was no gas service station, there were however horse stables, farriers, and blacksmiths in each town along the roads.  There was no real "road map", there was no road naming system, like was created in 1926 - the United States Numbered Highway System.

The industry employees millions of people, and was a large factor in the economy of the USA.  It created or was created b…

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

Timeline of Social Networks -or- the Long Haul

I was listening to KERA's Think and they mentioned the concept of social networks.  It got me think...

But the book Long Haul, is its own interesting story - A Million Miles and Counting - A Trucker's Tale.

“The Long Haul: A Trucker’s Tales of Life on the Road”
Did you know 41 million people move in the US a year?  Having moved a few times in my life, sometime with the Bed-Bugger's help, this book is a great insight into that life.
Author: Finn Murphy's CB handle - "U-Turn" The radio interview noted the concept of social networks in the 21st century.  What is a highway - but a manifestation of a social network - a trail across the land.

a timeline using the Knight Lab Timeline JS tool kit.

See Also:

Social Media - Tracking its Exponential Growth video
Social media has overtaken porn as the #1 activity on the Web
List of social networking websites - Wikipedia

The World's 21 Most Important Social Media Sites and Apps in 2015



The Growth of Social Media - infog…

a little feedback please...

some feedback please...
How do you like the new look and feel of our site?
  ___)  nah (I like the old one better - bring it back)
  _X_)  yeah (much cleaner and easy to navigate)



powered by Typeform
See Also: