SCRUM for Startups Innosquared – Providing expertise on demand.

2Innosquared GmbH © 2013 Who I am…  Stephan Haupt  Born in 82‘ in Leverkusen, Germany  Studied „Technical Informatics“ (Information Engineering)  Lead Software Innosquared

3Innosquared GmbH © 2013 Who is INNOSQUARED…  Founded in 2010 in Duesseldorf, Germany  Provides global access to industry experts enabling thousands of interactions each year  Network of experts from more than 50 countries  Flat hierarchies  Young, good-humored team  Always looking for talented people to join our team

4Innosquared GmbH © 2013 Identify – Recruit – Manage What we do…

5Innosquared GmbH © 2013 Consultations Discussion between client and expert(s) via phone or face-to-face Project Staffing Series of consultations to complement client’s know-how Workshops/ Seminars Expert participates in client’s meetings or gives presentation Surveys Custom web-based survey of selected experts Experts can be sourced according to our clients needs

6Innosquared GmbH © 2013 WHAT THE HELL IS SCRUM ?

7Innosquared GmbH © 2013 SCRUM Process

8Innosquared GmbH © 2013 Ball Point Game  You are one big team  Ball must have air-time  No ball to your direct neighbors  Start Point = End Point  Iteration = 2 min  We will play 3-4 iterations

9Innosquared GmbH © 2013  Very long release times  Difficulties to react to changed requirements  Not enough time for quality management  Problems in requirement engineering Problems before SCRUM

10Innosquared GmbH © 2013  Short release times  Clear responsibilities  Clear requirements  Flexible dealing with changed requirements Improvements we made with SCRUM

11Innosquared GmbH © 2013  No SCRUM Master  Code Quality Issues  Estimation without Story points Problems implementing SCRUM

12Innosquared GmbH © 2013  Keep it simple  Implement a base version  Define a target for every sprint  The devil is in the implicit Key Learnings

13Innosquared GmbH © 2013  Sprint Planning I  Ask for requirements / specific information  Discover User Acceptance Tests  Talk about constraints  Discuss Acceptance criteria What you‘ll not learn from books…

14Innosquared GmbH © 2013  Sprint Planning II  Create architecture diagrams  Dive into the code base  Get an idea about the technical solution  Tasks will come up as a side product What you‘ll not learn from books…

15Innosquared GmbH © 2013  Estimation  Once a sprint / week  Do not use times for estimation, better use Story points (1, 3, 5, 8, 13)  Play „Magic Estimation“ What you‘ll not learn from books…

16Innosquared GmbH © 2013   Search on Youtube for boris gloger and the sprint meetings Links