Agile product development Intro into Scrum

Table of contents What is agile? Scrum basics Roles Ceremonies Future refinements

What is agile?

Agile management “Agile management refers to an iterative, incremental method of managing the design and build activities of engineering, information technology and other business areas that aim to provide new product or service development in a highly flexible and interactive manner.” Wikipedia

Pillars of an agile organisation

Scrum basics

Scrum basics Sprint Iterative working periode. Normally between 2-4 weeks User story The smallest unit of work. As a {type of user}, I want {goal} so that I {receive benefit}. Story points Relative estimation of work Fibonacci numbers are used during planing poker Product backlog Prioritized collection of all tasks and user stories related to a product Sprint backlog Prioritized collection of tasks and user stories planed for the next sprint

Scrum roles

Scrum Roles Main roles: Product Owner (scrum-po@app-arena.com) Scrum Master (scrum-master@app-arena.com) Team (scrum-team@app-arena.com) Externals: Project stakeholders (scrum-sh@app-arena.com) Experts

Main roles in detail Product owner – Story teller Promotes the product vision Prioritizes the product backlog to maximize the product’s functionality and value Creates user stories from requirements Talks to all stakeholders Involves experts when needed Scrum master – Cerimony master Ensures that everybody respects the rules Removes impediments/obstacles Protects the team from external influences Team – Action heros Is self-organized Estimates Story Points Plans the sprint Implements user stories

Ceremonies

Ceremonies Product planning (PO + Stakeholder) Stakeholders describe product wishes, PO converts to user stories Refinement (PO + SM + Team) PO discussed user stories with the team Planning poker to estimate work Sprint planning (SM + Team) Team moves user stories from the top of the backlog to the next sprint until team capacity is exceeded Tasks for each user story will be defined. Each task should be completable within one day! Daily scrum (SM + Team) Standup-Meeting for synchronizing the team: What did I do? What‘s next? Any impediments? Sprint review (PO + SM + Team + Stakeholder) Team presents sprint results to PO and stakeholders. Feedback can lead to new user stories PO presents the next targets Retrospective (PO + SM + Team) Last activity of a Sprint. Feedback round to improve cooperation and increase velocity

Team charter Example of a team charter Refinement 1. Thursday Basics: Each team member commits to the rules of the charter It is frequently updated during the retrospective Schedule: Rules of cooperation: Sprints are 3 weeks and start Thursday The last week is only for testing and bug fixing. Nobody tests its own tasks Project team is always interdisciplinary Part time team members have fix working hours (each day from 09:00 to 13:00) Project work is within the developers-room. No phone The team writes all tasks together Each team member will read the stories before the refinement meeting Refinement 1. Thursday 09:00 – 11:00 Sprint planning 11:00 – 12:30 Daily scrum Daily 09:30 – 09:45 Sprint review 3. Wednesday 12:00 – 13:00 Retrospective 13:15 – 14:15

Definition of done When can a task be accepted as done Reviewed and tested – 4 eyes see more than 2 Another person as the assignee has to review and test the task Deployed to production like environment – Your local machine does not count Your feature has been deployed to a production like environment Your feature has been merged to the master branch Documentation – Tell everyone how it works Inform our Sales-, Service-Team, Resellers and Customers about it Stop people from interupting you on your desk and asking how it works: Create a new Wiki „How-To-Article“ here: https://wiki.app-arena.com/display/SP/Anleitungsartikel Write down how your feature works for stupid people and put Screenshots of your feature Label your article with all config Ids of App config values involved to configure your feature Send your article to your supervisor

Future refinements

Future refinements Performance Improvement Quality Assurance Improve Productivity by monitoring Release Burndown Chart Sprint Burndown Chart Impediment Backlog Create a list of impediments, the SM will take care of Quality Assurance Defintion of Done – What things have to be done to accept a user story as ‚finished‘ Definition of Ready – How a user story has to be defined, that it can go into planing Feedback, feedback, feedback Improve Scrum adaption by frequently improving the process with Team feedback from Sprint retrospectives

Any questions? Thank you! Contact Sebastian Buckpesch App-Arena GmbH CTO Moltkestraße 123 +49 221 177 340 - 12 50674 Köln s.buckpesch@app-arena.com www.app-arena.com www.app-arena.com

So let‘s get started Refinement Meeting: NOW!

Quellen https://www.atlassian.com/agile iConsultants Whitepaper „Agile Organisationen – Ein Allheilmittel für alle?“ Agile Produktentwicklung – „Ervolution Poster“ https://en.wikipedia.org/wiki/Agile_management