an agile/scrum primer

46
An Agile/Scrum Primer Jen Harris, CSM & Steve Curtis, CSM Project Managers, CivicActions

Upload: jen-harris

Post on 19-May-2015

57 views

Category:

Technology


2 download

DESCRIPTION

An introduction to Agile and Scrum for staff at The Ad Council.

TRANSCRIPT

Page 1: An Agile/Scrum Primer

An Agile/Scrum Primer

Jen Harris, CSM &Steve Curtis, CSM

Project Managers, CivicActions

Page 2: An Agile/Scrum Primer

Agile vs. Waterfall

Page 3: An Agile/Scrum Primer

Agile vs. Waterfall

What is traditional or “Waterfall” project management?

Page 4: An Agile/Scrum Primer

Agile vs. Waterfall

What is traditional or “Waterfall” project management?

The waterfall model is a sequential process, in which progress is expected to flow steadily downwards through various phases.

Page 5: An Agile/Scrum Primer

The waterfall model is a sequential process, in which progress is expected to flow steadily downwards through various phases.

Page 6: An Agile/Scrum Primer

What is Agile?

Page 7: An Agile/Scrum Primer

What is Agile?

Page 8: An Agile/Scrum Primer

What is Agile?

Agile project management is an iterative method of determining requirements for engineering and information technology development projects in a highly flexible and interactive manner.

Page 9: An Agile/Scrum Primer
Page 10: An Agile/Scrum Primer

What is Scrum?

Page 11: An Agile/Scrum Primer

What is Scrum?

Scrum is one version of the Agile process.

It was developed in 1993 and has at its foundation the principles and values set forth in the Agile Manifesto.

Page 12: An Agile/Scrum Primer

Why is it called Scrum?

Page 13: An Agile/Scrum Primer

Why is it called Scrum?

The term "scrum" was borrowed from an analogy put forth in a 1986 study published in the Harvard Business Review. In that study, the authors compare high-performing, cross-functional teams to the scrum formation used in Rugby.

Page 14: An Agile/Scrum Primer

3 Scrum Roles

Page 15: An Agile/Scrum Primer

Product Owner

Responsible for the business value of the product.

The PO is a subject-matter expert, end user advocate, customer advocate, business advocate, communicator, decision maker, risk assessor.

Page 16: An Agile/Scrum Primer

ScrumMaster

Ensures that the team isfunctional and productive.

Keeps the team focused.

SM is facilitator, assistant,Scrum coach/mentor, enforcerof time-boxing, mediator, riskassessor.

Page 17: An Agile/Scrum Primer

Scrum Team

Self-organizes to get the work done.

Page 18: An Agile/Scrum Primer

3 Scrum Artifacts

The artifacts are tangible itemsnecessary for communication and transparency.

Page 19: An Agile/Scrum Primer

Product Backlog

A wish-list of requirements/specifications for the product, prioritized according to business value by the Product Owner.

This list can be constantly re-prioritized and added to as new requirements and issues come to light.

Page 20: An Agile/Scrum Primer

Sprint Backlog

A subset of work from the Product Backlog that the Team agrees to complete during a Sprint.

Prioritized requirements are further broken into tasks during Sprint Planning.

Page 21: An Agile/Scrum Primer

BurndownA visual representation reflecting the “velocity” at which work is being completed.

Updated daily by the ScrumMaster to communicate how much work and time remains in the Sprint. Shows at a glance whether or not the Sprint is on schedule.

Page 22: An Agile/Scrum Primer

3 Scrum Ceremonies

Page 23: An Agile/Scrum Primer

Sprint PlanningA meeting at the beginning of the Sprint cycle during which the Team selects a subset from the top of the prioritized Product Backlog – a set of requirements that they feel they can commit to completing during the Sprint.

Page 24: An Agile/Scrum Primer

Sprint Planning

Based on this subset (aka the Sprint Backlog), the Team and theProduct Owner decide on goals for the Sprint.

The Team further breaks down requirements into tasks and estimates thework.

Page 25: An Agile/Scrum Primer

Daily Scrum

A brief (15-20 minute) meeting convened by the ScrumMaster, to report on progress, identify any blockersto productivity, and adjust work assignments based on what's happening.

