Development Team
The Development Team process manages the planning, prioritization, and visualization of all activities related to the development of software and hardware components. There are multiple development teams in each development stream.
The development teams focus on the actual development of hardware and software. Their work is synchronized and aligned with the system and development streams by the common SPI cadence, which splits each increment into (normally) six sprints. For each sprint, the different teams break down features into stories and tasks to be implemented.
Note: Stories have two purposes - the first is to define small, deliverable pieces of software or hardware - and the second is for planning purposes.
Process overview
Principles
- Ensure the team backlog is ranked.
- Plan the iteration/sprint.
- Visualize work.
- Coordinate at daily stand-up meetings.
- Demonstrate value.
- Improve the development process.
- Build quality in.
- Ensure adherence to DoR and DoD.
Activities
Artifacts
| Artifact | Description | RACI | Receiver | Comments |
|---|---|---|---|---|
| Iteration Goal | Summary of business and technical goals for the iteration that the agile team agrees to accomplish | (R): Team (A): Scrum Master (C): - (I): - | Team | - |
| Team Board | Visualize the status of team progress, physical or digital board | (R): Team (A): Scrum Master (C): - (I): - | Team | - |
| Story | A (user) story is estimated and ranked in this process. For details about contents, see the "requirements" process. | (R): Team (A): Scrum Master (C): - (I): - | Team | - |
| Task | Piece of estimated work (hours) for a team member. It is a work item in Azure DevOps. | (R): Team (A): Scrum Master (C): - (I): - | Scrum Master | - |
| Team Backlog | Contains estimated and ranked stories and enablers originating from streams' backlog and additional stories from the team's local context. | (R): Team (A): Product Owner (C): - (I): - | Team | - |
| Impediment | Anything that keeps the team from getting work down or slows velocity. Identified in Daily Stand-Up. | (R): Team (A): Scrum Master (C): - (I): - | Team | - |
| Risk | Can cause future problems, loss, or threaten progress - but has not happened yet | (R): Team (A): Scrum Master (C): - (I): - | Team | - |
Dependencies
Details
The development team process focuses on lean-agile planning and execution. The process ensures the teams plan, execute and deliver according to expectations. The development teams are aligned to the increments by the stream.
Master Processes
The development team process belongs to the "master processes" responsible for continuous planning and execution. It takes the required activities defined in the functional processes (e.g., requirements, architecture, and test) and adds them to the iterations.
The development teams can use Scrum or Kanban, depending on their needs. Irrespective of the agile method, the team needs to sync to the common cadence in the stream. Deliverables and demos need to be prepared by the team.
Cadence view
The cadence view shows the process activities and the increments. Many of the activities are executed in parallel and not always in a sequence.
The team's cadence is aligned to fit into the PI increments. The iterations are, in most cases, 3 weeks, but they can be shorter or longer as long as they fit into the increments.
Flow view
This view shows an overview of one iteration (2-3 weeks).
HW Development activities have a longer cycle than 2-3 weeks before delivery - and need more than an iteration to be completed.
The flow view shows the process activities and the logical sequence with decision points. It makes it easier to understand the flow and the relationship between the activities.
