Agile Scrum - A Brief by Manish Manekar

[

[

WHAT IS AGILE/SCRUM?

WHAT IS AGILE/SCRUM?

]

]

Agile has gained huge popularity and is fast spreading out in the software Agile has gained huge popularity and is fast spreading out in the software development community. Scrum focus on Agile management and it is like Getting It development community. Scrum focus on Agile management and it is like Getting It Done. This brief is first step to the introduction of Agile/Scrum.

Trusted by over 1 million members

Try Scribd

FREE for 30 days to access over 125 million titles without ads or interruptions!

Start Free Trial

Cancel Anytime.

Trusted by over 1 million members

Try Scribd

FREE for 30 days to access over 125 million titles without ads or interruptions!

Start Free Trial

Table of Contents

Table of Contents

Pi g g & & CChihi cc keke n n AnAn aa lolo ggy y ... ... 44 Pr Pr odod uuct ct OwOw nene r ...r ... .... 44 Te Te aam m MMemem bber er ... 5... 5 Sc Sc rruum m MMaastst er er ... ... 55 Other Stakeholders... 5 Other Stakeholders... 5 B Baaccklkl og og ... ... 55 U Usese r r StSt oorriies es ... 5... 5 Pr Pr odod uuct ct BBaaccklkl og ...og ... 5. 5 Sp Sp rrinin t t BBaackck lolo g ...g ... .... 55 Sc

Sc rrum um MMeeee ttinin ggs ...s ... ... 66 Re

Re lleaea sse e PPlala nnnn iinng ...g ... ... 66 Sp Sp rrinin t t PP lala nnnninin g ...g ... .... 66 Da Da iily ly ScSc rrum um ... 6... 6 Review ... 6 Review ... 6 Re

Re ttrroospsp ecec ttiviv e ...e ... ... 66 Th

Th e e SpSp rrinin t t PlPl aannnn inin g g ... ... 77 Sc

Sc rrum um MMetet rricic s s ... ... 88 Ve Ve lolo cici tty y ... ... 88 St St oorry y PPooinin t t ... ... 88 B Burur ndnd oowwn n ChCh aarrt .t ... ... 88 Test Cases and Defects ... 9 Test Cases and Defects ... 9 Ne Ne xt xt StSt epep s ...s ... 9... 9 Ap Ap ppenen didi x x A: A: HoHo w w it it WoWo rrks ks in in AgAg ilil e? e? ... .. 1010 Minutes of Meeting ... 10 Minutes of Meeting ... 10 Co Co nfnf igig urur aatt ioio n n MaMa nana ggemem enen t ..t ... .. 1010 Ha Ha ndnd liling ng ChCh anan ge ge RReqeq ueue sst .t ... . 1010 Testing Procedures ... 10 Testing Procedures ... 10 Ap Ap pepe ndnd ix ix B: B: AgAg ilil e e CoCo didi ng ng GuGu idid elel inin es ...es ... 1.. 111

Trusted by over 1 million members

Try Scribd

FREE for 30 days to access over 125 million titles without ads or interruptions!

Start Free Trial

What is Agile/Scrum?

What is Agile/Scrum?

Dictionary meaning of A

Dictionary meaning of A gile is “able to move quickly and with suppleness,gile is “able to move quickly and with suppleness, skill, and control”. It is

skill, and control”. It is synonymous with Lively, Alert, & Responsive.synonymous with Lively, Alert, & Responsive. Agile isAgile is a quick & well coordinated movement. It is adaptive and people oriented.

a quick & well coordinated movement. It is adaptive and people oriented.

[Wikipedia] Agile software development refers to a group of software [Wikipedia] Agile software development refers to a group of software development methodologies based on iterative development, where development methodologies based on iterative development, where requirements and solutions evolve through collabora tion between requirements and solutions evolve through collabora tion between self-organizing cross-functional teams. The term was coined in the year 2001 organizing cross-functional teams. The term was coined in the year 2001 when the Agile Manifesto and the Twelve Principles were formulated. when the Agile Manifesto and the Twelve Principles were formulated. [www.agilemanifesto.org]

