2. Rapid Agile Delivery:
STORIES FROM STASH ON SHIPPING PRODUCT
FREQUENTLY
MATTHEW WATSON
•
STASH TEAM LEAD
•
ATLASSIAN
•
@mattw_watson

3. “
If you want a good example how
to do "release early, release
often" properly, take a look at
@atlassian Stash.
”
COSMIN STEJEREAN, @offbytwo, 21 August 2013

4. Timeline of releases
25 weeks
26
20 weeks
15 weeks
10 weeks
7
7
9
8
9
4
5 weeks
0 weeks
1.0
1.1
1.2
1.3
2.0
2.1
2.2
6
3
2.3
2.4
5
5
5
2.5
2.6
2.7
6
2.8

5. Why release often?
Good for the product
• Features to customers faster
• Smaller deliverables = less risk
• Earlier feedback

6. Release productivity cycle
Start work on out whatRelease!docs :-(
We’re Bug fixing,
rocking it
Figured release cycles! now!
we’re
Faster
doing

7. Release early, release often
Good for the development team
• Only ship when we’re ready
• Reduce stress
• No drop in quality or scope

8. Release early, release often
Good for the development team
• Smaller features = more features
• Always something to release

9. Stash feature
development

10. Early problems
Lack of feature ownership
• Front end/back end split in teams
• Long timeframe
• Developers working to ‘spec’
• Team leads under pressure

11. Developer ownership
Feature kickoffs
• Feature stakeholders
• Product Manager
• Designer
• Developers
• QA
• Brainstorming

12. Developer owns the spec
Feature Leads
• JIT Feature specification
• Developer driven process
• Developers responsible
for end result - the
drivers of quality

13. Benefits
• engaged developers
• complete, high quality features
• developer experience
• less work for PM, Design, Team leads

14. Innovation weeks
Features Product Management never think
of
• 2.6

15. “
Quietly impressed with features
that @atlassian have been
rolling out on Stash. Per-branch
permissions, pub. accessible
repos in particular.
”
DAVID BOLTON, @lightningdb, 13 June 2013

16. Stash development
cycle

17. Agile development with git
Feature branching
• Allows development in isolation
• functional testing
• performance testing
• Isolate stable code from work-inprogress
• Only merge when ready

18. Code review
In Stash: pull requests
• Guarantee quality of
shipped code
• Improve developer
skills and disseminate
information
• Gatekeeping
• Becomes part of the
culture of the team

21. Continuous integration
• All builds reported to
Stash
!
!
!
master
build
!
• Appear in Pull Requests
• Continuous deployment
•Database matrix
from day 5
•git version
matrix
•git on windows
Deploy to
stash.dev

22. Monitoring CI

23. Performance monitoring
Performance monitoring
Keeping Stash fast
• Daily monitoring
vcvcx
Level Two
Level Two
Level Two
Level One
• Check results in
standup
• Monitor significant
feature branches

24. Release branching
Supporting multiple
releases
master
2.6
2.5
• Develop on feature branches
• Merge to master
• JIT branch for release
• Merge all bug fixing
downstream
!
!

25. Automate all the things

26. Techniques for rapid delivery
• Release often!
• Engage developers and designers
• Parallelize feature development
• Quality code won’t slow you down
• Trust your CI
• Automate everything

27. “
Stash by Atlassian, one of the
best things that could happen to
your company.
”
ONDREJ KVASNOVSKY, @okvasnovsky, 5 June 2013

28. Thank you!
MATTHEW WATSON
•
STASH TEAM LEAD
•
ATLASSIAN
•
@mattw_watson

29. Rate this Talk
Rapid Agile Delivery: Stories from Stash on
Shipping Product More Frequently
Text code below to 22333
or visit http://bit.ly/19JYG7e
MEH = 21
NO T BA D = 22
P R ET T Y GO O D = 23
A WES O ME = 24
To join this session, send text 136888 to