Agile Software Development & Scrum: An Introduction

3y ago
117 Views
13 Downloads
3.03 MB
56 Pages
Last View : Today
Last Download : 6m ago
Upload by : Lucca Devoe
Transcription

ScrumThe EssenceTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

What is Scrum?Scrum is a framework thatallows you to create yourown lightweight process fordeveloping new products.Scrum is simple.It can be understood andimplemented in a few days.It takes a lifetime to master.“Scrum is not a methodology– it is a pathway”– Ken Schwaber (Boulder, Co, Nov. 2005)Tobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

The Empirical ProcessPlanExecuteReflectThe Core of ScrumTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

When is Scrum Appropriate?Requirements Scrum works bestwhen the problems tobe solved lie in theComplex Space. New ProductDevelopment Workand Knowledge Workboth tend to exist inthe Complex Space. Research lies in theAnarchy spaceTechnologyTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12 Maintenance lies inthe Simple Space

The Curve of Changethe Virginia Satir Change Process ModelThe situation sometimes gets worse before it gets betterTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

The Scrum atePush Your EdgeTake RisksDare to FailTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Scrumis aDanceFollow the rules anddiscover your team’sinnate creativityBreak the rules andwatch it all fall apartTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Scrum will helpyou fail in 30days or less-- Ken Schwaber, c2001Tobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Scrum bias Mayer, http://agilethinking.netSonntag, 19. Februar 12

The Scrum Foundation tionRhythmTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

EmpiricismDetailed up-front planningand defined processes arereplaced by just-in-timeinspect and adapt cyclesTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Self-organizationSmall teams manage their ownworkload and organize themselvesaround clear goals and constraintsTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

CollaborationScrum leaders, product visionaries andcustomers collaborate with developers –they do not manage or direct themTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

PrioritizationWork on themost importantthing – do notwaste timefocusing onwork that doesnot addimmediate valueTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

RhythmTimeboxing creates the rhythmthat drives developmentTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

With a solidfoundation your process, your design and yourproduct will emerge in the way mostappropriate to your contextTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

EmergenceThe beauty of letting go, and trustingTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

ScrumPeopleTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Scrum RelationshipsScrum MasterThe Team3-7 peopleProduct OwnerEnd UsersTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12StakeholdersThe WiderOrganization

Product OwnerThought Leader & VisionaryDrives the Product VisionMaintains the Product BacklogPrioritizes the RequirementsAccepts the Working SoftwareTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Scrum MasterTrouble Shooter& Servant Leader Manages the Process Supports the Team Removes Organizational Impediments Socializes Scrum to ManagementTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

The TeamTobias Mayer, http://agilethinking.netSonntag, 19. Februar 125-8 untable forMeeting Commitments

Team SizeTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

ScrumPlanningTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

VisionStatementA short statementof intentA goal to aspire toTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

ProductBacklogA living list ofrequirementsThe ProductBacklogrepresents theWHAT of thesystemPrioritization isessential!Tobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Request/Response ModelTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Planning 1The team meets withthe PO to discusspriorities, refine thestories, and determineacceptance criteria.This happens initiallybefore developmentand then iteratively,every sprint.Tobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Feature Prioritization Deliver thehighest valueearly on But don’tneglect thebigger pictureTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Planning 2Occurs at the start of each sprint. Team and POnegotiate the commitment, then the team membersbegin the design process and generate tasksTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Sprint GoalThe vision for the sprintThe Sprint Goal is anegotiated agreementbetween Product Ownerand TeamTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

ScrumExecutionTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Sprint BacklogThe CommittedStories and a list oftasks representing theHOW of the systemThe Sprint ‘To Do’ Listis owned andmanaged by the TeamTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Daily Scrum15 Minutes 3 Questions1. What did I complete in the past 24 hours?2. What do I commit to in the next 24 hours?3. What is getting in my way?Tobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

ImpedimentListA list of organizationaland team impediments– with suggestedsolutionsThis list is maintainedby the Scrum MasterTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Story BurndownTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Team Task BoardTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Example Task BoardTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

“Done” Example checklist for working software––––––––Unit tests passCustomer Acceptance tests passUser docs writtenUI design approved by POIntegrated into existing systemRegression test/s passDeployed on staging server Tobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Working SoftwareTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

ScrumReflectionTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

ReviewOccurs at the end of each sprint.Inspect and Adapt the product.The team meets with the Product Ownerand the Stakeholders to demonstrate theworking software from the sprint.Tobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

RetrospectiveOccurs at the end of each sprint.Inspect and Adapt the process.The team meets with the Scrum Master tolook at what went well and what can beimproved.Retrospectives must concludewith individual commitmentsto action.Tobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Velocity GraphTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