[www.agilemanifesto.org] The terms methodolog

The terms methodology, framework, method, practice, technique y, framework, method, practice, technique in referencein reference to Agile are used depending on its context, but here we will use most of  to Agile are used depending on its context, but here we will use most of  those loosely to refer to Scrum. Please note, this document is intended for those loosely to refer to Scrum. Please note, this document is intended for Agile novice audience to introduce Scrum in a manne r that is brief and Agile novice audience to introduce Scrum in a manne r that is brief and simple. While there are several Agile methods, for the purpose o f this simple. While there are several Agile methods, for the purpose o f this document, all the references are in

document, all the references are in resperespect to Scrum.ct to Scrum. Here is

Trusted by over 1 million members

Try Scribd

FREE for 30 days to access over 125 million titles without ads or interruptions!

Start Free Trial

Agile methodology is based on iterative development, where requirements Agile methodology is based on iterative development, where requirements and solutions evolve through collaboration between self-organizing and solutions evolve through collaboration between self-organizing cross-functional teams. It values Individuals and interac tions over processes and functional teams. It values Individuals and interac tions over processes and tools, working software over comprehensive document ation, c ustomer tools, working software over comprehensive document ation, c ustomer collaboration over contract negotiation and respond ing to change over collaboration over contract negotiation and respond ing to change over following a plan. Iteration refers to short cycle, typically 2 weeks and also following a plan. Iteration refers to short cycle, typically 2 weeks and also referred to as a sprint. Self-organizing team is a close group of motivated referred to as a sprint. Self-organizing team is a close group of motivated individuals committed to Agile values & principles who have been empowered individuals committed to Agile values & principles who have been empowered to take initiatives & decisions.

to take initiatives & decisions. Scrum is

Scrum is a team-based iterative, increma team-based iterative, incremental framework that allows teams toental framework that allows teams to deliver a potentially shippable set of f

deliver a potentially shippable set of f unctionalunctionality per iteration, providing theity per iteration, providing the agility needed to respond to rapidly changing requi rements. Its principles are agility needed to respond to rapidly changing requi rements. Its principles are customer satisfaction, responding to change, workin g software, and customer satisfaction, responding to change, workin g software, and continuous improvement, teamwork of self organized

continuous improvement, teamwork of self organized individuals, sustenance,individuals, sustenance, simplicity, trust, and

simplicity, trust, and conversatioconversation.n. A lot emphasis is put on maximizing

A lot emphasis is put on maximizing individuals‟ individuals‟ interactioninteraction –– amount as wellamount as well as frequency.

as frequency. Let us now see who all these individuals are…Let us now see who all these individuals are…

Various Roles in Scrum Development

Various Roles in Scrum Development

Pig & Chicken Analogy Pig & Chicken Analogy

A pig and a chicken are walking down the road. The chicken looks at the pig A pig and a chicken are walking down the road. The chicken looks at the pig and says, “Hey Pig, why don‟t we start a restaurant ?” The pig looks at the and says, “Hey Pig, why don‟t we start a restaurant ?” The pig looks at the chicken and says, “That‟s a great idea, but what do we call it?” The chicken chicken and says, “That‟s a great idea, but what do we call it?” The chicken replies, “Why don‟t we call it „Ham and Eggs‟?” The pig thinks about it and replies, “Why don‟t we call it „Ham and Eggs‟?” The pig thinks about it and says, “I don‟t think so. I‟d be committed but you‟d only be involved.” 

says, “I don‟t think so. I‟d be committed but you‟d only be involved.”  Individuals in a scrum team assumes either of two r oles

Individuals in a scrum team assumes either of two r oles –– in the Pig role arein the Pig role are those who committed to scrum and in the Chicken rol e are rest of those who those who committed to scrum and in the Chicken rol e are rest of those who are involved otherwise.

are involved otherwise. Product Owner

Product Owner

