SCRUM for Startups
Innosquared – Providing expertise on demand.
Who I am…
 Stephan Haupt
 Born in 82‘ in Leverkusen, Germany
 Studied „Technical Informatics“ (Information
Engineering)
 Lead Software Developer @ Innosquared
Innosquared GmbH © 2013
2
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
Innosquared GmbH © 2013
3
What we do…
Identify – Recruit – Manage
Innosquared GmbH © 2013
4
Experts can be sourced according to our clients needs
Consultations
Discussion between client
and expert(s) via phone or
face-to-face
Workshops/ Seminars
Expert participates in client’s
meetings or gives presentation
Innosquared GmbH © 2013
Project Staffing
Series of consultations to
complement client’s
know-how
Surveys
Custom web-based
survey of selected experts
5
WHAT THE HELL IS SCRUM ?
Innosquared GmbH © 2013
6
SCRUM Process
Innosquared GmbH © 2013
7
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
Innosquared GmbH © 2013
8
Problems before SCRUM




Very long release times
Difficulties to react to changed requirements
Not enough time for quality management
Problems in requirement engineering
Innosquared GmbH © 2013
9
Improvements we made with SCRUM




Short release times
Clear responsibilities
Clear requirements
Flexible dealing with changed requirements
Innosquared GmbH © 2013
10
Problems implementing SCRUM
 No SCRUM Master
 Code Quality Issues
 Estimation without Story points
Innosquared GmbH © 2013
11
Key Learnings




Keep it simple
Implement a base version
Define a target for every sprint
The devil is in the implicit
Innosquared GmbH © 2013
12
What you‘ll not learn from books…
 Sprint Planning I




Ask for requirements / specific information
Discover User Acceptance Tests
Talk about constraints
Discuss Acceptance criteria
Innosquared GmbH © 2013
13
What you‘ll not learn from books…
 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
Innosquared GmbH © 2013
14
What you‘ll not learn from books…
 Estimation
 Once a sprint / week
 Do not use times for estimation, better use Story points (1,
3, 5, 8, 13)
 Play „Magic Estimation“
Innosquared GmbH © 2013
15
Links
 http://borisgloger.com/
 Search on Youtube for boris gloger and the sprint
meetings
Innosquared GmbH © 2013
16