Page 26: An Agile/Scrum Primer

Daily Scrum

What have I worked on since the last Scrum?

What will I be working on between now andthe next Scrum?

Do I have any blockers?

Page 27: An Agile/Scrum Primer

Sprint Demo

Work completed in the Sprint is often demoed by the person who completed it, which builds accountability and thoroughness.

Page 28: An Agile/Scrum Primer

Retrospective(bonus)

A meeting where Team members can share experiences and results from the Sprint in order to improve communication, productivity and workability during the next Sprint: a space for honest feedback.

Page 29: An Agile/Scrum Primer
Page 30: An Agile/Scrum Primer

Case Studies...

Page 31: An Agile/Scrum Primer

170 Million Americans

Page 32: An Agile/Scrum Primer

170 Million Americans

American Public Media (APM) approached CivicActions in November 2010 to quickly produce an enticing campaign site to highlight public media and its funding in the USA, attract partner public media stations (to date over 250 stations have signed up) and encourage users to show their support for public media.

Page 33: An Agile/Scrum Primer

170 Million Americans

CivicActions used an Agile/Scrum approach to implement the basic functions of the 170MillionAmericans.org website, demo the site to stakeholders, and rapidly respond to stakeholder input.

The website was started, completed and launched within 2 weeks of kickoff.

Page 34: An Agile/Scrum Primer

170 Million Americans

RESULTS

Within a few weeks, American Public Media had over 127,921 Facebook fans, and activists persuaded Congress to preserve the entirety of the $445 million in government funding that supports public broadcasting. To date the website has a conversion rate of over 52% for users completing the sign-up form.

Page 35: An Agile/Scrum Primer

Greenpeace UK Mobile

Page 36: An Agile/Scrum Primer

Greenpeace UK MobileGreenpeace UK approached CivicActions in the summerof 2012 to make their existingsite more accessible to theirmobile users. Reports hadshown that nearly half of theirpage views were from mobiledevices.

Page 37: An Agile/Scrum Primer

Greenpeace UK MobileCivicActions' work with GPUK was designed to be carried out during a short sprint with a small team: just two engineers over a two week period. With dozens of types of content and over two-hundred thousand individual pieces of content, Greenpeace understood that making their mobile site 100% friendly was not achievable.

Page 38: An Agile/Scrum Primer

Greenpeace UK MobileWith our Agile practices, we supported them in writing and prioritizing the most important user stories* for mobile visitors.

In this way, we developed a focus on functionality, and on sections of the site devoted to fundraising, subscriptions, campaign pages and blogs.

*User stories capture the 'who', 'what' and 'why' of a requirement in a simple, concise way.

Page 39: An Agile/Scrum Primer

Greenpeace UK MobileMain impact of implementing Scrum was our ability to continuously reassess priority vs. deliverability within a short timeline and on a limited budget.

Page 40: An Agile/Scrum Primer

Greenpeace UK MobileRESULTS

"The mobile site is really impressive, and I honestly think we're setting a new standard in the charity sector in the UK." - Jamie WoolleyHead of Digital Communications, Greenpeace UK

Page 41: An Agile/Scrum Primer

Every Beat Matters

Page 42: An Agile/Scrum Primer

Every Beat Matters

Ad Council and Save the Children approached CivicActions in the summer of 2012 to quickly assist with getting the Every Beat Matters campaign website and mobile site launch-ready.

The EBM site had been designed and built by a third party vendor (BBDO), but still had some tweaks and bugs to be resolved before launch.

Page 43: An Agile/Scrum Primer

Every Beat Matters

CivicActions was able to step in and used an Agile approach to complete and launch the Every Beat Matters website and mobile site within approximately two weeks.

The main impact of the Agile/Scrum approach was our ability to respond quickly to evolving business requirements in days prior to launch.

Page 44: An Agile/Scrum Primer

Every Beat Matters

RESULTS

To date, Every Beat Matters has over 3,000 Facebook fans and over 3,500 followers on Twitter, and ...

Page 45: An Agile/Scrum Primer

Resources & Training

Page 46: An Agile/Scrum Primer

?