Artwork

Sisällön tarjoaa AgileThought and Dan Neumann at AgileThought. AgileThought and Dan Neumann at AgileThought tai sen podcast-alustan kumppani lataa ja toimittaa kaiken podcast-sisällön, mukaan lukien jaksot, grafiikat ja podcast-kuvaukset. Jos uskot jonkun käyttävän tekijänoikeudella suojattua teostasi ilman lupaasi, voit seurata tässä https://fi.player.fm/legal kuvattua prosessia.
Player FM - Podcast-sovellus
Siirry offline-tilaan Player FM avulla!

Are You Fluent in Agile? with James Shore

41:29
 
Jaa
 

Manage episode 348656787 series 2502498
Sisällön tarjoaa AgileThought and Dan Neumann at AgileThought. AgileThought and Dan Neumann at AgileThought tai sen podcast-alustan kumppani lataa ja toimittaa kaiken podcast-sisällön, mukaan lukien jaksot, grafiikat ja podcast-kuvaukset. Jos uskot jonkun käyttävän tekijänoikeudella suojattua teostasi ilman lupaasi, voit seurata tässä https://fi.player.fm/legal kuvattua prosessia.

This week, Dan Neumann is delighted to be joined by a new guest, James Shore, the author of The Art of Agile Development and co-creator of the Agile Fluency Project with Diana Larsen. His contribution is invaluable to the Agile field.

In this episode, James talks about the second edition of The Art of Agile Development, which was published in 2021. This edition is a fully rewritten version that shows the influence of the Agile Fluency Model, including the different zones Agile Teams can occupy, such as Focusing, Delivering, Optimizing, and Strengthening, and practices for Teams to become fluent in each area.

Key Takeaways

● James rewrote The Art of Agile Development for its second edition.

○ He rewrote the book around the ideas of the Agile Fluency Model.

○ It includes updated practices.

○ In the book, you can find out how to influence people to make a change, to try Agile ideas, and even advice when you are in a situation where you are not very Agile.

● What is the Agile Fluency Model?

○ There are four different zones that teams or organizations can occupy: Focusing, Delivering, Optimizing, and Strengthening. A Team can exhibit fluency in any of these zones.

○ A behavior is fluent when you can perform it unconsciously, naturally, as a default behavior.

○ A Team can demonstrate fluency but only the Organization can make it possible.

○ It is not a maturity model, you can be fluent in one of the zones and not the others.

● The Agile Goal:

○ For many organizations, it may be Focusing plus Delivering together.

● James talks about the structure of the book.

○ The first part of the book is about how to introduce Agile ideas.

○ Most of the book is about the practices for the Focus and the Delivery zone.

○ Alternatives and experiences can be found at the end of every practice.

● Learn the rules, break the rules, and then, ignore the rules.

○ After learning the rules you have to experiment because every Agile Team goes through a unique situation and process.

● How long does it take to achieve a level of fluency?

○ It takes time to become fluent.

○ In general, it takes two to six months to reach Focusing fluency. Have under consideration that there is a one-to-four-month period of decrease in performance while people learn.

○ During two to six months, performance will be affected while trying to reach fluency in Delivering in an expected period from three to 20 months.

○ When Optimizing fluency it takes one to two months of performance affectedness and three to nine months for reaching fluency in this area.

○ It takes one or two years to deliver reliably.

○ All these time frames overlap.

Mentioned in this Episode:

Follow James Shore.

Check the second edition of The Art of Agile Development.

Agile Fluency Project

FAST Agile

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

  continue reading

312 jaksoa

Artwork
iconJaa
 
Manage episode 348656787 series 2502498
Sisällön tarjoaa AgileThought and Dan Neumann at AgileThought. AgileThought and Dan Neumann at AgileThought tai sen podcast-alustan kumppani lataa ja toimittaa kaiken podcast-sisällön, mukaan lukien jaksot, grafiikat ja podcast-kuvaukset. Jos uskot jonkun käyttävän tekijänoikeudella suojattua teostasi ilman lupaasi, voit seurata tässä https://fi.player.fm/legal kuvattua prosessia.

This week, Dan Neumann is delighted to be joined by a new guest, James Shore, the author of The Art of Agile Development and co-creator of the Agile Fluency Project with Diana Larsen. His contribution is invaluable to the Agile field.

In this episode, James talks about the second edition of The Art of Agile Development, which was published in 2021. This edition is a fully rewritten version that shows the influence of the Agile Fluency Model, including the different zones Agile Teams can occupy, such as Focusing, Delivering, Optimizing, and Strengthening, and practices for Teams to become fluent in each area.

Key Takeaways

● James rewrote The Art of Agile Development for its second edition.

○ He rewrote the book around the ideas of the Agile Fluency Model.

○ It includes updated practices.

○ In the book, you can find out how to influence people to make a change, to try Agile ideas, and even advice when you are in a situation where you are not very Agile.

● What is the Agile Fluency Model?

○ There are four different zones that teams or organizations can occupy: Focusing, Delivering, Optimizing, and Strengthening. A Team can exhibit fluency in any of these zones.

○ A behavior is fluent when you can perform it unconsciously, naturally, as a default behavior.

○ A Team can demonstrate fluency but only the Organization can make it possible.

○ It is not a maturity model, you can be fluent in one of the zones and not the others.

● The Agile Goal:

○ For many organizations, it may be Focusing plus Delivering together.

● James talks about the structure of the book.

○ The first part of the book is about how to introduce Agile ideas.

○ Most of the book is about the practices for the Focus and the Delivery zone.

○ Alternatives and experiences can be found at the end of every practice.

● Learn the rules, break the rules, and then, ignore the rules.

○ After learning the rules you have to experiment because every Agile Team goes through a unique situation and process.

● How long does it take to achieve a level of fluency?

○ It takes time to become fluent.

○ In general, it takes two to six months to reach Focusing fluency. Have under consideration that there is a one-to-four-month period of decrease in performance while people learn.

○ During two to six months, performance will be affected while trying to reach fluency in Delivering in an expected period from three to 20 months.

○ When Optimizing fluency it takes one to two months of performance affectedness and three to nine months for reaching fluency in this area.

○ It takes one or two years to deliver reliably.

○ All these time frames overlap.

Mentioned in this Episode:

Follow James Shore.

Check the second edition of The Art of Agile Development.

Agile Fluency Project

FAST Agile

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

  continue reading

312 jaksoa

Kaikki jaksot

×
 
Loading …

Tervetuloa Player FM:n!

Player FM skannaa verkkoa löytääkseen korkealaatuisia podcasteja, joista voit nauttia juuri nyt. Se on paras podcast-sovellus ja toimii Androidilla, iPhonela, ja verkossa. Rekisteröidy sykronoidaksesi tilaukset laitteiden välillä.

 

Pikakäyttöopas