Do-Test-Review: Task workflow

In my workflow I like transparency and the ability to quickly asses what’s going on, what is worked on and what’s currently in wait queue. Few statuses glued together aren’t a workflow and over engineered complicated process will quickly become a burden.

I like clear distinction between DO and WAIT steps. Ideally you have just one task in DO state, but it should not be a restriction. The fewer steps the better but at least as many to see if we are on track to complete the project on time.

I came to like the workflow below.

It has verification steps for QA and Product Owner and gives insight as what is going on: Is there enough to start the work? Are issues being processed quickly enough? Are we focused or spread out? Is quality OK or we have to improve a lot?

Leave a Reply

Back to Top