The Product Owner is a customer advocate who know what customer wants, The Product Owner is a customer advocate who know what customer wants, along with its value to th

along with its value to th e customer. This person he customer. This person h olds the final authority forolds the final authority for setting and maintaining the backlog as well as the priorities throughout the setting and maintaining the backlog as well as the priorities throughout the release, determining the value of product delivered , and terminating a sprint release, determining the value of product delivered , and terminating a sprint when necessary. He

when necessary. He drives release planning, participatedrives release planning, participates in scrum meetings,s in scrum meetings, elaborate

elaborates on s on stories for the team, and accepts/rejects stories d emonstrated.stories for the team, and accepts/rejects stories d emonstrated. Product Owner is the role whose commitment greatly influences the success Product Owner is the role whose commitment greatly influences the success

Trusted by over 1 million members

Try Scribd

FREE for 30 days to access over 125 million titles without ads or interruptions!

Start Free Trial

Team Member Team Member

The team member is another committed individual who directly contributes The team member is another committed individual who directly contributes to the delivery of working software. This individua l is architect, designer, to the delivery of working software. This individua l is architect, designer, developer, tester, usability, build engineer and wh oever works o n the developer, tester, usability, build engineer and wh oever works o n the produce. A typical scrum team is about 7 members (+ /- 2). A great agile produce. A typical scrum team is about 7 members (+ /- 2). A great agile team is one that has assimilated agile values and principles, and can handle team is one that has assimilated agile values and principles, and can handle the power and

the power and responsibresponsibility that comes with it.ility that comes with it. Scrum Master

Scrum Master

The Scrum Master is the servant leader committed to ensure the highest The Scrum Master is the servant leader committed to ensure the highest priority needs of the team are being served. A grea t Scrum Master is one priority needs of the team are being served. A grea t Scrum Master is one who is a good listener, coach, humble, committed, c ollabora tive, and who is a good listener, coach, humble, committed, c ollabora tive, and knowledgeable.

knowledgeable. That he/she removes any impediments out of team‟s w ay onThat he/she removes any impediments out of team‟s w ay on a daily basis yet refrain from micro-manage the team. Scrum Master is the a daily basis yet refrain from micro-manage the team. Scrum Master is the leader with no authority.

leader with no authority. Other Stakeholders Other Stakeholders The rest of the

The rest of the parties involved in the project are the customer, v endor, userparties involved in the project are the customer, v endor, user and management. These stakeholders participate at v aried degree and at and management. These stakeholders participate at v aried degree and at different stages in the flow as and

different stages in the flow as and when necessary.when necessary.

We just met the entire scrum team; now let us see what work they do… We just met the entire scrum team; now let us see what work they do…

Backlog

Backlog

The work that is comprised of requirements, scope a nd specifications i s The work that is comprised of requirements, scope a nd specifications i s captured in the form of stories. A story is a templ ate to gather e nough captured in the form of stories. A story is a templ ate to gather e nough information about the feature or requirement to give the team a high level information about the feature or requirement to give the team a high level idea about it. Since it is

idea about it. Since it is a story of user requirement, it is popularly known asa story of user requirement, it is popularly known as User Story. We will know more on its use in next topic.

User Story. We will know more on its use in next topic. User Stories

User Stories

Product Owner who owns the vision of final delivera ble based on input from Product Owner who owns the vision of final delivera ble based on input from customers, end users, field

customers, end users, field people, industry experts and other stakeholders.people, industry experts and other stakeholders. These requirements are transformed into User Storie s so as to inform the These requirements are transformed into User Storie s so as to inform the team what is required to produce and deliver in small increments.

team what is required to produce and deliver in small increments. Product Backlog

Product Backlog

A Product Backlog is Product Owner‟s wish list in t he form

A Product Backlog is Product Owner‟s wish list in t he form of User Stories.of User Stories. The Product Owner set priority to each story in the backlog based on the The Product Owner set priority to each story in the backlog based on the associated business value and risk. The team is committed to deliver the associated business value and risk. The team is committed to deliver the highest priority items first.

