PM Agile

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.

The vector stencils library "Scrum workflow" contains 39 icons.
Use this clipart set to design your agile software development diagrams and flowcharts with ConceptDraw PRO software.
"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). Wikipedia]
The clip art sample "Design elements - Scrum workflow" is included in the Scrum solution from the Project Management area of ConceptDraw Solution Park.

The vector stencils library "Scrum artifacts" contains 52 icons.
Use this clipart set to design your agile software development diagrams and infographics with ConceptDraw PRO software.
"Product backlog
The product backlog comprises an ordered list of requirements that a scrum team maintains for a product. It consists of features, bug fixes, non-functional requirements, etc.—whatever must be done to successfully deliver a viable product. The product owner orders the product backlog items (PBIs) based on considerations such as risk, business value, dependencies, and date needed. ...
Sprint backlog
The sprint backlog is the list of work the development team must address during the next sprint. The list is derived by the scrum team selecting product backlog items from the top of the product backlog until the development team feels it has enough work to fill the sprint. This is done by the development team asking "Can we also do this?" and adding product backlog items to the sprint backlog. The development team should keep in mind its past performance assessing its capacity for the new sprint, and use this as a guide line of how much "effort" they can complete.
The product backlog items may be broken down into tasks by the development team. Tasks on the sprint backlog are never assigned; rather, tasks are signed up for by the team members as needed according to the set priority and the development team member skills. This promotes self-organization of the development team, and developer buy-in. ...
Sprint burn-down chart
The sprint burndown chart is a public displayed chart showing remaining work in the sprint backlog. Updated every day, it gives a simple view of the sprint progress. ...
Release burn-down chart
The release burndown chart is the way for the team to track progress and provide visibility. The release burndown chart is updated at the end of each sprint by the scrum master. The horizontal axis of the release burndown chart shows the sprints; the vertical axis shows the amount of work remaining at the start of each sprint." [Scrum (software development). Wikipedia]
The clip art sample "Design elements - Scrum artifacts" is included in 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.