ScrumIn More DetailTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

TheScrumFlowTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Planning 1Product BacklogVague StoriesPlanning bias Mayer, http://agilethinking.netSonntag, 19. Februar 12in detail.Pruned BacklogRefined StoriesEstimations

Planning 2Product BacklogPrioritized StoriesPlanning 2ProductOwnerTheme.Sonntag, 19. Februar 12Committed StoriesTask List (sprint backlog)Sprint GoalScrumMasterTobias Mayer, http://agilethinking.netTeamin detail.

Daily Scrumin detail.Problems.Daily ScrumImpediment ListCompleted TasksScrumMasterCommitmentsTeamAdditional MeetingsProductOwnerTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

ReviewCommitted StoriesWorking SoftwareVision Statementin crumMasterTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12New StoriesAccepted Software(Updated Vision)

RetrospectiveMetricsImpedimentsReflectionsTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12RetrospectiveScrumMasterTeamin detail.Ideas for ChangeCommitmentsImproved Process

ScrumWhat next?Tobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Change.Nothing of him that doth fadeBut doth suffer a sea-changeInto something rich and strange.William Shakespeare, “The Tempest”Tobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Take ActionWhat will you do on your first day back atwork to initiate change?Make a commitment to someone on thiscourseWrite it down, sign it, exchange emailsFollow up!Tobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Top Five Five books that Irecommend tocultivate the AgileMindset– Surfing the Edge of ChaosPascale, Milleman & Gioja– SlackTom De Marco– Artful Making:Rob Austin and Lee Devin– User Stories AppliedMike Cohn– Scrum & XP from theTrenchesHenrik KnibergTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12Top five chairs made out of trash: something from nothing

where to now?Start here:Bay Area Agile Project Leadership Networkhttp://bayAPLN.orgTobias Mayer, http://agilethinking.netSonntag, 19. Februar 12

Scrum is a framework that allows you to create your own lightweight process for developing new products. Scrum is simple. It can be understood and implemented in a few days. It takes a lifetime to master. “Scrum is not a methodology – it is a pathway” – Ken Schwaber (Boulder, Co, Nov. 2005) What is Scrum? Sonntag, 19. Februar 12

Related Documents:

This Scrum and Scrum Master Guide is a free, quick reference material designed to help aspiring scrum masters discover the ins and outs of Scrum. It throws light on the fundamental principles of the scrum, scrum terminologies, Agile Manifesto, scrum theories, scrum tools, different roles, responsibilities, and more. SCRUM & SCRUM MASTER

Agile Estimating and Planning by Mike Cohn Agile Game Development with Scrum by Clinton Keith Agile Product Ownership by Roman Pichler Agile Project Management with Scrum by Ken Schwaber Agile Retrospectives by Esther Derby and Diana Larsen Agile Testing: A Practical Guide for Testers and Agile Teams by Lisa Crispin and .

Training Formal Change Management training for key positions Agile certification -Product Owner -Scrum Master Agile team -Led by Scrum Master -Two day, self-paced Agile frameworks -Kanban: maintenance -Scrum: enhancements Scrum teams -Size: 7 2 -Team members Dedicated Scrum room Master Scrum Master

EXIN Agile Scrum Master is a certification that looks to confirm both skills and knowledge of the Agile framework and Scrum methodology. Agile Scrum is about working together to successfully reach a goal. Agile methodologies are popular approaches in software development and are increasingly being used in other areas.

The most popular agile methodologies include: extreme programming (XP), Scrum, Crystal, Dynamic Sys-tems Development (DSDM), Lean Development, and Feature Driven Development (FDD). All Agile methods share a common vision and core values of the Agile Manifesto. Agile Methods: Some well-known agile software development methods include: Agile .

Agile development method - Scrum is one of the growing development methods in software projects [13]. Scrum is a process skeleton that includes a set of practices and predefined roles [13, 14]. The Scrum team composed of Scrum master, Product owner and development team. A set of practices include Scrum sprint and Scrum meetings.

Agile Software Development with Scrum Jeff Sutherland Gabrielle Benefield. Agenda Introduction Overview of Methodologies Exercise; empirical learning Agile Manifesto Agile Values History of Scrum Exercise: The offsite customer Scrum 101 Scrum Overview Roles and responsibilities Scrum team Product Owner ScrumMaster. Agenda Scrum In-depth The Sprint Sprint Planning Exercise: Sprint Planning .

Agile software development therefore has a focus on: . Scrum is one of the most popular agile development methodologies. Scrum is a lightweight framework designed to help small, close-knit teams of people to create complex software products. The key features of the scrum methodology are as follows: Scrum team: A team of people using this methodology are called a “scrum”. Scrums usually .