welcome to agile training

Welcome to Agile Training The purpose of this workshop is to introduce you to Agile, and the

Scrum, Feature Driven Development (FDD) and Kanban frameworks that are part of the Agile family of methodologies.

The cou f role or backgro

When y » The » Tips timation

and » How

2

Schedule for todayTopic Leader Duration Time (ET)Introductions Dan 10 mins 8:00 – 8:10

Requiremen 10 – 8:45

Kickstart – 45 – 9:40

-- break -- 40 – 9:50

Kickstart – P 0 – 10:30

Fundament 30 – 11:30

Introduction 30 – 12:00

-- lunch -- 00 – 12:45

White Eleph 45 – 1:30

Essentials – 30 – 2:30

-- break -- 30 – 2:45


Wrap-up Brian 15 mins 3:45 – 4:00

3

IntroductionGood morning!

Today we are going to cover Agile and Scrum, with a focus on the basics. Tomorrow we’ll review

Two things » This is ble. We have

planne at will help you rem

» Keep a onal schools of though

Today we’r project gets started – it

We’re goin fundament er (in a way you’ve prob presentatio

Any questions before we get started?

6

STA FRO RE USER STORIES

7

New Projects New Projects at F500 clients typically start with a series of high level

meetings that result in documents called a Statement of Work [SOW] (when external parties are involved, like Cognizant ) and a Project Charte

» Th lly binding con

Projec all about. They v f at least four se» Hig a simple

bu .» Sc » Bu ber» Sta eeded

8

1

If Cognizant has a Master Services Agreement [MSA] with a client, an SOW may not be necessary.1

Requirements and User Stories

10

In order to get started with our project, first we need to know more about what we should build. So we open the Project Charter and begin to discuss the scope section, frequently meeting with the end user to determine what they want.

In Agile pro s are used to describe

User s terms, from a partic

» Has

Use Ca a system and on

» Ext or flows » Eac

The list built into functio

We’re goin most Agile projects fol

Our example scenario starts off today with a user story…

KIC

13

Kickstart - Sprint Simulation Rules First, break into evenly-sized groups of at least 4. I also need a volunteer

to play the role of Scrum Master for each group.

We wi backlog.

We wi ith time).

Each “ 6 mins.

Each “

No wo

At the spective.» Sp sh» Re g more

efficient

15

Step 2: Sprint Planning Discuss Team member availability

» Sum the time available for all team members For e

» Re e team be

» Br zing th

» Es • • y one

» Su he

av » If

OK – now let’s walk through the above steps…

17

Step 3: Start the Sprint

Each day in the sprint will be 2 minutes. You will have 3 days orm as many

At th person has c ext day, and w

GO!

24

Step 4: Sprint Review and Retrospective Ok…How was that?

For t o the produ

For t what work ext sprin » Di the

ac » Di al issues

or

25

AG

27

Agile Methodologies – Short Descriptions Scrum is…

» an iterative, incremental process wherein a small team of fixed size works over a series of constant-length timeboxes where each contains a fixed scope de

» Ea » De f

fun » Ea etermines

wh showing the en ld. Im prove their pro

» Du nd reports on

» Wh user stories are backlog for the

» In hat owns the e shepherd for the scrum team (not a PM), are two new roles that need to be accounted for. The PM and Architect roles & responsibilities are modified significantly.

» The primary metric the team is attempting to improve is the velocity, the actual speed at which the team is delivering functionality to the business. Predictability is a goal.

30

Agile Methodologies – Short Descriptions Daikibo℠ Scrum is…

» an iterative, incremental process wherein separated teams and bifurcated responsibilities work via a producer-consumer model with a pipeline ap h contains a fix key.

» Ea » De f

fun » Ea etermines

wh showing the en ld. Im prove their pro

» Du nd reports on

» Us ty. There is on ved.

» In hat owns the e shepherd for the scrum team (not a PM), are two new roles that need to be accounted for. The PM and Architect roles & responsibilities are modified significantly.

» The primary metric the teams are attempting to improve is their velocity, the actual speed at which the team is delivering functionality to the business. Predictability is a goal.

31

Agile Methodologies – Short Descriptions Kanban is…

» an incremental process wherein a small team of fixed size works over a continuous demand-driven cycle [there are no timeboxes] repeatedly pe

» Tr ange.» Ca rive

im» De lity

de » Ne handle it,

rat rd is com ch is the lis

» De quency as fea occur with reg

» Th work, not the

» Th hput of the team and the cycle time of each type of request received, which is the actual speed at which the team is delivering functionality to the business. Predictability is a goal.

» We’ve found that this works well for AVM and backend-type projects.

32

ValuesValues are the foundation for all the activities and artifacts for a project following an Agile methodology.

Agile V» Co usiness by

or » Co

un» Re » Op are open to

pe » Fo

Scrum » Tra » Ins ess» Ad eamline the

pro

35

SC S

36

