Introduction to ScrumHasan Jaffal, PMP, CSM

Thanks to our sponsors

GOLDSILVERBRONZEHOST

THANKS TO OUR

MEDIA PARTNERSECO-SYSTEM PARNERSSUPPORT SPONSORS

ORGANIZER

AgendaWhats a Project? The Traditional SDLCThe Agile WayScrum Framework: Process, Roles, Meetings and Artifacts

Whats a Project?PROJECT: According to the PMBOK Guide, Fifth Edition, a Project is a temporary endeavor undertaken to create a unique product, service or resultNOT PROJECT: An ongoing and repetitive work

Temporary means having a definite beginning and end. The end is reached when the projects objectives have been achieved or if the project is terminated for any reason.Temporary does not mean short in nature, and it could well be a 10 years project for example, sending a man to moon, Building the AUB Campus

An ongoing work effort is generally a repetitive process because it follows an organizations existing procedures. The ongoing execution of activities that produce the same result or product repetitively is what Operations is all about.

Project vs Operations

Project

Always has a start and end date.Produces a unique product, service or result.

OperationOngoing process of functionsAlways produces the same product, service, or result

The Traditional Grant IdeasRequirementsDesignDevelopmentTestingMaintenance

Waterfall Development is the traditional approach toSoftware DevelopmentChanges

Takes Too Long

Skipped

You complete one phase (e.g. design) before moving on to the next phase (e.g. development)You rarely aim to re-visit a phase once its completed. That means, you better get whatever youre doing right the first time!You dont realize any value until the end of the project You leave the testing until the end You dont seek approval from the stakeholders until late in the dayThis approach is highly risky, often more costly and generally less efficient than Agile approaches

The Traditional Grant IdeasIn 1970, Dr. Winston Royce published Managing the Development of Large Software Systems, in which the waterfall paradigm was first documented. He said:I believe in this concept, but the implementation described above is risky and invites failure.

You complete one phase (e.g. design) before moving on to the next phase (e.g. development)You rarely aim to re-visit a phase once its completed. That means, you better get whatever youre doing right the first time!You dont realize any value until the end of the project You leave the testing until the end You dont seek approval from the stakeholders until late in the dayThis approach is highly risky, often more costly and generally less efficient than Agile approaches

Agile Development

RequirementsDesignDevelopmentTestingMaintenance

RequirementsDesignDevelopmentTestingMaintenance

Manifesto for Agile Software Development Individual and interactionsProcess and toolsOverWorking SoftwareComprehensive documentationOverCustomer CollaborationContract negotiationOverResponding to changeFollowing a planOver

This doesn't mean we don't value the RED thingsbut we value the GREENS ones more

Agile Methodologies

Kanban3

Scrum9

13XPMore Adaptivefewer rules to followMore Prescriptivemore rules to follow

120+RUP

The Scrum Process

Sprint Review

ProductBacklog

Potentially Shippable Increment

SprintBacklog

1-4 WEEKS

24 Hours

Scrum projects make progress in a series of sprintsTypical duration is 24 weeks or a calendar month at mostA constant duration leads to a better rhythmProduct is designed, coded, and tested during the sprint

Backlogs

This is the Product BacklogThis is the Sprint Backlog

The requirementsA list of all desired work on the projectIdeally expressed such that each item has value to the users or customers of the product Prioritized by the product ownerReprioritized at the start of each sprintAnalyze and evaluate product backlog to select sprint goalCreate sprint backlog (tasks) from product backlog items (user stories / features)Estimate sprint backlog in hoursIndividuals sign up for work of their own choosing, Work is never assignedEstimated work remaining is updated daily

Sprint backlog is createdTasks are identified and each is estimated (1-16 hours)Collaboratively, not done alone by the ScrumMaster Work is never assigned

Individuals sign up for work of their own choosingEstimated work remaining is updated daily

Backlogs

As a player I want to see the enemy appear closer when I use my sniper scope so I am able to see them from long distances As an Origin user I want to want to know which of my friends is onlineAs a tourist visitor of the site I should be able to submit my reservation online so the hotel administration can confirm itAs a , I want so that .

Should be focused on the userSimple and clearPrioritizedUser Story Template

BacklogsBacklog itemEstimateAllow a guest to make a reservation3As a guest, I want to cancel a reservation.5As a guest, I want to change the dates of a reservation.3As a hotel employee, I can run RevPAR reports (revenue-per-available-room)8Improve exception handling8...30...50

Scrum Roles

Team

Scrum Master

Product Owner

Scrum Roles / Product OwnerDefine the features of the productPrioritize features according to market value Adjustfeatures and priority every iteration, as needed Accept or reject work results

Scrum Roles / Scrum MasterResponsible for enacting Scrum values and practicesRemoves impediments Ensure that the team is fully functional and productiveEnable close cooperation across all roles and functionsShield the team from external interferences

Scrum Roles / The TeamTypically 5-9 peopleCross-functionalMembers should be full-timeTeams are self-organizing

Scrum Ceremonies - Sprint PlanningSelect sprint goalTeam selects items from the product backlog they can commit to completingSprint backlog is createdTasks are identified and each is estimatedCollaboratively, not done alone by the ScrumMasterAs a vacation planner, I want to see photos of the hotels.Code the middle tier (8 hours)Code the user interface (4)Code the class (6)Update performance tests (4)

(1-16 hours)

Any team member can add, delete or change the sprint backlogWork for the sprint emergesIf work is unclear, define a sprint backlog item with a larger amount of time and break it down laterUpdate work remaining as more becomes known

Scrum Ceremonies - Daily MeetingNot for problem solvingWhole world is invitedOnly team members, ScrumMaster, product owner, can talkHelps avoid other unnecessary meetingsDaily 15-minutes Stand-up

Scrum Ceremonies - Sprint ReviewTeam presents what it accomplished during the sprintTypically takes the form of a demo of new features or underlying architectureInformalWhole team participatesInvite the world

Scrum Ceremonies - Sprint RetrospectiveThe sprint retrospective is usually the last thing done in a sprint.

Where to go nextOther roomsSome of the slides of this presentation are created by www.mountaingoatsoftware.comwww.scrumalliance.orgwww.controlchaos.comwww.scrum.org

Thank YouHasan Jaffal

www.jaftalks.comjaftalks@icloud.com