highest priority items first. Sprint Backlog

Trusted by over 1 million members

Try Scribd

FREE for 30 days to access over 125 million titles without ads or interruptions!

Start Free Trial

Scrum Meetings

Scrum Meetings

Since we value individuals and interactions while d iscounting on Since we value individuals and interactions while d iscounting on comprehensive documentation and claim to respond to change, meetings are comprehensive documentation and claim to respond to change, meetings are critical to success. Keep in mind that every scrum meeting is face-to-face critical to success. Keep in mind that every scrum meeting is face-to-face meeting and the team is expected to participate at all levels.

meeting and the team is expected to participate at all levels. Release Planning

Release Planning What:

What: Brainstorming Brainstorming high high level level scope/tscope/theme heme of of entire entire projecproject/releaset/release Who:

Who: Driven Driven by by Product Product Owner; Owner; Attendance Attendance mandatomandatory ry to to allall When:

When: At the At the beginning beginning of of the the project/reproject/release; lease; lasts lasts for for a a day day or or twotwo Outcome:

Outcome: Product Product BacklogBacklog Sprint Planning

Sprint Planning What:

What: Focus Focus on on highest highest priority priority backlog backlog itemsitems Who:

Who: Driven Driven by by Product Product Owner; Owner; Attendance Attendance mandatory mandatory to to teamteam When:

When: At the At the beginning beginning of of every every Sprint; Sprint; a a few few hours hours in in a a dayday Outcome:

Outcome: Sprint Sprint BacklogBacklog Daily Scrum

Daily Scrum What:

What: Every Every teteam member share what did I do yesterday, what‟s foram member share what did I do yesterday, what‟s for today and anything stopping me from getting there

today and anything stopping me from getting there Who:

Who: Driven Driven by by and and mandatory mandatory to to team team membersmembers When:

When: Every Working Every Working Day; Day; not not more more than than 10-15 10-15 minmin Outcome:

Outcome: ImpedimeImpediment Backlont Backlog (list g (list of iof issues ssues that Scrum that Scrum Master will Master will workwork to resolve)

to resolve) Review

Review What:

What: Review Review of of work work completed completed during during the the SprintSprint Who:

Who: Driven Driven by by Product Product Owner; Owner; Attendance Attendance mandatory mandatory to to teamteam When:

When: At the At the end end of of every every Sprint; Sprint; a a couple couple of of hourshours Outcome:

Outcome: Accept/ReAccept/Re jected jected User User StoriesStories Retrospective

Retrospective What:

What: Review Review what what went went well, well, what what did did not not work work for for the the team team in in thethe recent Sprint and decide what the

recent Sprint and decide what the team would like to do differentteam would like to do different Who:

Who: Driven Driven by by and and mandatory mandatory to to team team membersmembers When:

When: After Review After Review meeting meeting and and before before beginning beginning of of next next Sprint; Sprint; couplecouple of hours at most

of hours at most Outcome:

Outcome: Best Best Practices Practices to to follow follow in in coming coming SprintsSprints

All Scrum meetings are time boxed and facilitated and moderated by Scrum All Scrum meetings are time boxed and facilitated and moderated by Scrum Master. The agenda and format of each meeting is fi xed and the time Master. The agenda and format of each meeting is fi xed and the time

Trusted by over 1 million members

Try Scribd

FREE for 30 days to access over 125 million titles without ads or interruptions!

Start Free Trial

Start Free Trial

Cancel Anytime.

The Sprint Planning

The Sprint Planning

Agile is iterative approach to deliver working soft ware in increments. This Agile is iterative approach to deliver working soft ware in increments. This iteration is of a short period typically development cycle of 2-4 weeks. Such iteration is of a short period typically development cycle of 2-4 weeks. Such a cycle is called a Sprint. Series of Sprints conclude as a Release. Length of  a cycle is called a Sprint. Series of Sprints conclude as a Release. Length of  a Sprint is

