Agile in the Ether #19 / 14th February

Was on: Friday 14th February
12:30pm
(Universal Time Coordinated / UTC) which is also
12:30pm (Greenwich Mean Time / GMT)

We talked about…

  • Advice on visually measuring outcomes that are organisational change related not product or service
  • Estimating – yay or nay?
  • Minimal viable teams
  • What are your top ways to create a sense of responsibility for time spent on developing features

One Comment

  1. Notes and comments from the meetup

    Advice on visually measuring outcomes that are organisational change related not product or service

    Tool we to measure engagement: https://officevibe.com/


    
https://labs.spotify.com/2014/09/16/squad-health-check-model/


    
Accelerate includes organisational culture and uses Westrum


    
https://www.amazon.co.uk/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339


    
https://www.atlassian.com/team-playbook/health-monitor


    
https://blog.crisp.se/2019/03/11/jimmyjanlen/health-checks-for-teams-and-leadership


    
https://www.teamretro.com/health-checks/


    https://www.amazon.co.uk/Five-Dysfunctions-Team-Leadership-Lencioni/dp/0787960756

    Estimating – yay or nay?

    https://pragprog.com/book/gdestimate/software-estimation-without-guessing


    
my fave approach to estimation:
https://lizkeogh.com/2013/07/21/estimating-complexity/


    
https://jeffgothelf.com/blog/velocity-should-be-renamed-future-tech-debt/

    
Coming from a dev background, one of the reasons that devs can be reluctant to give estimates is that all too often what started as an estimate then becomes a hard deadline given to customers/stakeholders that they are then pressured to stick to.


    Minimal viable teams

    
“A team is a small number of people with complementary skills who are committed to a common purpose, set of performance goals, and approach for which they hold themselves mutually accountable.” – Katzenbach & Smith.


    
https://emilywebber.co.uk/agile-team-onion-many-pizzas-really-take-feed-team/


    What are your top ways to create a sense of responsibility for time spent on developing features

    https://medium.com/productmanagement101/spotify-squad-framework-part-i-8f74bcfcd761

    Calibrated estimates https://tcagley.wordpress.com/2016/01/16/how-to-measure-anything-chapter-5-calibrated-estimates-how-much-do-you-know-now/

    
https://twitter.com/branaby/status/1226042896488574976 “We did a sprint retro yesterday, and one thing we considered was how we hindered other people. And it was great! So often we look at the people and processes that got in *our* way, but how often do we reflect on the damage that *we* are doing?”


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.