Webinar: Agile Transformation — Defining Agile
Dates: Mar 23
Location: Webinar
Course Location:
Details to be sent.

Webinar: Agile Transformation — Defining Agile

Short Description: In this webinar we will discuss using the play or pattern — of defining agile to help move the Agile Transformation forward.

This webinar is another in a series to help you with a tough problem — making your Agile Transformation more successful in whatever role you have. The webinar will last about one hour.

We expect to have between 20 and 50 people. (No more than 50.)

We think a fair amount of the value is in the discussion. We will enable a few people to ask questions and discuss/comment. (We expect to have a fairly good group, so allowing everyone to talk will not be possible.)

Date: Friday, March 23
Time: 11 a.m. to noon EST. We will start promptly.

There are many things we can do to make an Agile Transformation work. In fact, like any good offensive coordinator in American Football, we need a playbook.

Last time we discussed 3 PlaysThis time we will focus on one play:

We will very briefly define this play, and explain it a bit. Then we will discuss each part or aspect of the play.

Collateral Benefits: You earn 1  PDU and 1 SEU for this hour.


  1. Short Intro — 5 minutes
  2. What is the idea?  — 5 minutes
  3. Discuss — 5 minutes
  4. How to define — 5 minutes
  5. Discuss — 5 minutes
  6. How to use the definition — 5 minutes
  7. Discuss — 5 minutes
  8. Things to watch out for — 5 minutes
  9. Discuss — 5 minutes
  10. General discussion — 10 minutes
  11. Next sessions/closing — 5 minutes

A few comments:

  • What is the idea? -—A key topic here is the content of the definition of agile. We will not have time to discuss each line item listed in the blog post.
  • How to define — This gets at the people and process of pulling together the definition.
  • How to USE the definition — The short answer: To help everyone improve. Or, at least, to reduce the confusion.
  • Things to watch for — Several things, but including not being dictatorial and allowing some teams to be different (when it makes sense). More carrot, less stick.
  • General discussion — Here it would be nice if we took two situations and described how this might work. So, I hope some of you will be ready to do that, and then get comments and suggestions.

We want your real-world experiences and your real-world questions. For those who have particular experiences to share or questions you must ask, please email Retta and she will discuss them with Joe.

Please complete a 1-page “business case” so we can quickly understand your specific situation, and then we all can respond and comment more usefully. (This is not required of everyone, but I expect 10 people to do it.) Here is the suggested format. You may color outside the lines — just don’t go crazy.

Notice that we are forming a learning community.

Note: We do not recommend being dictatorial or completely inflexible about Scrum or Agile. We do recommend rigor and useful conversations, such as, “Why aren’t we doing that? Do we have a good reason?” This distinction will be discussed.

Come and learn and contribute.