1. Karlstads University Computer Science Software Engineering, DVGC051 Times and activities Sprint-plan (same for all groups, SM and PO (Product Owner) can attend when relevant) Lecture (common for all groups): wed1 8.15-10.00 Planning (common for all groups): wed1 10.15-12.00. Sprint running Demo (all groups, in their ”corner”): fr2 13.00-14.30 Dissassembly of demo (and coffee break): fr2 14.30-15.00 Retrospect (each group by itself), PO rotates between groups: fr2 15.00- 16.00 Recovery: fr2 16.00 – next wed1 8.15 First sprint: to1 and to2 lecture

2. Karlstads University Computer Science Software Engineering, DVGC052 Sprint A sprint in Scrum is one iteration From backlog to demo:able product

3. Karlstads University Computer Science Software Engineering, DVGC053 Pre-project Requirements Analysis Design Implementation Test Sprints#1 #2 #3 #4 A Scrum Sprint Disciplines Sprints Initial requirements MoSCoW / Pareto, solve top 20% requirements first [Pareto], [MoSCoW]

4. Karlstads University Computer Science Software Engineering, DVGC054 Iterative Development – One Iteration Each iteration is a mini project involving all disciplines –Normally not in sequence Requirements Analysis Implementation verify requirements in implement requirements in capture in Requirements Model Analysis Model Design Model Architecture and Design Code realise requirements in * [until finished] Architecture Model Test specify requirements in : Class : Actor Test Model

5. Karlstads University Computer Science Software Engineering, DVGC055 The Sprint Flow Sprint planning meeting, eight hours Time box –Team and Product Owner update and prioritize Product Backlog4h –The team plans for and starts the sprint4h Place tasks in the Sprint Backlog, the sprint has started Team runs sprint28d –Team holds Daily Scrum15’ Synchronizes team members What is done, what is planned, what impediments stop me –Team updates Sprint Backlog Team holds Sprint review meeting4h –Demonstrate sprint results to anyone interested Scrum Master holds Sprint retrospective meeting with Team3h –Team revises and improves development process

6. Karlstads University Computer Science Software Engineering, DVGC056 The Scrum Process Overview Vision: Anticipated ROI, Releases, Milestones. Initial requirements Planning meeting [Scrum 07]

7. Karlstads University Computer Science Software Engineering, DVGC057 What does Done mean? Deliverable to the customer –Ready to be used in a product –QA, documentation, refactored, meets good engineering practice standards What if I am unable to finish all this during this sprint? Some options –Increase effort, work harder, longer, smarter –Cut quality, skip design, testing, intergation, documentation –Cut features What are the consequences of each? –Which one is least / most desireable

8. Karlstads University Computer Science Software Engineering, DVGC058 Consequences of Rushing or Cutting Quality Rushing: Working overtime, cutting breaks, adding people –Leads to burn out –Error rate increases More crap produced in shorter time Cutting quality –Harder to reuse and develop further Increased technical dept due to lack of refactoringtechnical dept –Reduces velocity –Makes it harder to meet new goals –Increases need to rush or cut quality in subsequent sprints Only sustainable option –Cut features, postpone to lates sprints and/or releases –Informed decisions with the PO involved [Kniberg 08]

9. Karlstads University Computer Science Software Engineering, DVGC059 Sprint Planning Meeting Product Owner selects top priority features from Product Backlog –Candidates for next sprint –Feature = something useful for product owner –Closer to top  more detailed stories, more scenarios Team estimates features from top until sprint velocity reached –Story Points, Sprint velocity = number of story points done in earlier sprints Only complete features count Feature estimates kept constant throughout product development –Planning PokerPlanning Poker Only rough, relative estimates (story points) for whole features Product Owner writes acceptance tests –For selected features –Supported by team members [Backlog item practice], [Planning Poker]Planning Poker

10. Karlstads University Computer Science Software Engineering, DVGC0510 Sprint Starts Team builds initial Sprint Backlog –Breaks down features to tasks Add database tables or fields Write data access routines Increase domain model functionality Add user interface Etc etc –Makes initial task estimates by hours Do not map directly to Product Backlog scale –Build sprint backlog Workshop tools –Off you go The sprint has already started, time is ticking

11. Karlstads University Computer Science Software Engineering, DVGC0511 Work During Sprint, for One Task at a Time Select an acceptance test corresponding to the user story –Prepared by PO –Set test property on local workstation only Analysis and design –For the short term items No AP (Analysis Paralysis) No DBUF (Big Design Up Front) –Normally standing in groups in front of a whiteboard Incrementally and iteratively develop features in tiny steps –Document example in NUnit, implement, refactor –Apply all design skills and software engineering practices during refactoring –Until Done with that task and eventually that user story

12. Karlstads University Computer Science Software Engineering, DVGC0512 Daily Stand Up Meeting Purpose –Team member inform each other of their progress and need for assistance –Three items: Achieved yesterday, goal for today, impediments Common pitfalls – discuss what kind of problems they cause –Team members report to the project manager –Team members embellish their progress –Team members report ”done” before Done –Team members do not offer to help each other Time boxed to 15 minutes –Expanded discussions are postponed to additional meetings Same time, every (working) day –Groups select times themselves –Times are to be respected

13. Karlstads University Computer Science Software Engineering, DVGC0513 Scrum Demonstration With Product Owner and any interested party –You have to deliver a piece of business functionality every sprint Last day of every sprint –End of sprint time box –Time and date fixed in advance at regular pace –Unconditional Demonstrates that what was promised actually works –No excuse –Problems should have been raised and solved earlier –Include ”How to demonstrate” in Product Backlog Next up –Team and Scrum Master: Retrospective meeting –Product Owner: Plan priorities for next sprint

14. Karlstads University Computer Science Software Engineering, DVGC0514 Scrum Retrospective Meeting Team and Scrum Master The single most important activity for continuous improvement –Återblicken, blog Tobias Fors, Citerus (in Swedish)Återblicken, blog Tobias Fors, Citerus (in Swedish) Assess what has worked and what has not during last sprint –Make list of what needs to improve –Suggest changes Select at most one item to change during the coming sprint –Discuss how to implement the change Next up –Team, Scrum Master, Product Owner: Planning meeting for the next sprint

15. Karlstads University Computer Science Software Engineering, DVGC0515 Practices Pair programming Stand up meetings TDD Incremental design Continuous integration Collective code ownership Informative workspace Coding standard Sustainable pace

16. Karlstads University Computer Science Software Engineering, DVGC0516 Tools Visual Studio –Coding and connecting NUnit –TDD SubVersion –Version control FitNesse –Integration testing Cruise Control –Automation MSBuild –Putting it all together

17. Karlstads University Computer Science Software Engineering, DVGC0517 Group business There will be three groups –5-6 people We want your groups to work as well as possible together –Good composition –Good teamwork –Good guidance Different skills –user thinking/requirements –analys/design –coding –testing Which of the above four is your strongest, according to yourself? –All skills will be needed –Has no bearing to course grade Also think about if you want to speak English in your group or not

18. Karlstads University Computer Science Software Engineering, DVGC0518 More group business Group yourself in the four corners of the room according to your strong point English or not Group forming Agree on standup meeting time –from 10AM and forward –preferrably in conjunction with fika, before or after Groups should be self organizing Everyone should do their part One lecture every other week, or more –8-10 wed1

19. Karlstads University Computer Science Software Engineering, DVGC0519 Checking in/out When your solution is ready –grab mascot place it next to yourself –commit your files (to server) –update all files (from server) –compile –run test suite –if all green run build script on integration server return mascot you’re done –else you have a problem