scrum implemented in an educational context

SCRUMRody Middelkoop

Thursday, March 18, 2010

Scrum - HvA - Rody Middelkoop

http://blogs.seattleweekly.com/dailyweekly/scrum.jpg




3


Agenda

9:00 - 9:30 Introductie:

ICA->Semestermodel->DDOA Processen:

Projectmanagement & Softwareontwikkeling Agile Development

9:30 - 11:30 Scrum in Theory and Practice Theorie 60 min Workshops / Demo

Sprint Planning: 45 min. Standup-meeting: 15 min.

11:30 - 12:00 Scrum toegepast in DDOA


ICAThursday, March 18, 2010

5


ICA

Informatica en Communicatie Academie Instituut van de faculteit Techniek van de HAN Brede opleidingen

Bedrijfskundige Informatica Communicatie en Multimedia Design Digitale Communicatie Informatica Technische Informatica

Flexibele leerroutes, beroepstaken, competentiegericht


6


Propedeuses en Opleidingen

Bedrijfskundige InformaticaInformaticaTechnische Informatica Communicatie & Multimedia Design (I)

Communicatie & Multimedia Design (C) Digitale Communicatie

Informatica propedeuse

Communicatie propedeuse


7


Semestermodel


8


DDOA Semester

Project

7.5 + 7.5 EC

15 EC

tijd


9


Beroepstaak

“Ontwikkel een gedistribueerde OO applicatie” Richt zich op veel aspecten van een software

engineeringsproject: analyseren, ontwerpen, bouwen, testen, implementeren

Voorbeelden: HAN: Senior Navigator Human Inference: Collaborative Knowledge Verifier Avisi: JIRA Timesheet Plugin Luminis: JMX Console VXCompany: Mister Match InfoSupport: JavaFX Standapp


10


Eigenschappen DDOA

Software opleveren van hoge kwaliteit 10 tot 12 projectgroepen van 5 studenten Integratie van techniek en social skills Aandacht voor volledige ontwikkelproces Externe opdrachtgevers: 2Pro, Accenture, Avisi, E-ID,

HAN, InfoSupport, ITude, Logica, Lucka, Luminis, Profict, Sogyo,VXCompany

Aandacht voor open/ shared source (Atlassian) Tooling: Eclipse, Subversion, Ant, JUnit, Jira,

Confluence, Bamboo


ProcessThursday, March 18, 2010

12


Softwareontwikkel-proces:RollenProductenVerantwoordelijk-hedenFasering: Analyse, Ontwerp, Bouw, Test, Oplevering

Processen

Projectmanagement-proces: Geld Organisatie Kwaliteit Informatie Tijd


12


Softwareontwikkel-proces:RollenProductenVerantwoordelijk-hedenFasering: Analyse, Ontwerp, Bouw, Test, Oplevering

Processen

Projectmanagement-proces: Geld Organisatie Kwaliteit Informatie Tijd

Scrum?


13


Process: which one works.....

DSDMWaterfall

RUP

Essential UPAgile?

Spiral

XP

Prince2


13


Process: which one works.....

DSDMWaterfall

RUP

Essential UPAgile?

Spiral

XP

Prince2

Scrum?


14


Click to edit Master text styles

Process: Waterfall

BDUF: Big Design Up Front

Documentation is important

Clear phases and milestones

Well known by projectmanagers

http://www.software-development-resource.com/images/waterfall_software_process.jpg




15



Process: Unified Proces

Incremental and iterative

Inception, Elaboration, Construction, Transition

Risk mitigation: prototypes

Architectural relevant use case(s)

Describes roles and workproducts in detail

http://era.nih.gov/docs/rup_fundamentals_slide03.jpg




Agile

http://globalnerdy.com/wordpress/wp-content/uploads/2007/11/dilbert-agile_programming.gif




17


What’s our problem

