Design elements - Scrum people

The vector stencils library "Scrum people" contains 30 icons: scrum master, product owner, development team, etc.
Use this clipart set to design your agile software development diagrams and infographics with ConceptDraw PRO software.
"There are three core roles in the scrum framework. These core roles are those committed to the project in the scrum process — they are the ones producing the product (objective of the project). They represent the scrum team. ...
Product owner
The product owner represents the stakeholders and is the voice of the customer, who is accountable for ensuring that the team delivers value to the business. The product owner writes (or has the team write) customer-centric items (typically user stories), ranks and prioritizes them, and adds them to the product backlog. ...
Development team
The development team is responsible for delivering potentially shippable increments (PSIs) of product at the end of each sprint (the sprint goal). A team is made up of 3–9 individuals who do the actual work (analyse, design, develop, test, technical communication, document, etc.). Development teams are cross-functional, with all of the skills as a team necessary to create a product increment. The development team in scrum is self-organizing...
Scrum master
Scrum is facilitated by a scrum master, who is accountable for removing impediments to the ability of the team to deliver the product goals and deliverables. The scrum master is not a traditional team lead or project manager, but acts as a buffer between the team and any distracting influences. The scrum master ensures that the scrum process is used as intended. The scrum master helps ensure the team follows the agreed scrum processes, often facilitates key sessions, and encourages the team to improve." [Scrum (software development). Wikipedia]
The clip art sample "Design elements - Scrum people" is included in the Scrum solution from the Project Management area of ConceptDraw Solution Park.

"In technology, agile development involves teams self-managing to a large extent (though agile development is commonly still practised within a hierarchical organization, which means that certain types of decisions such as hiring, firing, and pay rises remain the prerogative of managers). In scrum, an agile methodology, team members assign work to be done among themselves, either by free choice or by consensus. The scrum master role in scrum is not a management role as such, but is a role that involves helping to remove obstacles to forward progress, and ensuring that the basic scrum framework is adhered to by all parties, inside and outside the team - both aspects of the role being more akin to facilitation than to top-down micromanagement. Agile methodologies such as scrum have also begun being used in non-technology companies and organizations." [Flat organization. Wikipedia]
This flat org chart template for the ConceptDraw PRO diagramming and vector drawing software is included in the 25 Typical Organizational Charts solution from the 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.

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