Rapid Agile Delivery:
STORIES FROM STASH ON SHIPPING PRODUCT
FREQUENTLY

MATTHEW WATSON

•

STASH TEAM LEAD

•

ATLASSIAN
...
“

If you want a good example how
to do "release early, release
often" properly, take a look at
@atlassian Stash.

”

COSM...
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

...
Why release often?
Good for the product

• Features to customers faster
• Smaller deliverables = less risk
• Earlier feedb...
Release productivity cycle

Start work on out whatRelease!docs :-(
We’re Bug fixing,
rocking it
Figured release cycles! now...
Release early, release often
Good for the development team

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

• Smaller features = more features
• Always something to relea...
Stash feature
development
Early problems
Lack of feature ownership

• Front end/back end split in teams
• Long timeframe
• Developers working to ‘sp...
Developer ownership
Feature kickoffs

• Feature stakeholders
• Product Manager
• Designer
• Developers
• QA
• Brainstormin...
Developer owns the spec
Feature Leads

• JIT Feature specification
• Developer driven process
• Developers responsible
for ...
Benefits
• engaged developers
• complete, high quality features
• developer experience
• less work for PM, Design, Team le...
Innovation weeks
Features Product Management never think
of

• 2.6
“

Quietly impressed with features
that @atlassian have been
rolling out on Stash. Per-branch
permissions, pub. accessible...
Stash development
cycle
Agile development with git
Feature branching

• Allows development in isolation
• functional testing
• performance testing...
Code review
In Stash: pull requests

• Guarantee quality of
shipped code
• Improve developer
skills and disseminate
inform...
Continuous integration
• All builds reported to
Stash

!
!
!
master
build

!

• Appear in Pull Requests
• Continuous deplo...
Monitoring CI
Performance monitoring

Performance monitoring
Keeping Stash fast

• Daily monitoring
vcvcx

Level Two
Level Two
Level Two...
Release branching
Supporting multiple
releases

master

2.6

2.5

• Develop on feature branches
• Merge to master
• JIT br...
Automate all the things
Techniques for rapid delivery
• Release often!
• Engage developers and designers
• Parallelize feature development
• Quali...
“

Stash by Atlassian, one of the
best things that could happen to
your company.

”

ONDREJ KVASNOVSKY, @okvasnovsky, 5 Ju...
Thank you!
MATTHEW WATSON

•

STASH TEAM LEAD

•

ATLASSIAN

•

@mattw_watson
Rate this Talk
Rapid Agile Delivery: Stories from Stash on
Shipping Product More Frequently
Text code below to 22333
or vi...
Rapid Agile Delivery: Stories from Stash on Shipping Product More Frequently
Rapid Agile Delivery: Stories from Stash on Shipping Product More Frequently
Rapid Agile Delivery: Stories from Stash on Shipping Product More Frequently
Upcoming SlideShare
Loading in...5
×

Rapid Agile Delivery: Stories from Stash on Shipping Product More Frequently

422

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
422
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Rapid Agile Delivery: Stories from Stash on Shipping Product More Frequently

  1. 1. Rapid Agile Delivery: STORIES FROM STASH ON SHIPPING PRODUCT FREQUENTLY MATTHEW WATSON • STASH TEAM LEAD • ATLASSIAN • @mattw_watson
  2. 2. “ 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
  3. 3. 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
  4. 4. Why release often? Good for the product • Features to customers faster • Smaller deliverables = less risk • Earlier feedback
  5. 5. Release productivity cycle Start work on out whatRelease!docs :-( We’re Bug fixing, rocking it Figured release cycles! now! we’re Faster doing
  6. 6. Release early, release often Good for the development team • Only ship when we’re ready • Reduce stress • No drop in quality or scope
  7. 7. Release early, release often Good for the development team • Smaller features = more features • Always something to release
  8. 8. Stash feature development
  9. 9. Early problems Lack of feature ownership • Front end/back end split in teams • Long timeframe • Developers working to ‘spec’ • Team leads under pressure
  10. 10. Developer ownership Feature kickoffs • Feature stakeholders • Product Manager • Designer • Developers • QA • Brainstorming
  11. 11. Developer owns the spec Feature Leads • JIT Feature specification • Developer driven process • Developers responsible for end result - the drivers of quality
  12. 12. Benefits • engaged developers • complete, high quality features • developer experience • less work for PM, Design, Team leads
  13. 13. Innovation weeks Features Product Management never think of • 2.6
  14. 14. “ 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
  15. 15. Stash development cycle
  16. 16. Agile development with git Feature branching • Allows development in isolation • functional testing • performance testing • Isolate stable code from work-inprogress • Only merge when ready
  17. 17. 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
  18. 18. 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
  19. 19. Monitoring CI
  20. 20. 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
  21. 21. 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 ! !
  22. 22. Automate all the things
  23. 23. 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
  24. 24. “ Stash by Atlassian, one of the best things that could happen to your company. ” ONDREJ KVASNOVSKY, @okvasnovsky, 5 June 2013
  25. 25. Thank you! MATTHEW WATSON • STASH TEAM LEAD • ATLASSIAN • @mattw_watson
  26. 26. 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
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×