Scrum sprint cycle

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 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: 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.

"Scrum: A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. ...
The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules. Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage.
The rules of Scrum bind together the events, roles, and artifacts, governing the relationships and interaction between them." [scrumguides.org/ scrum-guide.html#definition]
The agile software development infographic sample "Scrum" 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 "Diagram of Major Sprint Components" from p. 14 of "SUITE Agile Process Guide. Another Companion to the Systems Engineering Methodology (SEM) of the State Unified Information Technology Environment (SUITE). Michigan Department of Technology,
Management & Budget. January 2015".
[michigan.gov/ documents/ suite/ SUITE_ Agile_ Process_ Guide_ -_ 20120711_ V.1_ 430719_ 7.pdf]
"A sprint (or iteration) is the basic unit of development in scrum. The sprint is a timeboxed effort; that is, it is restricted to a specific duration. The duration is fixed in advance for each sprint and is normally between one week and one month, with two weeks being the most common.
Each sprint starts with a sprint planning event that aims to define a sprint backlog, identify the work for the sprint, and make an estimated commitment for the sprint goal. Each sprint ends with a sprint review and sprint retrospective, that reviews progress to show to stakeholders and identify lessons and improvements for the next sprints.
Scrum emphasizes working product at the end of the sprint that is really done. In the case of software, this likely includes that the software has been integrated, fully tested, end-user documented, and is potentially shippable." [Scrum (software development). Workflow. Wikipedia]
The scrum infographic sample "Major sprint components" 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 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.