Conversation

Notices

1. Embed this notice
   Jeremy Kahn (trochee@dair-community.social)'s status on Friday, 15-Dec-2023 07:28:04 JST Jeremy Kahn

   I propose that 2024 be the year of no more "sprints".

   organize your work into "strolls", and connect up those strolls into "rambles".

   aw dammit now I want a book pitch for the "randonneur's guide to software development".

   • GreenSkyOverMe (Monika) repeated this.
   • Embed this notice
     Jeremy Kahn (trochee@dair-community.social)'s status on Friday, 15-Dec-2023 07:28:01 JST Jeremy Kahn

     in reply to

     • egregious philbin

     @ieure

     AND ANOTHER THING

     it's RIGHT IN THE NAME that you shouldn't have back-to-back sprints all year long

     unless you want to kill your runners

     which is something that a lot of shops seem okay with :(

   • Embed this notice
     egregious philbin (ieure@retro.social)'s status on Friday, 15-Dec-2023 07:28:03 JST egregious philbin

     in reply to

     @trochee At more than one Agile shop, I have successfully agitated to interleave sprints with "moseys," generally on a two-sprint-one-mosey cadence.

     The mosey is where you work on technical debt, documentation, or polish.

     Not an Agile fan, but this honestly helps a lot.

     GreenSkyOverMe (Monika) repeated this.
   • Embed this notice
     Bill Jorth (wdjorth@mastodon.online)'s status on Friday, 15-Dec-2023 09:10:04 JST Bill Jorth

     in reply to

     • GreenSkyOverMe (Monika)
     • egregious philbin

     @ieure @GreenSkyOverMe @trochee Those mosey action details are critical to software excellence. Too often the documentation is lacking, not tested, code is allowed to be sloppy resulting in excessive maintenance, and security flaws.