We are skilled problem solvers, experts at devising long-lasting solutions. “The problem in our profession is not process or technology …it is people and dysfunctional interactions. It can only be solved person by person.”

Business value - it is hard to focus on what the customer really needs.


18


Communication


19


Agile development

Agile Manifesto: Individuals and

interactions Working software Customer collaboration Responding to change

processes and toolscomprehensive documentationcontract negotiationfollowing a plan

That is, while there is value in the items on the right, we value the items on the left more.


20


Agile development

Testing early and automated Incremental design Daily deployment Customer involvement Continuous integration Short deployment cycles Incremental planning


21


Agile playground

Well known methods: DSDM Scrum Extreme Programming Lean

Lots of combinations possible Smart


22


Plan-driven home ground✓ High criticality✓ Junior developers✓ Requirements do not

change often✓ Large number of

developers✓ Culture that demands

order

When to do agile (Boehm/Turner)

Agile home ground✓ Low criticality✓ Senior developers✓ Requirements change

often✓ Small number of

developers✓ Culture that thrives

on chaos


Scrum: Theory/PracticeThursday, March 18, 2010

24


Scrum in a nutshell

Empirical management & control process – inspect and adapt feedback loops

Used to manage complex projects since 1990 Delivers business functionality in 30 days Scalable to distributed, large, and long projects Extremely simple but very hard “Scrum provides the mechanism for making the

people problems apparent so they can be solved and helps customer back in driver seat.”


25


Scrum origins

Jeff Sutherland Initial Scrums at Easel Corp in 1993 IDX and nearly 600 people doing Scrum Not just for trivial projects: FDA-approved, life-critical software for x-rays and MRIs

Ken Schwaber: ADM (Advanced Development Methods) Initial definitions of Scrum at OOPSLA 96 with

Sutherland Mike Beedle

Scrum patterns in Patterns book: PLOPD4


26


Scrum values

Commitment (Teamwork) Focus Openness

Enabler of Honesty Provides Transparency)

Respect Courage


27


Scrum values

“We believe in [value] therefore we will [do something].”

For example, your team might come back with: We believe in respect, therefore we will show up on time

for all meetings.


28


Scrum process

http://www.russianit.info/en/scrum/scrum_large.gif




29


Scrum levenscyclus


30


Scrum levenscyclus (2)

http://www.scrumdesk.com/pictures/ScrumDesk%20process%20poster.png




31


Scrum rollen

Scrum, presentatie Jeroen Bouvrie, Luminis.


32


Scrum rollen - Scrum master

Represents management to the project

Responsible for enacting Scrum values and practices

Main job is to remove impediments

http://chrisdonnan.com/blog/wp-content/uploads/2007/06/Humorous_ScrumMaster_image_2.jpg




33


Scrum rollen - Product Owner

Defines the features of the product, decides on release date and content

Prioritizes features, accepts or rejects work results Can change features and priority every 30 days Commits to not throw new requirements at the team

during a sprint


34


Scrum rollen - inside and outside

Scrum team: Pigs Werkt aan de Sprint backlog Geen verdere taak- en rolverdeling

Alle anderen: Chickens Wel observeren Niet interveniëren tijdens iteraties


35


Scrum team

Typically 5-10 people

Cross-functional

QA, Programmers, UI Designers, etc. Members should be full-time

May be exceptions (e.g., System Admin, etc.)

Teams are self-organizing

Membership can change only between sprints


36


Scrum Praktijken

Pre-game Planning And Staging Features, Stories, Use cases (door ‘iedereen’) High level design (software architectuur) Product Backlog

Sprint Planning (her) prioriteren in Productbacklog Sprint backlog creëren


37


Product backlog

A list of all desired work on the project Usually a combination of:

story-based work (“let user search and replace”) task-based work (“improve exception handling”)

List is prioritized by the Product Owner Typically a Product Manager, Marketing, Internal

Customer, etc. Contains a first estimation by the team


38


Product backlog items