Pigs and ChickensThe importance of knowing who’s on the critical path and who’s not

On scr t i di id l i ith i hicken. The sto

» A p o the pig, “he

» The nt to call it?” s”.

» “I d » The

Chicke ted to the pro lowed to talk in

» On a scrum team, product owners, story authors, developers and testers are the pigs while everyone else is a chicken.

42

Key Mandatory MeetingsSprint Estimation

» Purpose: Estimate the effort/complexity/duration for stories in the product backlog» Frequency/Duration: once a week, timeboxed to 1 hr. one held for each scrum team.» Attendees: product owner, scrum master & team, architects, analysts, et al. » Format: F » Process: s ner answers

questions y.

Sprint Plann» Purpose: » Frequency » Attendees » Format: F » Process: s eak stories down

into techn

Sprint Revie» Purpose: » Frequency » Attendees » Format: F » Process: P w functionality.

Retrospectiv» Purpose: process improvement» Frequency/Duration: last day of the current sprint, after the demo. Usually 30 mins – 1 hr. » Attendees: each scrum team has their own.» Format: F2F and conf call for offsite/remote» Process: product owner facilitates concept teams. Scrum master facilitates delivery teams. Cover these topics:

Accolades, What went well, What we could have done better, Ideas to try in the next sprint

45

The Rules “One Team” Approach

» Like the origin of the Rugby term scrum, where all team members are supposed to lock arms and push together to move the ball forward, team members should work together in a complementary manner toward the sprint goal

» All s » Whe the entire

scru ough team mem eed to step up t hem – not say

» If an eveloper stuc

» The s a team.

The Tim» The t.» Onc

The Sco» Any – even for

“clarifications» Once a set of stories are committed to by a scrum team, stories should not be removed or

swapped out of the resulting sprint backlog during the sprint - unless the scrum team unanimously agrees with the request.

» Stories may be added by the team if they complete their sprint backlog early.

47

IN

48

The Introduction Brochure Introduce yourself to your team members using a “brochure”.

Don’t worry – it’s easy!

Follow 1. Id

• • • places•

2. Id • • •

3. Id what new te

Document these on the template provided and present yourselfto your colleagues.

49

Schedule for todayTopic Leader Duration Time (ET)Introductions Dan 10 mins 8:00 – 8:10

Requiremen 10 – 8:45

Kickstart – 45 – 9:40

-- break -- 40 – 9:50

Kickstart – P 0 – 10:30

Fundament 30 – 11:30

Introduction 30 – 12:00

-- lunch -- 00 – 12:45

White Eleph 45 – 1:30


-- break -- 30 – 2:45


Wrap-up Brian 15 mins 3:45 – 4:00

50

AC

51

White Elephant Sizing

52

How it works: There are two roles: a Product Owner and the team.

» The Product Owner has a stack of user stories ready to be estimated.» The ill i i f

There is The gam (can also be

accompl

There ar a turn. During the first bsequent rounds,

Every te mber may:» Get oard» Mov » Afte th the story

pla» Wh

Team m t discuss the story wi

The game ends when all stories are placed on the board and everyone decides to “pass”.

SC

53

Preparation for Sprint 1 This is sometimes known as “Sprint Zero” Checklist:

» Fo roles» Tr ry» PO am» Cr ories)» Ag

ag» Se » Ag » Ho

54

Team AgreementsEvery scrum team must have a few documents that they all agree upon. These include:

The D

Story

At wh design doc b

Produ » W » Ho » What are their “extended business hours”?

55

User Story Examples

Good examples» As ses so that

I o » As an choose

the » As ave to

en » As my

ne

Bad e» Ou viewpoint)» Ne » Th ue)» A u » Sh

58

Epics Revisited

What » An mentable

Wher » Ep h may

inc c.

How d » Ask a developer or tester

64

Example EpicDescription: As an end user I need to find a pediatrician health care provider

kids to the

AcceptancCriteria:

their address, on a map.

Attributes of a Good Story = INVEST Independent – user stories should be decomposed to the point that there are no

dependencies between stories; this is more of a guideline than a rule

Negoti hat must be implem een the concep

Valuab efits to the custom s opposed to guesse

Estima y team. If they ca domain knowle

Small just enough informa se story. (Usuall per to build it and t

Testable – all user stories should be testable, and 99% of the functionality described in user stories should be able to be tested by automation

65

Guidelines for Writing Good User Stories Write goal-oriented stories that originate from a particular role, persona or point of

view.

Stories should contain only one viewpoint not many

Write in “The button may be

Slice th ugh the product ercise the entire a er than later.

Write a details to the hap

Write cl eaningful goal tha o meaning that eac

Stories

User int scriptions of the functionality and attach diagrams or pictures of the screens, and include details in an attached wireframe.

Include constraints in a NOTES section – e.g. website must run on IE8, Safari, and Firefox

66

Guidelines for Better Acceptance Criteria Describe where the story begins and any initial automated action, like a pop-up screen

Describe any follow-on actions during or after the user performs the activity, such as mouse-overs

Does ev

Does th

Is every

Cannot at you need to break it

Are ther hem to the AC.

Keyword a list of specific

Attachm» “mo

» busi

» diag ty

If a grou individual roles

Negative statements (“Nurses should not be able to…”), technical constraints (“this app should work on the iPhone”), and contextual information should not be in the AC

67

ESS WO

69

User Story Review

Good examples» As ses so that

I o » As an choose

the » As ave to

en » As my

ne

Bad e» Ou viewpoint)» Ne » Th ue)» A u » Sh