a Sprint is generalgenerally constant throughout the Release.ly constant throughout the Release. Before the Sprint Planning

Before the Sprint Planning meeting, the team members are expected to do ameeting, the team members are expected to do a little homework. Product Owner ensures that the Pro duct Backlog is up to little homework. Product Owner ensures that the Pro duct Backlog is up to date with priorities. All members announce their av ailability (also called date with priorities. All members announce their av ailability (also called Velocity) during this Sprint. Responsible members t ake a look at their Velocity) during this Sprint. Responsible members t ake a look at their respective User Stories with next highest priority in the Product Backlog. respective User Stories with next highest priority in the Product Backlog. Where possible, it is broken down into small activi ties known as tasks along Where possible, it is broken down into small activi ties known as tasks along with estimates. There are various ways of estimating User Stories; however, with estimates. There are various ways of estimating User Stories; however, the team has to follow one agreed method.

the team has to follow one agreed method.

During the Sprint Planning Meeting, Product Owner s hares his vision of the During the Sprint Planning Meeting, Product Owner s hares his vision of the Release again and along with the team defines the Sprint Goal. If the team Release again and along with the team defines the Sprint Goal. If the team needs any clarification on respective User Stories, Product Owner provides needs any clarification on respective User Stories, Product Owner provides the necessary details that help the team estimate i t. At the end of this the necessary details that help the team estimate i t. At the end of this meeting, there is a mutually

meeting, there is a mutually agreed Sprint Backlog.agreed Sprint Backlog.

Post Sprint Planning Meeting, the team makes sure t hat estimated tasks are Post Sprint Planning Meeting, the team makes sure t hat estimated tasks are added to all items in the Sprint Backlog and respective task owners ar e added to all items in the Sprint Backlog and respective task owners ar e identified.

identified.

All these activities are recorded on a storyboard

All these activities are recorded on a storyboard –– which is either generatedwhich is either generated using some project management softwar

using some project management software tool or e tool or a physical board with stia physical board with sti ckycky notes on it. Here is how it looks like

notes on it. Here is how it looks like –– in the middle of a Sprint - while wein the middle of a Sprint - while we keep the details out of t

Trusted by over 1 million members

Try Scribd

FREE for 30 days to access over 125 million titles without ads or interruptions!

Start Free Trial

Cancel Anytime.

Trusted by over 1 million members

Try Scribd

FREE for 30 days to access over 125 million titles without ads or interruptions!

Start Free Trial

Cancel Anytime.

Scrum Metrics

Scrum Metrics

We can measure the success using a variety of metri cs. Some of the popular We can measure the success using a variety of metri cs. Some of the popular and useful ones are listed here:

and useful ones are listed here: Velocity

Velocity

Velocity is the availability of a team member and i s recorded either as hours, Velocity is the availability of a team member and i s recorded either as hours, days or percentage. Team velocity is the total of all team members. This is days or percentage. Team velocity is the total of all team members. This is measured and tracked Sprint over Sprint. As

measured and tracked Sprint over Sprint. As a general guideline, you cannota general guideline, you cannot accomplish total estimated hours greater than the t eam velocity in a ny accomplish total estimated hours greater than the t eam velocity in a ny particular Sprint.

Start Free Trial

Cancel Anytime.

Test Cases and Defects Test Cases and Defects

We can always collect the usual metrics around Test Cases and Defects. We can always collect the usual metrics around Test Cases and Defects.

Next Steps

Next Steps

1

1.. Learn & Assimilate Agile Values & Learn & Assimilate Agile Values & PrinciplesPrinciples 2

2.. Learn the Basics Learn the Basics of Agile/Scrumof Agile/Scrum 3

3.. Learn & Identify Challenges in Agile AdoptionLearn & Identify Challenges in Agile Adoption 4

4.. Pilot Agile DevelopmentPilot Agile Development 5

Trusted by over 1 million members

Try Scribd

FREE for 30 days to access over 125 million titles without ads or interruptions!