Required ID Feature, Story of Use Case Priority Risk Assessment Estimated points Estimated hours

Optional Comment Status Business value


39



Product backlog in relation to projectmanagement

http://www.infoq.com/presentations/agile-quality-canary-coalmine

During time a team gets work done from the backlog with a preferable constant quality, value and pace or “velocity”




40


Sprint Planning

http://blog.svencipido.be/Blog/content/binary/ScrumSprintPlanningMeeting.jpg




41


Sprint Goal

Theme for the next sprint

Add database support Add camera support Enable concurrent use for 1000 users


42


From Sprint Goal to Sprint Backlog

Scrum team takes the Sprint Goal and decides what tasks are necessary to meet the Sprint Goal

Managers don’t assign tasks to individuals and don’t make decisions for the team


43


How to deliver a potentially shippable product Make slices Each slice can operate

independent of an other slice

Architecural slice Not every slice has to

be put in production immediately http://burgertjes.punt.nl/upload/sushi-for-2.jpg


http://burgertjes.punt.nl/upload/sushi-for-2.jpg

http://burgertjes.punt.nl/upload/sushi-for-2.jpg

44


Example Sprint Backlog


45


Product & Sprint backlog combined


46


Sprint Backlog during the sprint

Changes Team adds or removes tasks whenever they need to in

order to meet the Sprint Goal Sprint Backlog can only be updated by the team Estimates are updated whenever there’s new

information


47


“The definition of done”

Mijn taak is “af”… .... behalve dan de documentatie .... en de code review .... ik heb het zelf al getest


48


“The definition of done” Alle code is ingecheckt. De publieke interface van elke klasse is voorzien van Javadoc. Code voldoet aan de door het team vastgestelde coderichtlijnen (te checken met

Checkstyle of PMD) Alle unittests kunnen uitgevoerd worden met minimal 50% testcoverage. Productbacklog is up to date. Sprintbacklog is up to date. Package-, class-, sequence- en deploymentdiagramman zijn bijgewerkt. Ontwerpbeslissingen zijn vastgelegd. Alle taken (issues, bugs, tasks etc.) zijn afgesloten of uitgesteld tot de volgende sprint. Er is een installatiehandleiding voor de installatie van de software. Er is zoveel mogelijk gebruikersdocumentatie beschikbaar in de applicatie, de rest

digitaal en/of op papier. De nightly en continuous builds falen niet. De sprint is geaccepteerd door de productowner / opdrachtgever.


49


Quality? Value Driven Development





workshop: Sprint backlogThursday, March 18, 2010

51


Workshop: Casus


52


Workshop: High Level Architectuur


53


Workshop: Domein Model


54


Workshop: Sprint Backlog

Gegeven een product backlog: 10 min:

Bepaal de Sprint Goal en welke features op de sprint backlog komen

20 min: Schat de features met behulp van planning poker

15 min: Verdeel enkele features tot taken en verdeel de taken

Beantwoord minimaal de volgende vragen: Voor hoeveel punten werk heb je ingepland? Voor hoeveel uren werk heb je ingepland?


55


Scrum Praktijken - vervolg

Het team is ‘zelfsturend’ Houdt dagelijkse Scrum Meetings: standup Scrum master werkt als ‘Firewall’

Blocks: beslissing binnen een uur Blocks: weggewerkt in één dag

Het team werkt dagelijks in één ruimte Iedere dag: integratie en testen Sprint Review zònder PowerPoints: gaat om demo.


56


Scrum Meeting - stand-up


57


Scrum Meeting - vervolg


58


Burndown


film standup-meetingThursday, March 18, 2010

60


Sprint Review Meeting

Team presents what it accomplished during the sprint Typically takes the form of a demo of new features

or underlying architecture Informal

Participants Customers Management Product Owner Other engineers


61


Inspect and Adapt: Retrospective

Wat ging goed? Wat ging niet goed en hoe kwam dat? Welke acties moeten we ondernemen om eerdere

