Ken Ritchie
@classmaker
Agility Coach/Trainer. CSM, CSPO, PMI-ACP, PMP, ICP-ACC, SAFe SPC, 6σGB, TKP. Org Mindset Lean-Agile Enterprise Coach. Teamwork Facilitator. ENFP Dad ;-)
You might like
Back to the Future, at #Agile2013, 10 words, from @arlobelshee.
Agile in 10 words: Work tiny. Prove it. Get done. Learn constantly. Work together. Note: the tech is first.
“Most teams archive too much. We err on the side of archiving everything, because we can. But when we archive everything, we make the things we truly need harder to find.” - @ttorres bit.ly/3qWHVWu #prodmgmt #ux #engineering
I love this book! An amazing book on getting mentors was released last week, Mentor to Millions. I was told it's 99 cents on Kindle until the end of TODAY. click.convertkit-mail.com/zludmkgw2cnh5v…
With all the people working remote, you may want to remember to take care of the social part of work as well. We sometimes undervalue the need for that. One example can be to pair up and have coffee/tea breaks together over video. That feels good when you are home alone :)
Try the magic of *cadence* : a recurring whole-team slot; then add just enough agenda just in time. No more hunting! ;-)
I feel like I just spent my whole day looking for slots in people's calendars, so we can talk.... For a whole team it seems impossible
You often have to buy yourself some space away from the crazy pressure before you can exercise patience. Pick one thing, empower the team, shield them from the pressure. Use this success to gain trust from the pressure source. Flip that trust into more patience.
It's simple really — ☑️ Hire smart, motivated people ☑️ Tell them what needs to be achieved, not what you want them to do ☑️ Provide the tools, support and space they require ☑️ Step forward when they need you to, otherwise stand back ☑️ Be patient ☑️ Watch the magic happen
The word “unit” in “unit-testing” usually just means “small”. Other than that, the word has no agreed definition. Some TDDers call them micro-tests to stress the smallness. I prefer “programmer tests” because, using TDD, they are written by programmers for programmers.
A jelled Agile software development team can be like this, also.
Improv actors don’t know what is going to come up, but whatever does, they are determined to accept, respect, & add to it. Surprising results emerge when wehave a yes, and mindset in the team; nothing is impossible, nothing can stop us, & the creativity and energy is immense.
1/ The Phoenix Project #ebook is *free* today (Dec 19) on @amazon & other bookseller sites. If there’s someone you think should read it, now’s your chance. Retweet + tag your friends, colleagues, bosses. Link: itrevolution.com/free-the-phoen… (A Thread) @RealGeneKim @kevinbehr @gspaff
I wish everyone in a leadership/mgmt position who is in a position to measure stuff would read Measuring & Managing Performance in Organizations (fondly MMPO) by Austin + what ever @t_magennis has posted about metrics. And his book on this topic, when it comes to life.
Bravo!!! When I make my heavenly escape you my lift my cold, dead pinky off that real, live ESC key. Until then, I’m on it! ;-)
Indeed, we (re)plan often, even daily: just enough, just in time!
The notion that there is no planning in Agile is remarkably ignorant. Planning is the core practice of Agile. Observe, Plan, Execute, Evaluate. Over and over and over.
An awsome statement of Agile Values youtube.com/watch?v=mvyqXA…
youtube.com
YouTube
Agile Nation: New Zealand's response to terrorism | Rashina Hoda |...
Today we celebrate the anniversary of OOPSLA 1995, when the first paper on #Scrum was delivered. Thank you Ken, Jeff and everyone who has made Scrum a wonderful way to improve how people deliver products over the past 24 years. Here's to the next 24! ow.ly/86an50wMYIn
Just like there is value in NOT doing some work (the art of work not done), there is value in the charts and metrics you DON'T make/track. Every chart and dashboard should support decisions leading to a specific outcome. #NoChartsWithoutAnObjective
Bit late after starting features to ask "when will it be done?" It will be done when it's working and complete enough to get feedback. Better idea to do small incremental features so "it's done sooner" than worry about started work status. Get better splitting and learning fast.
Learning from experimentation leads to improvements. A little + a little + a little more = a lot! Or maybe operator is multiplication, not simple addition, like compound interest? That can change the game.
Picard management tip: Even without game-changing results, experimentation is time well spent.
Inverse. (Re)form the org around the desired architecture. And let emergent architecture incorporate learning (retrospectives on a cadence).
Yes! We may minimize coupling and maximize cohesion. In a balanced way, while catering for some global/external constraints. Spotify teams formed around their architecture?
My rule of thumb is to exploit Conway’s Law rather than be victim to it. Figure out a broad strokes view of how different parts of your system should interact in an ideal world, and structure your teams around the same communication channels.
United States Trends
- 1. #River 5,879 posts
- 2. Jokic 28.6K posts
- 3. Good Thursday 19.2K posts
- 4. Rejoice in the Lord 1,316 posts
- 5. Lakers 52.6K posts
- 6. Namjoon 75.6K posts
- 7. FELIX VOGUE COVER STAR 10.5K posts
- 8. #FELIXxVOGUEKOREA 10.9K posts
- 9. #FELIXxLouisVuitton 10.1K posts
- 10. #ReasonableDoubtHulu N/A
- 11. #AEWDynamite 52K posts
- 12. New Zealand 14.9K posts
- 13. Clippers 15.4K posts
- 14. Mikey 66.8K posts
- 15. Nemec 3,592 posts
- 16. Shai 16.6K posts
- 17. Thunder 40K posts
- 18. Visi 7,933 posts
- 19. Rory 8,504 posts
- 20. Ty Lue 1,312 posts
Something went wrong.
Something went wrong.