Conversation

Notices

1. Embed this notice
   joep schuurkes (joeposaurus@chaos.social)'s status on Monday, 11-Sep-2023 21:35:18 JST joep schuurkes

   in reply to

   • Dawn Ahukanna

   @dahukanna That starts to look a lot like waterfall, even though you're pointing to your build&test team to prove you're doing Agile.

   It makes me want to try out a three- or four-week sprint, that has a clear goal for the sprint, but that leaves a lot more leeway for discovery in how to achieve the goal during the sprint, than the currently common two-week sprint. (2/2)

   • Embed this notice
     joep schuurkes (joeposaurus@chaos.social)'s status on Monday, 11-Sep-2023 21:35:21 JST joep schuurkes

     in reply to

     • Dawn Ahukanna

     @dahukanna A two-week sprint in which you have to deliver a bunch of stories, is rather short. So you want every story fully refined before it gets into planning. And once the code is written and tested, it's hard to fit in a UAT, writing documentation, etc.

     So you end up with groups of people who have to prepare the sprint beforehand (user research, design, architecture, etc) and who have to do post-sprint work (UAT mgt and support, tech writers, etc.). (1/2)

   • Embed this notice
     Dawn Ahukanna (dahukanna@mastodon.social)'s status on Monday, 11-Sep-2023 21:35:22 JST Dawn Ahukanna

     in reply to

     @joeposaurus

     Interesting and I’m curious.
     Please could you expand on “to short sprints result in water falling”?

   • Embed this notice
     joep schuurkes (joeposaurus@chaos.social)'s status on Monday, 11-Sep-2023 21:35:23 JST joep schuurkes

     "You're waterfalling because your sprints are too short." - me at #FrogsConf