hey peeps, are you still using mastodon? i've been away for a while

@omartwotone nope, you can't diagram anything in complex systems. by trying to template the daily scrum we got the three questions ee can't get rid of now, and that format is basically killing the agility of the team

@thomas_michl very insightful, and i like the call to action in conclusion. we have to step up and lead by example

@vlentz yes. when defining them, insiat that they're SMART (specific, measurable, attainable, relevant, time-bound).

@mikebrew i attended scrum.org's PSK training and read a lot of material. i've described my prep workflow here https://www.linkedin.com/pulse/psk-i-exam-really-hard-luka-mati%C4%87/ and you can find my reading list and annotations here https://hypothes.is/users/skribomatic?q=tag%3APSK

@kironbondale@mastodon.world @thatagile nothing happened. ways are methods. scrum doesn't prescribe methods – it does prescribe feedback loops, accountabilities, artifacts and commitments.
and I'm totally fine with people experimenting with frameworks, just don't call it scrum if it gets rid of any of the minimal requirements of that specific framework

@kironbondale@mastodon.world @thatagile yup, i understood that but i still disagree :) namely – speaking of the mechanical application of scrum – it has a name, #zombiescrum and strategies how to overcome it. but, with regards to scrum, i align with the professional scrum and agree that you can't call it scrum if you don't do it as it should be done. that's why the framework is lightweight and doesn't prescribe methods of work, just the frame and feedback loops.

@nevenjovanovic @nino mastodon mali, šokadiji nigdje kraja

@nino vrlo male :) idem otvorit instancu sokadija.global 😂

@nino zn'o sam, što bi rekla moja stara baka, ti po prezimenu da si negdje s područja brodske graničarske pukovnije. ja sam u županji odrasto

@nino ma jok. ja sam slavonac, a u nas je komšiluk najviša institucija 😊

@nino dobrojutro komšija!

I’m reading about #Scrum and this song by The 5th Dimension came on. How did they know the scrum values in 1968?

@alexschnapper if it can be of any help or use to you, i did a review of my prep and exam taking tactics https://www.linkedin.com/posts/luka-matic_psm-share-activity-6994203461479206912-l1PD?utm_source=share&utm_medium=member_android

🤞 that you make it

@kironbondale@mastodon.world @thatagile strongly disagree. i think it's fundamentally wrong to categorise #scrum / #kanban as processes&tools, when scrum is a framework and kanban is a strategy, and both are meant to enable acting on [all twelve] principles behind agile manifesto.
on the other hand, fetishism of JIRA, story points, velocity is – as i see it – what's wrong in the sense that processes and tools are prioritised over individuals and interactions

@thatagile let's rather have both. from my perspective, the questions are whether you introduce #scrum or #kanban first. e.g. i'm just starting #agile transformation of a small accounting/tax advisory team, and i'll start by introducing kanban to facilitate teamwork around the work items (instead of individual responsibility for small tasks). when we stabilise that, we'll see how to move forward. but the goal is to get to scrum with kanban developed inside the team.

@_ragozzine my favorite lesson was maximize the work not done 😀

@joejardim be open to listen to what their experiences have been to date. Working with a Scrum Master is an acquired taste. Hearing those experiences even though they may be unpleasant will give you some insights into how they were working before. I've had to comb through unmanaged and untracked projects. Observe before changing. Promote the benefit instead of the reason for the change. Your rule should be Listen to Understand instead of Listen to Reply.

I know how hard it was for me to prepare for this exam, so I've written a blog post to give insight into my prep #flow.
hopefully it'll help someone: https://www.linkedin.com/pulse/psk-i-exam-really-hard-luka-mati%25C4%2587

#scrum #scrumorg #kanban #PSK

@malcolm fyi, the 2021 #scrum guide switches from roles to accountabilities. so you can name the roles whatever you want, but those people still have to be accountable for some specific stuff. and, yes, agile teams might not need those accountabilities, but you can't have #ProfessionalScrum without them.