continuous agile - assembla's approach

9
Release More Frequently Assembla Approach www.assembla.com Agileguide.assembla.com From Andy Singleton, http://andysingleton.com

Upload: assembla

Post on 15-Jan-2015

177 views

Category:

Technology


1 download

DESCRIPTION

Short introduction to Continuous Delivery and Continuous Agile. Why do it? Some linked resources to get started, from Assembla. The structure is simple: 1) Release more frequently 2) Improve

TRANSCRIPT

Page 1: Continuous Agile - Assembla's approach

Release More FrequentlyAssembla Approachwww.assembla.com

Agileguide.assembla.comFrom Andy Singleton,

http://andysingleton.com

Page 2: Continuous Agile - Assembla's approach

Assembla in 2011“Scrumban” with iterative releases, but continuous

planning to accommodate a distributed team.Releases took longer as system got bigger and there

was more to test. 2 weeks -> 3 weeksBugs in production. 2 days for fixes. StressfulCompetitors achieved faster velocity with continuous

delivery

Made a study of continuous methods with our own team, customers, and tools.

Now – releasing about 250 times per month. Fewer bugs. Much less stress.

Page 3: Continuous Agile - Assembla's approach

Assembla results

Page 4: Continuous Agile - Assembla's approach

When to use Continuous Delivery?You provide an online service. Competitive

pressure will force you to continuous: Office 365 vs Google Docs

Your release times are getting longer, with added QA

You are developing a new product with lean startup and MVP techniques

You have a big project with a lot of contributorsYou need to release frequent security patches

Improves speed, quality, capacity and scale, cost, focus, clarity.

Page 5: Continuous Agile - Assembla's approach

What is Continuous Agile?Continuous Integration test strategiesContinuous Delivery code managementKanban task managementContinuous “Story Owner” product management

Lean, not ScrumWorks for distributed teams, different sizes, faster

releasesNot team building and coaching. That is indirect. Focus

directly on output. Teams will become high performing when they feel success.

Scrum compatible. Scrum teams are good contributors.

Page 6: Continuous Agile - Assembla's approach

Our Master Plan1. Release more frequently2. Improve

How can Assembla help?

Page 7: Continuous Agile - Assembla's approach

KnowledgeUnblock! A Guide to the New Continuous

AgileeBook at: http://Agileguide.assembla.comContinuous agile task management. Code

contribution. Centralized and distributed continuous delivery. Test layers. Product management. Big projects. Etc.

Enterprise Agility from Damon PooleIncremental Product Design from PovMethod

Page 8: Continuous Agile - Assembla's approach

How can Assembla help?Workshop to answer questions from

developers or product managers90 minutesShort presentation of goals and tacticsAnswer questions and explore

recommendationsConsulting (as needed and as available)Delivery with blended teams

Pick a projectManage it to release more frequently

Page 9: Continuous Agile - Assembla's approach

Recent Delivery ResultsSaaS Release in 6 weeks. Full builds from week 2. Accelerating.