Roles on DAD teams

This agile software development infographic example illustrates roles in disciplined agile delivery (DAD).
"Disciplined agile delivery (DAD) is a process decision framework that enables simplified process decisions around incremental and iterative solution delivery. DAD builds on the many practices espoused by advocates of agile software development, including Scrum, agile modeling, lean software development, and others." [Disciplined agile delivery. Wikipedia]
The infographic sample "Roles on DAD teams" was created using the ConceptDraw PRO software extended with the Scrum solution from the Project Management area of ConceptDraw Solution Park.

This agile software development infographic example was inspired by Mike Cohn's post "The Ideal Agile Workspace" from the Mountain Goat Software blog.
"... a list of all the things that ... should be visible within the ideal agile workspace:
* Big Visible Charts. ... the sprint burndown chart, showing the number of hours remaining as of each day of the current sprint. ... big visible charts showing the number of passing customer acceptance tests, the pass/ fail status of tests by day, sprint and release burndown charts, number of new stories introduced to the product backlog per sprint ...
* Additional feedback devices. ... a lava lamp that is turned on whenever the automated build is broken. ... flashing red traffic lights to indicate exceptional conditions such as an issue on a production server. ... ambient orbs and Nabaztag rabbits, which are wireless programmable devices that can also be configured to change colors, speak messages, or wiggle their ears as a team desires.
* Everyone on your team. Each person on the team should ideally be able to see each other person on the team. ...
* The sprint backlog. ... The best way to do that is by displaying the sprint backlog on a wall, ideally in the form of a task board A task board is usually oriented in rows and columns with each row containing a particular user story and one index card or sticky note for each task involved in that story. Task cards are organized in columns, minimally including “To Do” “In Process,” and “Done.” ...
* The product backlog. ... tack the index cards with those upcoming user stories on a wall where all can see them. ...
* At least one big white board. ...
* Someplace quiet and private. ...
* Food and drink. ...
* A window." [mountaingoatsoftware.com/ blog/ the-ideal-agile-workspace].
The infographic sample "Scrum workspace" was created using the ConceptDraw PRO software extended with the Scrum solution from the Project Management area of ConceptDraw Solution Park.

This agile software development infographic example was designed on the base of the Wikimedia Commons file: NL-scrum.jpg. [commons.wikimedia.org/ wiki/ File:NL-scrum.jpg]
"Sprint
A time period (typically 1–4 weeks) in which development occurs on a set of backlog items that the team has committed to — commonly referred to as a time-box or iteration" [Scrum (software development). Wikipedia]
The infographic sample "Scrum sprint cycle" was created using the ConceptDraw PRO software extended with the Scrum solution from the Project Management area of ConceptDraw Solution Park.

This agile software development infographic example was designed on the base of the Wikimedia Commons file: Simple-kanban-board-.jpg. [commons.wikimedia.org/ wiki/ File:Simple-kanban-board-.jpg]
This file is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported license. [creativecommons.org/ licenses/ by-sa/ 3.0/ deed.en]
"The basic Scrumban board is composed out of three columns: To Do, Doing and Done. After the planning meeting the tasks are added to the To Do column, when a team member is ready to work on a task, he/ she moves it to the Doing column and when he/ she completes it, he/ she moves it to the Done column. The Scrumban board visually represents the progress of the team. The task board columns are adapted and expanded based on the team's work progress. The most common add-ons include priority columns in the To Do section and columns like Design, Manufacturing, Testing in the Doing section." [Scrumban. Wikipedia]
The infographic sample "Scrum board suggesting to use Kanban" was created using the ConceptDraw PRO software extended with the Scrum solution from the Project Management area of ConceptDraw Solution Park.

The vector stencils library "Scrum arrows" contains 15 shapes.
Use it to design your agile software development diagrams and scrum infographics with ConceptDraw PRO software.
"Agile software development is a set of principles for software development in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, and continuous improvement, and it encourages rapid and flexible response to change. Agile itself has never defined any specific methods to achieve this, but many have grown up as a result and have been recognized as being 'Agile'." [Agile software development. Wikipedia]
The diagram shapes sample "Design elements - Scrum arrows" is included in the Scrum solution from the Project Management area of ConceptDraw Solution Park.

The vector stencils library "Scrum workspace" contains 21 icons.
Use this clipart set to design your agile software development diagrams and infographics with ConceptDraw PRO software.
"... a list of all the things that ... should be visible within the ideal agile workspace:
Big Visible Charts. ... the sprint burndown chart, showing the number of hours remaining as of each day of the current sprint. ... big visible charts showing the number of passing customer acceptance tests, the pass/ fail status of tests by day, sprint and release burndown charts, number of new stories introduced to the product backlog per sprint, and more.
Additional feedback devices. In addition to big, visible charts, it is common for an agile team to use additional visual feedback devices in their workspace. One of the most common is a lava lamp that is turned on whenever the automated build is broken.
... flashing red traffic lights to indicate exceptional conditions such as an issue on a production server. Also popular are ambient orbs and Nabaztag rabbits, which are wireless programmable devices that can also be configured to change colors, speak messages, or wiggle their ears as a team desires. ...
Everyone on your team. Each person on the team should ideally be able to see each other person on the team. This absolutely includes the ScrumMaster and ideally includes the product owner. ...
The sprint backlog. One of the best ways to ensure that everything necessary is completed in the sprint is to make the sprint backlog visible. The best way to do that is by displaying the sprint backlog on a wall, ideally in the form of a task board ...
The product backlog. One problem with running an endless series of sprints is that each can feel disconnected or isolated from the whole of a planned released or related set of new capabilities. A good way to reduce the impact of this problem is by displaying the product backlog somewhere clearly visible. ... tack the index cards with those upcoming user stories on a wall where all can see them. This allows team members to see how the user stories they are working on in the current sprint relate to others that are coming soon.
At least one big white board. ... Locating this in the team’s common workspace encourages spontaneous meetings." [mountaingoatsoftware.com/ blog/ the-ideal-agile-workspace]
The clip art sample "Design elements - Scrum workspace" is included in the Scrum solution from the Project Management area of ConceptDraw Solution Park.