2. @flinc, @m_ic
Being agile is a never-ending journey. An adventure with ups and
downs, failures and successes - this presentation shows where we
are right now..
11. @flinc, @m_ic
Make sure things work,
fixing bugs, maintenance,
refactoring..
Everybody is part of a client
team, where the ground work
is done.
iOS Android Core
12. @flinc, @m_ic
If new things come up, we
build a new feature team.
Feature Team
iOS Android Core
13. @flinc, @m_ic
A feature team is an
interdisciplinary team that can
act on its own.
iOS Android Core
Decide & Deploy
Feature Team
15. @flinc, @m_ic
Team: Collaborate with everyone
to find the best solution.
Leader: Communicate
which problems need to
be solved and why.
TODO WIP DONE
Prioritised list
17. @flinc, @m_ic
It starts with understanding. What
is the real problem? What are the
real user needs? What is really
important?
This can be done through
research, data analysis, customer
interviews, customer experience
maps…
* Most of this work is done before we build the feature
team
18. @flinc, @m_ic
The prototyping phase has several
steps we run through.
* Depending on the complexity of the feature.
Feature Kickoff
PrototypingDeveloper
Kickoff
Acceptance criteria for MVP
Success metrics
Head scratchers
Tested prototype
19. @flinc, @m_ic
Collaboration is key and
stakeholder involvement is
important.
That’s why we do a feature kickoff
where we try to figure out side
effects (e.g. legal & contract
issues) and get everyone on the
same page.
Feature Kickoff
PrototypingDeveloper
Kickoff
Acceptance criteria for MVP
Success metrics
Head scratchers
Tested prototype
20. @flinc, @m_ic
Prototyping is the only way to ensure
we build the right solution.
This step is iterative - we do it until we
have a potential solution.
A prototype is worth a 1000
meetings.
Feature Kickoff
PrototypingDeveloper
Kickoff
Acceptance criteria for MVP
Success metrics
Head scratchers
Tested prototype
21. @flinc, @m_ic
There are lots of great tools for prototyping like sketches, wireframes and
technological prototypes. No matter what you choose - the important thing is
user involvement. So get out of the building and start testing!
22. @flinc, @m_ic
While things could look easy from the
outside, it may have complicated
technological dependencies on the
inside.
To avoid bad surprises we try to find
“head scratchers" before we start the
main development.
Feature Kickoff
PrototypingDeveloper
Kickoff
Acceptance criteria for MVP
Success metrics
Head scratchers
Tested prototype
23. @flinc, @m_ic
If we have a common understanding
of the problem and a (potential)
solution, we start developing it.
If not, we start over again.
* This takes days, not months.
Feature Kickoff
PrototypingDeveloper
Kickoff
Acceptance criteria for MVP
Success metrics
Head scratchers
Tested prototype
24. @flinc, @m_ic
Prototyping is awesome to show quick results.
But: Prototypes are made to throw away.
Their code may never become part of the
production code base.
25. @flinc, @m_ic
To get code to production two things need to be
done:
1. Proper test coverage
2. Review by a peer.
26. @flinc, @m_ic
Tests are as important as the implementation itself!
It is up to the developer to decide how to achieve the
best possible test automation.
TDD is great, but so are other principles.
31. @flinc, @m_ic
For deployments we use our own deployment
tool: Applikatoni.
With Toni everyone can deploy code with one
click (i.e. designers on staging).
Toni also shows the current CI status of every
branch or pull request you want to deploy.
* It’s Open Source, get it here: http://applikatoni.com/
32. @flinc, @m_ic
Everybody in the
company can have
access to our code base
and is able to open a pull
request. Even people
from marketing and sales
do this (i.e. for frontend
changes).
37. @flinc, @m_ic
This is a follow up presentation to “How
flinc works - Best practices after 5
years of company building” where I
describe how we organise our company
in general.
Check it out online at http://www.slideshare.net/
michaelhuebl/how-flinc-works-best-practices-after-5-years-
of-company-building
38. @flinc, @m_ic
Thanks to Spotify and Thinslices <3
Scribbles taken from “Spotify engineering culture”:
https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/
Role icons taken from “Ready. Steady. Go Scrum Methodology!”
http://www.thinslices.com/ready-steady-scrum-methodology/