Start Free Trial

Cancel Anytime.

Trusted by over 1 million members

Try Scribd

FREE for 30 days to access over 125 million titles without ads or interruptions!

Start Free Trial

Cancel Anytime.

Appendix A: How it Works in Agile?

Appendix A: How it Works in Agile?

Minutes of Meeting Minutes of Meeting

Agile values interactions and insists that

Agile values interactions and insists that everybodeverybody in y in the team including thethe team including the stakeholders and entire organization, where desired , should have access to stakeholders and entire organization, where desired , should have access to the progress, impediments and the decisions/results of all the meetings. the progress, impediments and the decisions/results of all the meetings. While most of the teams

While most of the teams use storyboarduse storyboards as ths as th e tool for all this ine tool for all this in formatioformation,n, there is no need for separate minutes of meeting. T his info rmation is there is no need for separate minutes of meeting. T his info rmation is recorded on the storyboard and everybody has access to it. If you still find recorded on the storyboard and everybody has access to it. If you still find value in maintaining and/or distributing it separat ely, there is no stopping. value in maintaining and/or distributing it separat ely, there is no stopping. You may prepare and use some template that delivers value to the You may prepare and use some template that delivers value to the recipients.

recipients.

Configuration Management Configuration Management

Streamlined process and Automation are the keys to Configuration Streamlined process and Automation are the keys to Configuration Management in Agile environment. While there are so me patterns you may Management in Agile environment. While there are so me patterns you may use, the best practices such as Source Control, Aut omated use, the best practices such as Source Control, Aut omated Build-Migrate-Deploy, Test Automation and Continuous Integration is the way to go about Deploy, Test Automation and Continuous Integration is the way to go about it. Remember the Agile teams are

it. Remember the Agile teams are closely interacting and committed to followclosely interacting and committed to follow the process. Besides, the daily scrum meeting expos es any configuration the process. Besides, the daily scrum meeting expos es any configuration problem within a day

problem within a day –– which makes it difficult for the team to breach thewhich makes it difficult for the team to breach the process repeatedly.

process repeatedly.

Handling Change Request Handling Change Request

Agile vouch for responding to change. While Scrum d oes not recommend Agile vouch for responding to change. While Scrum d oes not recommend distracting team during the sprint, the Product Own er can always mak e distracting team during the sprint, the Product Own er can always mak e necessary changes to the product backlog that will be considered during the necessary changes to the product backlog that will be considered during the following sprint. Since the sprint duration is typi cally 2 weeks, most of the following sprint. Since the sprint duration is typi cally 2 weeks, most of the change requests those can wait for 2 weeks are seamlessly accommodated. change requests those can wait for 2 weeks are seamlessly accommodated. In extreme situation, the Product Owner may also decide and terminate In extreme situation, the Product Owner may also decide and terminate ongoing sprint and call on Sprint Planning for the new sprint.

Start Free Trial

Cancel Anytime.

Appendix B: Agile Coding Guidelines

Appendix B: Agile Coding Guidelines

While there is no mandate as Agile Coding Standards , considering that we While there is no mandate as Agile Coding Standards , considering that we deliver software in increments and respond to chang e, there certainly are deliver software in increments and respond to chang e, there certainly are some best practices those serve as guidelines. Here is a partial list for your some best practices those serve as guidelines. Here is a partial list for your information.

information.

Modeling/Design Modeling/Design 

 Simple, flexible and scalableSimple, flexible and scalable 

 Model in small incrementsModel in small increments 

 Apply patterns gentlyApply patterns gently 

 Update only when it hurtsUpdate only when it hurts 

 Collective ownershipCollective ownership 

 Use simple toolsUse simple tools Coding

Coding

Your usual coding standards still holds the ground and make sure it Your usual coding standards still holds the ground and make sure it addresses following:

addresses following: 

 Standardize on Standardize on ConsensusConsensus 

 Collective Code OwnershipCollective Code Ownership 

 Coding DisciplineCoding Discipline 