fouten te voorkomen?


62


Scrum of Scrums

http://www.mountaingoatsoftware.com/images/scrumofscrums.gif


http://t2.gstatic.com/images?q=tbn:A8zS9YTB8tamLM:http://www.mountaingoatsoftware.com/images/scrumofscrums.gif

http://t2.gstatic.com/images?q=tbn:A8zS9YTB8tamLM:http://www.mountaingoatsoftware.com/images/scrumofscrums.gif

Scrum in DDOAErvaringen vanuit ICA


64


Eigen projectplanning


65


Sprint lengte

Kies een vaste lengte Velocity DDOA: 2 weken

Junior developers Overhead schoolwerk Past goed in 8 weken Nadeel: velocity pas

goed na gem. 3 sprintshttp://www.jimcarroll.com/weblog/archives/pictures/velocity.jpg


http://www.jimcarroll.com/weblog/archives/pictures/velocity.jpg

http://www.jimcarroll.com/weblog/archives/pictures/velocity.jpg

66


Projectondersteuning

Workshops op aanvraag ICA Extern

Coaching Kwaliteit: Quality Assurance Manager

Product: Technical Coach

Proces: Process Coach

Vaardigheden: Social Skills Coach

Functioneringsgesprekken en IPV 2x op basis van gekozen competenties


67


Tools: Confluence


68


Tools: JIRA


69


Tools: Bamboo


70


Other “Agile” Tools and Practices

Test Driven Development: JUnit EasyMock Cobertura

Versioncontrol Subversion

Planningboard & Burndown Jira, GreenHopper

Pair Programming Planning Poker Refactoring


71


Competentiematrix

Rol/Competentie Samenwerken Communiceren Planmatig werken

Scrum Master

Product Owner

Team Member


71


Competentiematrix


Scrum Master

Product Owner

Team Member

X


71


Competentiematrix


Scrum Master

Product Owner

Team Member

X

X


71


Competentiematrix


Scrum Master

Product Owner

Team Member

X

XX


71


Competentiematrix


Scrum Master

Product Owner

Team Member

X

XX

X


71


Competentiematrix


Scrum Master

Product Owner

Team Member

X

XX

XX


71


Competentiematrix


Scrum Master

Product Owner

Team Member

X

XX

XX X


72


Scrum Master & Planmatig werken


73


Product Owner & Communiceren


74


Team Member & Samenwerken


ConclusieThursday, March 18, 2010

76


What to expect?

Initial progress will likely be slower than anticipated The process will quickly reveal constraints Team will take time to learn how to self-organize You will want to tell the team how to solve problems You will need encourage visibility and transparency Team may have difficulties focusing on daily plan


77


Wrap up: Scrum values

Agile, team commitment Timeboxing Transparency Play your role Communicate Define what “done” means Scrum won’t solve problems; it makes them visible so

there are no execuses to do nothing. Nowhere to hide and visible results!


78


Softwareontwikkel-proces:✓RollenProducten✓Verantwoordelijk-hedenFasering: Analyse, Ontwerp, Bouw, Test, Oplevering

Processen: Scrum

Projectmanagement-proces: Geld✓ Organisatie✓ Kwaliteit Informatie✓ Tijd


79


Resources

DDOA http://wiki.icaprojecten.nl

Agile Manifesto http://agilemanifesto.org/

Implementing Scrumhttp://www.implementingscrum.com/

Larman, Craig, (2004), Agile & Iterative Development. A Manager’s Guide, Boston: Pearson Education.

Luminis, Jeroen Bouvrie, Scrum Master


http://wiki.icaprojecten.nl






http://agilemanifesto.org/




http://www.implementingscrum.com

http://www.implementingscrum.com

Bedankt voor uw aandacht!


scrum implemented in an educational context

Technology

rody middelkoop thursday

heden informatie fasering

team member scrum

team member

product owner

sprint goal

tijd ontwerp

based work