This is an interesting Webinar. Most of the Senior Living Communities I've been speaking with are facing some challenges on the labor space. This will give you good insights on how to build your strategy.
We've had an AMAZING first half of the year. Here's a press release where we cover everything we've been able to accomplish in 2024 so far!
Thank you all so much for your continued support.
https://vist.ly/3ef25
I typically go back to first principles whenever working with new teams or new clients. Instead of trying to have them be as knowledgeable about XP or agile development practices as us, I focus on the core principles. Then show how they were applied them during retros. You can then use this evidence to tell a story in stakeholder meetings.
One of the big ones that comes up is collaboration over documentation. Obviously you're still gonna need some documentation. Typically we aim on the lighter side (think 1 pagers). ideally executable documentation, whether that's through Postman scripts or something more sophisticated like Jupiter notebooks.
One of the ways this typically takes place is by introducing Pair Programming sessions as well as Group Sessions (ie. Mobbing). Every time we have a retro after these sessions team members always come away surprised at how much they’ve learned. Another beneficial side effect is that the teams become more cohesive.
Teams that are able to effectively communicate are always going out perform teams that act as a band of mercenaries. When you have teams that don't collaborate together, then you're gonna see behavior such as cowboy coding and hero worship.
#xp#agile#softwaredevelopment#consulting#leadership
response to a question on my quote "We wrote the manifesto to avoid the codification of practices":
hi, thanks - i gave it in my reply to Henrik in that subthread
https://lnkd.in/e6nujs-v
another way to say, my preferred way:
we all agreed to disagree at the level of daily explicit recommendations: Steven Mellor loved to model, Kent Beck hated to model; I liked deliveries every 2 months (back then), Ward Cunningham liked deliveries every week or two, etc.
so how to find a common place? : "Surely there is a description that allows us to agree on the general direction and disagree on daily actions?"
the answer lies in "levels of precision", like pi is roughly 3 at the first level of precision, good enough to indicate it isn't 10,000; then at the second level of precision you can get away with 22/7 for some calculations, but need a third or fourth level of precision, like who knows, 20 decimal places for some calculations.
so:
at the first, roughest level of precision, we have one one word: "Agile". Just one word, but it indicates something, a general difference (I do like "Adaptive" as contrasted with "Predictive", as making a direction clearer, but that really also comes at some 2nd level of precision, when we get talking about details).
We could all agree we wanted agility, no rigidity. Level 1
Level 2: we found those values, and put the "over" to indicate the opposite direction. Values are directions. Unanimous agreement at level 2. No practices anywhere in sight, just value centers.
Level 3: we named 12 principles, started having a few disagreements. Still no practices.
after that we knew we would not agree completely, nor did we want to . Practices are down at level 4 or 5, things that change from project to project and person to person.
Practices vary all the time, values are steady (and note the last sentence in the values page, where we said the items on the right are appropriate sometimes).
I hope that answers your question
Since I kinda was a long-time Student before I started working in the IT Business (kids need to be feed 😊), work became more than a 9-5 routine, when I got in touch with the agile manifesto, because I saw so many relations with experience! So just a personal big THANKS for this enlightment 🔥, Alistair Cockburn!
As a part of a great Kanban Team for online Display advertising, trying to find out how this thing called Agility might work in practice…and it did thanks to great mentors and Coaches: Jörg Harm, Silvana Saveri Reiner Kuehn! 🙏
Since then I‘ve been working with, in and on agile contexts with great people in commited companies!! 👏👋👍
(if you think you could be adressed, you probably are 😊).
🎁I will share some resources📖, you might find helpful 💡and some details about my agile-related experience 🗣️, you might find entertaining🤣 in the comments 💬
Feel free to comment and share yours too!
🔒I decided to offer the quintessence of my personal path with Agility and related fields on an hourly basis as a Coach: FEEP Coaching, please get in touch if your interested.
I typically go back to first principles whenever working with new teams or new clients. Instead of trying to have them be as knowledgeable about XP or agile development practices as us, I focus on the core principles. Then show how they were applied them during retros. You can then use this evidence to tell a story in stakeholder meetings.
One of the big ones that comes up is collaboration over documentation. Obviously you're still gonna need some documentation. Typically we aim on the lighter side (think 1 pagers). ideally executable documentation, whether that's through Postman scripts or something more sophisticated like Jupiter notebooks.
One of the ways this typically takes place is by introducing Pair Programming sessions as well as Group Sessions (ie. Mobbing). Every time we have a retro after these sessions team members always come away surprised at how much they’ve learned. Another beneficial side effect is that the teams become more cohesive.
Teams that are able to effectively communicate are always going out perform teams that act as a band of mercenaries. When you have teams that don't collaborate together, then you're gonna see behavior such as cowboy coding and hero worship.
#xp#agile#softwaredevelopment#consulting#leadership