It finally clicked, what nostr:nprofile1qqs06gywary09qmcp2249ztwfq3ue8wxhl2yyp3c39thzp55plvj0sgprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qguwaehxw309a6xsetrd96xzer9dshxummnw3erztnrdakj7qgmwaehxw309amksetpwshxsctswpuhgctkv4exutnrduhsw0qlr4 has been writing about in regards to Agile methodology. I've been developing in features, rather than user stories. Time to break down the work further and deliver one user story at a time.

Keep an eye out for more PRs on the #aedile, #alexandria, and other #gitcitadel repos as well realign to more bite-sized chunks of work.

Reply to this note

Please Login to reply.

Discussion

Been thinking a lot about this lately, breaking work down to very small pieces is a really important step. Helps understand what is truly the smallest releasable piece to batch together. Then once you start releasing faster due to bei mg able to easily identify small reliable chunks you start creating momentum. Trying to bite off huge chunks to release prevents this momentum, it’s such a slog.

Yes I think that's right. And momentum is what my team needs right now. Time to get this train rolling.

Some of the best defects I've found have been from pretending to be a user (veteran, new, etc) with a specific goal (generating a year-over-year profit-loss report, adjudicating a claim with Coordination of Benefits, adding a transportation dept to an existing accounting structure, etc).

Sit in the driver's seat. Have a destination, and a reason to get there; then observe what the process entails.