Mae! Qari Su ‘Comprehensive Scrum Guide, ‘Three pillars of Serum Why Scrum? agile vs Scum Benefits of Serum Scrum Events TryNowitdownload/) Request Demo idemalrequestisp) @ ~ port) Pricing 'shop/ Comprehensive Scrum Guide ‘Sccum ((scrum/scrum-in-2-minutes/ isa framework for project management that emphasizes teamwork, accountabilly and iterative progress toward a welldefined goal. The framework begins with a simple premise: Start with what can be seen or known. After that, track the progress and tweak as necessary. Three pillars of Scrum ‘The base of Scrum is Empiricism, which states that knowledge comes from experience and we should make decisions from what is known. There are the three pillars that hold Serum tog Transparency Scrum Specer te 3 . Inspection z 5 a 2 3 : i g re iP Adaptation Spins on The tree plas of serum ‘A powerful scrum software that supports serum project management. features scrum tols tke usr story imap, product backlog management, sprit backlog management, task management, dally scrum meeting, Sprint planing too sprint review tol, sprint retrospective too, burndown impediment, stakeholder and team management. Learn More (/features/scrum-process-canwvas/) Why Scrum? Serum delivers features at time, while waterfall simply delivers phases. typical waterfall syle development fs phased:-based and sequential process that will ot give value untl the very end the project: Scrum turns that madel on is head and delivers new features every few weeks instead of focusing on a big Felease inthe future we se cote tooeryou abet expres son ur WEDS YoU See ote sof cool deserbed urology ox ‘daboutuseoshie-policejs0Scrum divides complex work into simple pleces, large organizations into small earns and far-reaching projects into a series of short time horizons called sprints (scrum/what-is-sprintin-scrum), Waterfall SS im Development Agile (Scrum) A. Releane: 4 4 Waterfall vs Serum By building iteratively and incrementally, companies are able to deliver customers the products and services they really need faster and more effectively. With Scrum, you can receive and incorporate customer feedback at the end of every small development cycle, which means your resus get shaped by reabworld use, not your assumptions. This makes it much easler to keep customers and key stakeholders closely involved and engages. Agile vs Scrum ‘Aglle(Uscrum/whatts-agile-software.development/ methodology isa practice that helps continuous Iteration of development and testing in the SDLC process. Agile breaks the product into smaller builds. ‘Scrum is just one of the many iterative and incremental agile software development process that allows US to focus on delivering the business value inthe shortest time, Scrum xP SAFE Kanban Lean ‘Agile vs Serum “The Scrum Framewark usually deals with the fact thatthe requirements are likely to change or mast of the time not known at the start ofthe project, The Characteristics of Serum are + Lightweighe + Simple to understand + Difficult to master Benefits of Scrum Following are the benefits that scrum provides to organizations, teams, products, and individuals 1. Better Quality: Projects exist to accomplish a vision or goal. Scrum provides the framework for continual feedback and exposure to make sure that qualty is as high as possible Serum helps ensure quality by the following practices 2, Reduced time to market: Scrum has been proven to deliver value tothe end customer 30 0.40 percent faster than traditional methods, We use cookes to ote you abet experience BINSERREERRSUMD 9 NVESITADET OF ASSES SDE NAIM ESSERE ARS KY reason tha, Scympaccletacealie abisher return on investment (RON). Because revenue and othertargeted benefits start coming in sooner, earlier accurmulation means higher total return ‘overtime, This is a basic tenet of net present value (NPY) calculations. 4 Higher Team Morale: Working with happy people who enjay their jobs can be satistying, and rewarding, Self management puts decisions that would normally be made by 2 ‘manager or the organization nto scrum team (/serum/whats-scrum-team/) members! hands. Enhance Team Collaboration: When scrum teams take responsiblity for projects and products, they can produce great results, Scrum teams collaborate and take ownership of duality and project performance through enhanced teamn participation and communication, The Scrum Framework Scrum is simple. Itis the opposite ofa big collection of interwoven mandatory components. Scrum is not a ‘methodology. Scrum implements the sclentific method of empiricism, Serum replaces a programmed algorithmic approach with a heur Lnpredictabilty and solving complex problems, The below graphic represents Scrum in Action as described bby Ken Schwaber and jeff Sutherland in their book Software in 30 Days taking us from planning through software delivery. SCRUM FRAMEWORK Ne as > > > Fr ca Product pin foesiog ecto tic one, with respect for people and sel-organization to deal with Serurn Framework The components of Scrum process ‘The Scrum Framework tse is very simple. It defines only some general guidetines with only afer utes, soles (/scrum/whatare-the-three-scrum-oles),attifacts(scrum/whatare-scrum-artifacts/ and events Nevertheless each ofthese components is important, serves a specific purpose andis essential fora successful usage a the framework ‘The main components of Scrum Framework are + The scrum roles: Serum Master (/sceum/what-is-scrum-master/), Scrum Product Owner (/sctum/what- Is:project-owner-role-in-scrum/) and the Scrum Team + The artifacts: Sprint backlog (/scrum/what-s-sprint-backlog-in-serum), product backlog (Uscrum/what-is-product-backlog-in-scrum/), burndown chart (/scrum/scrum-burndewn-chart), lo, ec. + Scrum events /scrum/what-are-scrum-events/) Sprint planning /scrum/whatis-sprint-planning/), Weuse ookes wo oteryousberer oye at aI aE A GERMER Sint ceo, eeWe use cookes wo eter you bere expe + Sprint The diagram below shows the key elements of the SCRUM framework, The process has been applied by the fo} com 2.2 @ set = @ — | oD oj Scrum Framework The Scrum roles When an organization decides to embrace Scrum, one of the frst things to understand is how Scrum roles itfer from traditional project execution roles, While there are only three main roles in Scrum, they don't automatically align with titles familar to most of us. Let's start witha brief definition of each: Product owner Product owner isa scrum development role for a person who represents the business or user community and is responsible for working with the user group to determine what features will be in the product release, The main responsibilities ofthe Product Owner are: + Develop the direction and strategy for the products and services, including the short and long-time goals; + Provide or have access to knowledge about the product or the service; + Understand and explain customer needs for the Development tear; ‘+ Gather, prioritize and manage the product or service requirements; + Take over any responsibilities related to the product of service budget, including its profitably + Determine the release date forthe product or service features; ‘+ Work together with the development tearm on a daly basis to answer questions and take decisions; + Accept or reject completed features relate to the Sprints ‘+ Show the main realizations ofthe development team in the end of each Sprint + Responsible for the Product Backlog Scrum master ‘Aserum master isthe facilitator for an agile development tear. Serum is a methodology that allows a team se.elfgrganige and.enake changes guicky cn ascer donee nth ale pcngilga,t he scrum master manages SME AMA MAS COIR jes of the Scrum Master are: the process aw odeimation dg exchanged. The main respons:+ Actasa coach, helping the team to follow scrum values and practices + Help to remove impediments and protect the team from external interferences + Promote a good cooperation between the team and stakeholders; + Facate common sense within the team; + Protect the team from organization distractions; Scrum team Scrum team (ake. Development team) is formed with from 3 to 9 people whe MUST full all technical needs to deliver the product or the service. They wll be guided direct by the Serum Master, but they will nt be lirectly managed. They must be selF-organized, versatile, and responsible enough to complete all required tasks. The development team is responsible for delivering potentially shippable product increments every sprint from analys's, design, development, testing to technical writing and ete, tis extremely important for Serum team possesses the following characteristics + Teams must be Self-Organized. All tarn components must manage thelr own efforts to complete the wat has been given. In Agile Scrum there Is no figure ofthe Team Leader or Line Manager. assignment Everybody must be committed enough ta perform their own activities and contribute ta the success of the team. Ifone fails, everybody fails, + Teams must be Cross-functional, All team members together must possess all required knowledge and skills to deliver a service or product that is well done and ready to Use, A spedallst can be used In necessary cases, but only as a coach whe transfers the knowledge to eLearn to fulfil a specific gap. + Being a Product Owner Requires a Business Vision. The Product Owner represents the voice of the customer and needs to trans Scrum Master and Development Teams. This is usually a full-time job. ein needs t + The Scrum Master is not a Line Manager. They help to provide the required coach to the Development ‘team and also help to remove any barrier that the team faces. Scrum artifacts The SCRUM artifacts are used to helo define the workload coming into the team and currently being worked upon the team. There are many more artifacts, for example, User stories, Release backlog, Burn-up chatt etc, But we will concentrate an the core three: Product backlog The product backlog isa collection of user stories which present functionalty which is required/wanted by the product 1m. Usually the product owner takes responsible for this list. Sprint backlog Sprint backlogs contain a collection of stories which could be included in the current sprint. Two important points to note about the relationship between the sprint backlog and the inclusion of iter into the sprint y ofthe delivery of those items. 2) Before an item can be remaved from the sprint backlog and added to the 1) The team decides what gets added to the sprint. The team therefore takes ownership and responsi sprint, the team must ensure they have all the information needed within the backlog. Usually a team defines a checklist of tems which must be present before the item can be added, Product Backlog vs Sprint Backlog \Weuuse coolest oteryou a beter experience, 2y vstng our webste, you agree to te use o cookie as described in our Coakie Paice ox ‘daboutuseoshie-policejs0‘The sprint backlog isa lst of tasks identived by the Scrum team to be completed during the Scrum sprint. During the sprint planning meeting, the tear selects some number of product backlog tems, usually inthe form of user stores, and identifies the tasks necessary to complete each user story as shown in the Figure below: Product backlog vs Scrum backlog Burn-down chart ‘A burn down chart isa graphical representation of work left todo versus time. The outstanding work (or backlog) 's often an the vertical axis, with time along the horizontal, That, itis a run chart of outstanding "work, Its useful for predicting when all of the work will be completed. tis eften used in agile software development methodologies such as Scrum. However, burn down charts can be applied to any project containing measurable progress overtime, Outstanding work can be represented in terms of ether time or story points (scrum/what-is-story-noint-in-agile). Burndown Chart 3 Burndown chart Scrum Events Communication is key! SCRUM relies on all aspects ofthe tear being and working transparently (scrum pillar #1). With this core ethos in mind, the methodology is structured around a number of key event for ensuring the two other pillars: Inspection and adaptation as shown in the Table below: Event Inspection ‘Adaptation \Weuuse coolest oteryou a beter experience, 2y vstng our webste, you agree to te use o cookie as described in our Coakie Paice ox ‘daboutuseoshie-policejs0Sprint Planning Daily Serum Sprint Review Uscrum/what is Sprint Retrospective Product backlog (Commitments Retrospective /scrum/what- {s-sprintretrospective-meeting/)) (Definition of Done (/scrum/definition-of done.ve-acceptancecriteriaN) Progress toward sprint goal Product increment Product backlog (release) Market-business conditions ‘Team & collaboration Technology & engineering Definition of Done Sprint goal Uscrum/write- sprint-goald) Forecast Sprint backlog Sprint backlog, Daly plan Product backlog, Actionable Improvements Note: There are five main meetings in Scrum during the execution of each sprint as shown in the Figure below: 1. Sprint Planning Sprint execution Sprint Planning 5. Product Backlog Refinement 2.Daily 3. Sprint 4. Sprint Scrum Review Retrospective All sprints begin with planning, The team needs to identity and commit to which terns are going to be: delivered as part ofthe sprint. The possible items are always taken from the Sprint Backlog as shown inthe Image below: Product Backlog er sv oy So? Sprint Planning Meeting Sprint Backlog > We use cokes eter you a beter expSRHEE B]ARAIRBITARER, you apreeo ce use of cookes as deserves in our Caale Paice ‘daboutuseoshle-polce|s‘This isthe time where the SCRUM master can shine. The product owner, identifies aspects they need from a business/customer point of view, the SCRUM team, identify which items they think they can deliver and the SCRUM master accommodates all and ensure the best of both worlds are met. Daily Scrum Meeting Conce the team have identified the kems they are committed to delivering as partf the sprint. The team will havea dally stand-up meeting. The core aim ofthis mestng ito ensure everyone within the team (and possible observers) ull visibility of what the status ofthe tasks being done and progress: + What they have done “+ What they are going to day ‘+ Whats stopping ther Poe reer Daily serum meeting ‘This dally update provides instance feedback tothe team and provides. These meetings are meant to be short and snappy no longer than 3 minutes per person, Note That: Observers are there to observe, the SCRUM master must where possible mitigate outside interruptions and distractions tothe team. Sprint Review Meeting A Sprint Review/Demo meeting is held atthe end of the Sprint ta inspect the increment. The Tearn demonstrates the Increment with focus on the Sprint Goal according tothe Definition of Done. The Product Owner reviews and accepts the delivered Increment. Sprint Retrospective ‘The sprint retrospective is usually the last thing done Ina sprint. Many tears wll do ic immediately after the sprint review. The entire team, including both the Scrum Master and the product owner should participate. You can schedule a scrum retrospective fer up to an hour, which s usually quite sufiient. The retrospective gives the team the opportunity to identify 3 key aspects 1. What should starting doing? 2. What did not go well and stop doing againi? 3. What went well (and should keep doing??? \Weuuse cooks ooteryou beter experienc, 2y visting our webste, you agree to the use of cooke as described in our Coake Paice ox ‘daboutuseoshie-policejs0What should do? What should stop doing? ‘What should keep doing? Sprint retrospective ‘The aim ofthis approach is to continually improve the team efficiency. Backlog Refinement Meeting (/scrum/what-is-product-backlog- refinement/) Think ofthe backlog asthe roadmap of the project. As the team collaborates to create alist of everything that needs to be built or done for project completion, this lst can be mosified and added to throughout project to ensure that all ofthe necessary needs of the project are met he Sprint inthe Scrum Framework all actives needed forte implementation of entries fom the Srum Product Backlog ave performed within Sprints ak ale erations), Sprints ae aways short: normaly about 24 weeks. Each Sprint follows a defined process as shown below: Sprint 1 Sprint 2 Final Sprint Agile serum sprint {As mentioned before, contains only a few large items, the impact of underestimating the work on even a single em will have a profound impact on the sprint. And since larger items tend to be harder to estimate and understand, the potential for a falled sprint increases further. Experienced Scrum Teams spend time and effort to break down complex and larger items (ie user features or epics) into smaller user stories (or subsequently rs in the product backlog are pri 12 and selected to the sprint backlog. a sprint breaking down into task, or subtasks) Epic An epic captures a large body of work. Iti essentially a “large user story that can be broken down into a ‘number of smaller stories. it may take several sprints to complete an epic. So when we take epic for development, it MUST be decomposed into smaller user stories, Early in the project cycle, we come up with Epics. These are very high-level, almost marketing-centric,bullet- points of functionality We call large stories “epics” to communicate something about them, ke to think of this in relation to ‘movies. I tell you a particular movie was an ‘action-adventure movie" that tells you something abou the movie. There's probably some car chases, probably some shooting, and so on. Similarly, calling a story an “epic” can sometimes convey adltional meaning. \Weuuse cooks to oteryou beter experienc, By vstng our webse, you agree to the use a cooke as described in our Coake Paice ox ‘daboutuseoshie-policejs0User Story A Stories ia briet statement ofa product requirement ora business case. Typically stories ae expressed in plain language to help the reader understand what the software should accomplish, Product owners create stories A scrum user then divides the es into one or more scrum tasks. A.ser storys typically functionality that will be visible to end users. A user story follows the format "las WHO want to da WHAT, sot at WHY. A.ser story delivers value tothe customer/user. Its a product requirement from the custemer/user, eg. "As a customer, 1 want tobe able to create an account so that | can see the purchases I made in the last year to help me budget for next year: Tasks on the other hand, more a technical nature, Task is typically something Ike code this, design that, create test data for such-and-such, automate that, and so on, These tend to be things done by one person. ‘Atask is not writen in the user story format. A task has more a technical nature. eg, “Evaluate Angular material design for user interface” or "Submit app to app store’ ‘About Visual Paradigm Visual Paradigm help organizations process-canvas/ in 2018, introduced Scrum Process Canvas for automating the way a Scrum team to create, manage and deploy software application that empowers the team to continuously improve thelr changing environment. Our ward.winning products are trusted by performance at unprecedented speed and scale, Manage the Entire Scrum Process in One Page = Automat the Scrum Framework in a fun and enjoyable dashboard with eye-catching updated status, + Manage Backlog, Multiple Sprints of different Scrum Roles witha single-page visually executable + Allow instantly access, review and generate scrum artifacts and related documents to be archived in the Shared Cabin: + Automate the Scrum events and related activities with self-explanatory instructions, samples and required document templates, Turn every software project into a successful one. ‘We use cookies to otferyou a better experience. 3y vsring LOY MIBMAL PAT APR FEE. EPMOUREM bescrves in our Cookie Policy oK aboutuslcakle-sai0 Product Support Feawesieatues” forums fons ledtionss Tow (usowntonan Pang Ushons orm) aradiem, nts (tsostontne visual, Sustomer Service paradigm coma ror oyvislbeaden AVeNS ed, epbenathnlis) Ene semersiabecseo aes) Learn About Us Communtyciele visual Parad (bspsuceclevisua aboutus paradlemo™) arom, Know-how aboutusnewsrseases/ paradigmcam reas youtube comlusarVs ema wiseos adamie Parinershio Todas mutoratsn, —partnrtacadericn (Goupoonicocumentsa (neeps:/witter.com/visualparadigm) A (hetps://wwew-tacebook.com/Visual- Paradigr-822068561487170/) (heeps://wwe.linkedin.com/company/visual: paradigm) © (hteps://worn.pinterest.com/visualparadign/) 8 (hetps://mwn.youtube.com/user/VisualParadi, o (hteps:/tvern.instagram.com/visualparadigm) \Weuuse coolest oteryou beter experience, ay vstng our webste, you agree to the use of cooke as described in our Coakie Policy ox daboutuseoshie-noiceJs