71

Story Estimation Weekly meeting for one hour facilitated by Scrum master

All scrum team members participate. Product owners must attend. Architects, Project Managers, User Experience groups may be invited, but may not speak.

Stories a is the opposite of confid

Team me » Effor sizes» 1 me means it’s average» If th » 13 m » 21 m

Agile “plan e meeting and distributed

The proc1. The the story.2. The echnical tasks need

to be .3. For u with a “one-two-

thre4. The why they believe

it is more or less difficult than their peers expect.5. The scrum master repeats the votes until the numbers converge and the team as whole can agree.6. The scrum master asks the testers if they need to adjust the effort estimate.7. The scrum master assigns the total effort points to the story, a.k.a “the plan estimate.”8. Repeat until there are no more stories or the allocated time for the meeting is exhausted.

75

Sprint Planning Sprint Planning occurs on the first day of each sprint. It is usually 2-3

hours.

Sprint 1. Th team

ac • am commit to

2. Th se them as ne

3. Th • y during this

4. Th • g it down into

ailable time is exhausted.

• Committed stories are moved to the sprint backlog

76

Design Reviews

77

After the story has been committed, the developer(s) that volunteered have as their first task: perform analysis and design.

These minutes to a cou » Th ,

co » If ctual

de • rt, but

e the story

• the design

• make sure

ory, and to make sure the product owner understand s what will be be built.

Scrum Meetings Daily Scrum

» Purpose: for team members to synchronize their work» Frequency/Duration: every business day, same time, same location. Short, timeboxed to 15 mins.» Atte ct Managers,

Ana » For » Pro s attached):

•

• n story 588 and

•

» Aft ndown and

dis nt backlog» NO

Scrum » Pur » Fre to 15 mins.» Atte s should attend

but not speak.» Format: conf call» Process: In turn each product owner and scrum master describes

• What did my team accomplished yesterday?• What will my team accomplish today?• What’s blocking my team from completing their work?

78

Testing Testing in Scrum is integrated into the sprint. Testing must complete prior

to asking the product owner for story acceptance.

All tes » Th vious

spr» Th possible.

There » Th be complete

wi » A t h the

acc eveloper so tha

Should component is now ation and determine if the discovery may be overcome in the sprint, or if it warrants a new story.

79

Grooming and Forecasting When: in the off-week Who: product owner, scrum master and team Durati How: y) by

the sc

Groom he order of the

Foreca scuss what s rints (based n stories.» Pro sks if there

are ed in the nex

» Thi f there’s enough on the product backlog.

80

Story Acceptance Near the end of the sprint, the developer should notify the product owner

that the functionality has been built and tested, and it is ready to be accepted.

Story all of the accept

If the st clearly and sp » If r to the

de nto the next spr ed in the ret

81

Sprint Review Also known as “the Demo” When: A meeting on the last day of the sprint. Who: Everyone on the project is expected to attend Duratio How: T ted by the

scrum Deliver

The ag» The e sprint.

Sec for each tea mins total.

» Sho the new fun ponsors, ask

» Dis will quickly wa built and the tec ica c a e ges e cou te ed. i eboxed to 10 i s o each team.

83

The Retrospective When: The retrospective is a meeting on the last day of the sprint, usually

after the demo. Purpose: find ways to improve, adapt and learn for the next sprint. Who: E ate. Duratio How: T Deliver

Discus » Acc» Wh » Wh » Ide » Ove » Rev

• ght?

86

WR

87

Point Go Throw game

88

Required: a tennis ball (or a ball small and soft)

Goal: to sh th t i l i t ti lt i diffi lt t rform activit ly

Team e team memb immed “GO”, and the pe

If, at a meone in the cir

Try to

Learnings Performing Agile/Scrum successfully is difficult.

The Agil /S i hi hl t t d d ill d more docum

Agile/S functio e plan.

It tak Understand the or e mental shift re » Kn ts to learn

to

Agile/S le. Every memb what to do to mak ( )

Early sprint results will be uneven; look for trends. Don’t be alarmed by great results in sprint 2 but poor results in sprint 3.

90

Thank you!

This is the end of Agile Training for College Hires – Day One

The p good techn eal issues

Today » Th » Tip g from

es ve» Ho

91

welcome to agile training

Documents