Your SlideShare is downloading. ×
0
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Beyond Scrum: Introducing Simple Scalable Agile Development
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Beyond Scrum: Introducing Simple Scalable Agile Development

972

Published on

Scrum is the most popular Agile process, and aspects like the daily meeting are familiar to most developers and businesspeople. But it's not for everyone. …

Scrum is the most popular Agile process, and aspects like the daily meeting are familiar to most developers and businesspeople. But it's not for everyone.

Scrum was designed for small collocated teams working on simple projects. Larger Scrum projects can experience hierarchical planning, integration nightmares, and inefficient use of resources.

In these slides, Assembla and Perfroce demonstrate an Agile framework that avoids these problems by recognizing the concept that managing code is often easier than managing people

These slides are from a webinar on 2/25/2012. Watch the webinar recording here: http://youtu.be/egWYdFplNQY

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

No Downloads
Views
Total Views
972
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
28
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  •  Scrum is a small team process. When scrum grows, you end up with an unwieldy ‘scrum of scrums’ approach. That’s a hierarchy requiring some top down planning – it’s not Agile. These teams need a point of integration (a place for work to sync up at the end of the sprints). That means that a delay in any one team can impact the others.It does not easily handle remote contributors, and these days we want to use talent wherever its located. 20% of workers are now telecommuting.Scrum also does not easily handle coordination between components/modules, or different parts of a big product, or complex customizations that introduce dependencies. These complexities introduce more integration pain. You have to be able to handle the larger release management picture.Things get worse when you’re trying to release more frequently.
  • These correlate to points on slide 6.
  • The folks in Bangalore have to be first class members of the project.Choose this slide or slide 14.
  • Add screenshot and notes.
  • Merges must be fast, easy, and automated. This prevents any integration problems.Note that this view is really for architects and release managers: the ‘big picture’ of everything that happens in the product lifecycle.(Addressing the integration and frequency problem.)
  • Perforce brings a lot of version management power to bear to keep things running smoothly. I’ll briefly talk about a few of these areas: providing the right data for developers, easy merging at the task branch and release management level, and supporting massive automation. “Amateurs talk about tactics, but professionals study logistics.” – Team management is nice, but you have to give people the tools to get the job done.On a complex project, the release managers understand all of the dependencies between components, versions, and external libraries. This information should be modeled in the enterprise repo and used to quickly give developers the right set of files to work on.(Addressing the complex product problem.)
  • Andy notes: Should we emphasize these points that are advantages over git? 1) Automated merge. 2) merge to multiple test environments. 3) Merge to multiple output versions.Complex feature matrix: due to multiple platforms, customizations, several supported versions. Perforce can automate merging one change to 50+ locations.By relying on these powerful collaboration tools, you can avoid the business repercussions that arise when important work doesn’t make it to your customers. If a bug fix hasn’t shipped, that work isn’t helping your business.Can I trace bug fix flow through 50 customizations?Can I trace automated deployment of bug fix to all production servers?How big is my feature matrix? (Intuit builds 80 versions of some products.)Example: electronics manufacturer lost $800 million due to shipping bad product – because they didn’t merge a bug fix to the right place.Automated merging prevents buildup of technical debt. There is some risk involved, but the risk is present in the less stable stream.(Addressing the complex product problem.)
  • This information is based on real customer success stories. Massive automation is a key to success, but you need the firepower to back it up. Perforce provides that firepower.(Addressing the on-demand CI problem.)125+ scrum teamsSoftware handles 10b+ transactions per monthOver 100k customersMonthly iterations, quarterly releases80% code coverage via 90k automated testsAutomated everythingAlso note that one gaming customer used Perforce to store everything they needed for debugging, which gets them much closer to on-demand delivery. (Even debugging used to be so painful that it didn’t happen until very late in the dev cycle.)
  • Slide on the right is from Salesforce. Not sure if we can mention them by name though.
  • 2 KEY ELEMENTSContinuous Deliver “Dial”IT CalendarCONTINUOUS DELIVERY DIALLike Dial on ThermostatEnterprises – Multiple Environments on Path to ProductionDial In How Far Continuous Delivery Is UsedFor Development & Integration StagesDevelopers Self-Service DeploymentCheck-In Triggers Continuous IntegrationSuccessful Build Triggers Automated TestPromotes to Integration TestTo Eliminate Ops Infra Dependency & LagOption to Deploy to Cloud, like AmazonEliminate Infrastructure & Manual Deployment BottlenecksLater Stages Can Use Formal Release TrainsFormal ReviewOps TestingControlled Promotion ApprovalIT CALENDARUnique to SerenaVisibility to All StakeholdersDevOpsBizCoordinate Apps & Infrastructure ChangesSTATSEtsy Deploys 20-50 Times per DayFacebook Gatekeeper
  • Seed questions:Can I use this process if I have a traditional delivery schedule? I ship my product twice a year.What does ScrumBan mean for the idea of committing to a given amount of work in a sprint?
  • Transcript

    • 1. Beyond Scrum Introducing Simple Scalable Agile DevelopmentCopyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 2. Presenters Randy DeFauw • Technical Marketing Manager at Perforce • Certified Scrum Master (and member of an Agile marketing team) Andy Singleton • CEO and Founder, Assembla • Released over 20 online software and service products Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 3. Perforce Software• Fast, scalable version control• Available on over 50 platforms• Version management for any team, any data, and any location• Used by over 5,000 customers in software, gaming, multimedia, firmware, finance, and other industries Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 4. Assembla• Cloud-based tools for distributed Agile development teams – Agile planning – Ticketing/task management – Code management (SVN/Git/Perforce)• Over 500,000 users in 100 countries• Development team in 15 countries• Now offering PERFORCE ON-DEMAND Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 5. The Problem with Scrum Small teams ? Scrum of Collocated Team scrums One Scrum teams Narrowly scoped Today‟s Challenges projects • Big multi-platform projects Team • Distributed teams TwoFixed release times • Release frequently Team • On-demand apps and services Three Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 6. Change in ApproachSimpler?• We will remove some “rituals,” making it easier to join projects, manage multiple teams, manage distributed teams, and get releases out• Less emphasis on face-to-face team dynamics. Nice, but a luxury.Tradeoff• We will rely more heavily on technology• Code management with code review and contribution becomes a core part of agileNew speed and scale is achievable• Facebook releases 2 times per day. Android contributions from 1000‟s. Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 7. Scalable Agile ProcessPrioritize at Beginning Plan at endNo iteration plan (Release when ready)No resource constraints Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 8. Advantages• Continuous delivery – Faster. Release when ready. Take the right duration, long or short• Distributed and Dispersed teams – No big meetings or requirement for mass consensus• Scales to more contributors. – No centralized iteration planning or testing. – Include new contributors and many types of contributors – Scrum compatible – Scrum teams can work as contributors with zero process change. Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 9. Building Blocks to Go Beyond Scrum• Distributed Teams – Support contributors who are distributed in space, and in management structure (scrum teams, hackers, outsourcers, partners)• Continuous delivery – Code management and merge capabilities to review, test and merge code from many contributors, quickly and reliably• On-Demand Infrastructure – Unlimited, on-demand test environments and continuous integration to build and test any change Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 10. Tasks and Tools for Distributed Teams Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 11. Collaboration for Continuous Delivery Stay up to date Continuous Flow on all changes: of Tasks Activity stream
    • 12. Global Perforce Architecture Why did the case study for distributed Agile choose Perforce? The entire set of teams must function as a single team with one global build repository, one tracking and reporting tool, and daily meetings across geographies. - Jeff Sutherland, The Scrum Papers Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 13. Steps to Continuous Delivery Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 14. Idealized Scrum Sprint Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 15. Idealized Kanban Process Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 16. Idealized ScrumBan Release Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 17. Testing Iterative Releases Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 18. The Secret of Continuous Delivery
    • 19. Assembla Merge Request Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 20. Perforce Merge Intuitive workflow Merge notifications Fast context switching Visual tools Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 21. Complex Component Models The right data Dynamic adjustments On demand Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 22. Build and Test On-Demand Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 23. Build and Test Each Change Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 24. Complex Feature MatrixAutomatic merge to 50+ locationsEnsure visibility and transparency Has the bug fix reached the customer version yet? Have you patched all the consumers of the module? Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 25. Heavy Artillery• Over 100,000 customers rely on Salesforce for 10 billion transactions per Proxy Build Replica Smart Replica month • Avoids data • Avoids data • Avoids data• Salesforce relies on transfer cost transfer and read- transfer and read- „Extreme‟ Agile • 75% savings in only operations only operations, data transfer time • 95% savings in allows writes to development: data transfer shared service 125+ scrum teams and • 88% savings in • Purely local read- 90,000+ automated tests release note only activity plus reporting seamless write• „Extreme Agile‟ relies on operations Perforce Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 26. Result: Faster Velocity Salesforce.com Assembla Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 27. Next Steps• Scrumban • On-demand build and test systems• Continuous Integration • Continuous delivery dial Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 28. Continuous Delivery Dial Business Dev Ops Self-Service Controlled DEV TEST INTEG STAGING UAT PROD CONTINUOUS DELIVERY RELEASE TRAIN Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 29. Thank you!Please enter your questions using the chat utility. Copyright 2012 Perforce Software, Inc. - Assembla, Inc.
    • 30. Resources http://www.perforce.com/perforce/agile info@perforce.com https://www.assembla.com info@assembla.com @rdefauw

    ×