Agile Resources

Learn more about transforming people, process and culture with the Real Agility Program

This page contains a number of links to recommended web sites, books or tools relating to Agile Work. This page will be updated from time-to-time and as this is done, announcements will be posted on the Agile Advice blog. As such, this page will always be “under construction”. If you have links to suggest, I will examine them and put them up in my own time. Please feel free to post suggestions.

Introductory Material:

Agile Axioms
Agile Manifesto
The OpenAgile Primer
OpenAgile Resources and Presentations – English & Chinese available
Agile Work Cheat Sheets and White Papers – Berteig Consulting Inc. [pdf]

Agile Software Focus:

Extreme Programming
Methods and Tools
The Scrum Primer [PDF]
A Scrum Primer – Report from Yahoo! [PDF]
Scrum and XP from the Trenches
Scrum and Kanban
Control Chaos – Ken Schwaber and The Scrum Methodology
Agile Software Development by Alistair Cockburn
Agile vs. Lean – Thad Scheer
No Silver Bullet by Frederick Brooks
Agile Planet – agile blog aggregator
Buildix – agile software dev tools on a CD
Agile Forums
Implementing Scrum

Project Management:

Agile Project Management with Scrum – Ken Schwaber
Project Management Institute
Agile Project Management Yahoo! Group
Burndown and Burnup Charts
Huge List of Software Project Management resources
Scrum Alliance – Agile Project Management and Training
Project Management Resources – by Michael Greer. I don’t agree with everything on this site, but if you are looking for traditional PM stuff this is a good place to go.

Lean and Theory of Constraints:

Lean Software Development – Mary and Tom Poppendieck
Evolving Excellence – by Kevin Meyer, Bill Waddell, Dan Markovitz NEW!
Theory of Constraints – Eliyahu Goldratt
Agile Work for Flow Projects – Mishkin Berteig
The Toyota Production System
Practice Without Principles – TPS Without the Toyota Way – Victor Szalvay
Agile Work Uses Lean Thinking – Whitepaper [pdf] by Mishkin Berteig


Agile Management Yahoo! Group
Slow Leadership – the opposite of Agile?
Adaptive Management – Jeffrey Phillips

Adult Education:

The Self-Educative, Narrative and Metaphorical Faculties of the Soul – Alexei Berteig (pdf)

Team Building:

The Wisdom of Teams: Creating the High-Performance Organization
Retrospective Patterns by William Wake
How to Win Friends & Influence People – Dale Carnegie

Community Development:

Corporate Culture:

Catastrophic Organizational Change – Tobias Mayer
The Corporate Culture Survival Guide – Edgar H. Schein
Good to Great (fastcompany article) – Jim Collins

Agile Services:

Berteig Consulting – Agile Work Coaching, Training and Consulting
CC Pace
Digital Focus
Israfil Consulting Services Corporation
Scrum Alliance
Tobias Mayer
David Chilcott
Joe Little
Michael Vizdos

Agile in Other Domains:

Extreme Project Management for Architects

Experiences and Stories of Applying Agile in Other Domains:

Agile Documentary Video Project
Agile Publishing

The following sections of material are based on the Agile Work Cheat Sheet.

We are Creators

Reality is Perceived

An Introduction to General Systems Thinking by Gerald M. Weinberg

Change is Natural

About “Resistance” by Dale H. Emery

Trust is the Foundation

Agile or Not Agile?
Trust and Small Groups

Empower the Team

Launching an Agile Team – A Manager’s Howto Guide

Amplify Learning

Abe Lincoln’s Productivity Secret – a nice little bit about being properly prepared (although caution should be taken not to over-prepare!)

Eliminate Waste

Self-Organizing Team

Variations on the Daily Standup – Rachel Davies
Scrum from Hell – William Wake
Team Formation Stages – Forming Storming Norming Performing

Iterative Delivery

Are Iterations Hazardous to Your Project? – Alistair Cockburn

Adaptive Planning

Maximize Communication

Edward Tufte’s web site with lots of great info about the visual display of information
Human Tools for effective communication
Eight Barriers to Effective Listening
Facilitation Skills [pdf]

Test-Driven Work

The Qualities of an Ideal Test

Appropriate Metrics

Appropriate Agile Measurement White Paper (pdf)

Removing Obstacles

The Art of Obstacle Removal

Intros and Summaries

The Seven Core Practices of Agile Work

Please share!

2 thoughts on “Agile Resources”

  1. I need advice on how many repeats of ‘given / when / then’ entries are best put in acceptance criteria, in the same scenario.

    For example, ‘As an online operations employee, I want to delete store type information, so that outdated store types are no longer present for association with store information’

    Would one put in the acceptance criteria, each of the steps to be followed, like this :

    1. Given that the employee is logged into CMS and the Store Type Management page is displayed, when the grid is displayed, then an option to delete store type information should be available through a delete button in the action column in each store type’s row

    2. Given that the employee is logged into CMS and the Store Type Management page is displayed, when the delete store type button is clicked, then a confirmation popup should appear stating the type which is about to be deleted along with yes and no buttons

    3. Given that the delete button has been clicked and the confirmation popup is displayed, when the yes (confirmation) button is clicked, then it must be validated that the relevant store type is not linked to a store.

    4. Given that the yes (confirmation) button has been clicked, when the relevant store type is verified not to be linked to a store, then it must be deleted from the database table and a success message should be displayed.

    5. Given that the yes (confirmation) button has been clicked, when the relevant store type is verified to still be linked to a store, then an error message should be displayed stating that the type is still associated with a store’s information and no changes are made to the database.

    6. Given that the delete button has been clicked and the confirmation popup is displayed, when the no (confirmation) button is clicked, then the popup should close and no changes are made to the database

    This seems WAY too wordy. Please advise..

    1. Hi Phil,

      Thanks for writing. I strongly recommend that acceptance criteria not be written down in long form anywhere. Instead, use a word or two for each acceptance criterium and then use ongoing conversation with the team as well as automated acceptance tests (e.g. Specification by Example) to share and capture important details. You are right: it IS way too wordy.

Leave a Reply

Your email address will not be published. Required fields are marked *