Provide a summary of this practice.
The Daily Workflow describes the major tasks in the Core Team’s working day. It applies primarily to the developer/user pairs as they convert stories into working software.
What is the overall goal or intention of this practice?
The Daily Workflow is used:
What are the schedule, cost, quality, frequency, performance or other expectations for completing this practice?
N/a. This ‘practice’ is only indicative.
What must have happened or been delivered for this practice to be considered complete?
What pre-conditions must be met before this practice is used?
This view shows a simplified version of this process. For full details, explanation and advice, click on the ‘Detailed process’ tab. For background such as entry and exit conditions, click on the ‘Context’ tab.
|1||Daily Stand-Up Meeting|
|4||Code & configure|
|1||Daily Stand-Up Meeting||Iteration Lead.||See ‘Daily Stand-Up Meeting‘ for the detailed process.|
|Backlogs are normally structured sequentially in priority order, so selecting each day’s work should not be a problem.|
|Agreed interpretation of story.|
|4||Code & configure||Developer.|
|5||Update records||Developer.||Updated logs & boards.|
Issues & risks
What are the key concerns in making a success of this practice?
- This Daily Workflow applies primarily to the developer/user pairs who turn stories into working software.
- Although stories are deliberately designed to be at a high level of granularity (i.e., a small, manageable element), they are not developed in true isolation.
- While developing an individual story, the Iteration Planning process, plus general team awareness, should ensure that the user and developer take into account the rest of the Iteration Backlog, any epic the story is part of, and any wider considerations.
- In other words, story implementation is like doing as jigsaw: the immediate problem – finding out how to deal with a single piece – is only ever part of a larger picture.
- Stories often take more than a single day to complete, of course. Where this happens:
- Start each new day by fixing the overnight defects.
- Try to complete whole units of functionality each day.
- Refactor at least daily (but ideally much more frequently).
- Re-integrate your code at the end of every day.
- Update the Backlog & Story/Task Board daily.
- Run automated tests every night.
- A standardised Daily Workflow is possible only because the Iteration Lead:
- Protects the developer/user pairs from interruption & distraction.
- Manages all communications between the team and its stakeholders.
- Manages the risks, obstacles and improvements on which smooth delivery depends.
- Prevents uncontrolled changes to the backlog.
- Where the day is disturbed, it should only be by pre-planned events such as:
- Meetings with External Team members.
- Unavoidable interruptions such as organisational events, meetings with external agencies(e.g., regulators), etc.
- Where disturbances begin to disturb the daily workflow regularly, the team should develop methods either to avoid such events or to absorb them efficiently.