A message to myself in 2019

A message to myself in 2019

Back in 2019, in my former company we were doing quarterly releases. For a period also bi-monthly. We were working with Scrum, more or less, and we had bi-weekly sprints as one does.

The dreaded sprint.

And most of us were "why the hell do we have to do this bi-weekly shit if we're only releasing quarterly", me included. I even called it "laws of physics". If you know you're 100 meters away from the edge of a cliff, you can bloody surely go another 90 without stopping. All the PBIs have to be done by the end of the release - not by the end of the sprint FFS!

We're not gonna gather any kind of customer feedback on sprint end, we're not going to use them to course-correct the release (unless something really went south, which was sometimes the case, but we never used sprints as a lever or tool to course correct), we're not gonna review the backlog with users and stakeholders to determine what the next best thing to build is and if we're on the best possible course. So why bother having them?

No alt text provided for this image

My manager surely recalls this ... Hi Pavlo, sorry for being such a royal PITA :)

So here's the message to myself

You dumb fuck, when did you forget that delivery is the best medicine you can give to a sick team?

  • Can't finish a story in one sprint? Practice splitting so you can deliver it in chunks!
  • Can't integrate the backend and frontend fast enough in one sprint? Then start pairing between backend and frontend on a daily (hell, hourly if you need to!) basis in order to deliver the whole vertical slice in one sprint!
  • Specialised roles are the reason you have too long mini waterfalls in the sprint and 2 weeks isn't enough? You guessed it, fix that shit however you can (pairing helps, yes) in order to deliver in 2 weeks!
  • You're using your mock data you created to test the feature that breaks when it starts to work with prod data? Deliver to prod-like before the end of sprint!

So, shut up with the laws of physics and use the delivery as a lever to fix your process and your team!

Frequent delivery will most likely surface all the problems your team has. Applies for young and mature teams. You will maybe fall into an existential crisis before you start delivering, but such is life. Roll with the punches.

No alt text provided for this image


Ozren Crnogorac

Agile Coach / Scrum master at One Backlog

3 年

Great one Darko! It’s a medicine to get healy feedback! It could take you to the spaces unknown. ??

要查看或添加评论,请登录

Darko ?poljari?的更多文章

  • Scrum, "by the book"

    Scrum, "by the book"

    Many times I've seen teams struggle with Scrum. Many times I've seen "scrum, but" implementations.

  • Jack of all trades, master of none

    Jack of all trades, master of none

    ..

    1 条评论
  • Refactoring for business people

    Refactoring for business people

    Try calculating this without a calculator.: 1.

  • Business people and developers. The language.

    Business people and developers. The language.

    Recently I had a session with a couple of business people in my company and we had an interesting conversation. The…

  • O pregledu koda

    O pregledu koda

    Mislim na praksu code review - evo kako to sretno izgleda kad prevedete na hrvatski :) ?ujem dosta ekipe da pri?a kako…

  • O preuzimanju odgovornosti

    O preuzimanju odgovornosti

    Obuzelo me ju?er razmi?ljanje o odgovornosti, i preuzimanju odgovornosti na sebe. Kako je to .

    1 条评论
  • Za?to su procjene uvijek krive?

    Za?to su procjene uvijek krive?

    Prvo i osnovno: procjene ne mogu biti krive. U sr? rije?i "procjena" ugra?ena je nesigurnost i prema tome to?na…

  • "Kako stojimo" - u waterfall projektima

    "Kako stojimo" - u waterfall projektima

    U zadnje vrijeme relativno ?esto me pitaju kako stojimo na projektu. Produkcija se bli?i, neki rokovi ve? pro?li i…

  • Software is a 100% thing.

    Software is a 100% thing.

    Disclaimer - this is a rant, and there's harsh language ahead. Let me ask you something.

  • Scrum is a challenge

    Scrum is a challenge

    I've been thinking about how many Scrum teams actually aren't Scrum teams, and why that is so. Stuff that usually…

社区洞察

其他会员也浏览了