Experience Report Program - 2014 Experience Reports
by Daniel Vacanti and Bennet Vallet. This report study details how a shift from traditional agile metrics (Story Points, Velocity) to actionable flow metrics (Work In Progress, Cycle Time, Throughput) reduced Cycle Times, increased quality, and increased overall predictability at Siemens Health Services. Actionable Metrics At Siemens Health Services.pdf
by Brandon Raines and Judy Neher. This report describes the road taken to transform a major government organization using Agile, Lean and Scrum principles, practices and techniques. No Way Agility in the Federal Government.pdf
by Stephanie Savoia describes how Marchex, Inc., evolved from a traditional waterfall process with a separate QA group, to an agile one where QA and Devs work together on the same team. Tearing Down the Walls: Embedding QA in a TDD/Pairing and Agile Environment.pdf Agile2014 Conference Experience Reports
Agile and Six Sigma, how do they mix together? by Mohamed Amr and Ayman Khalifa. This experience report is about how agile software development and Six Sigma can benefit from each other and the gaps that are filled by mixing them.
A rescue of a COTS public sector project using agile, Scrum, lean, and SAFe principles, practices and frameworks by Ben Blanquera. The report chronicles the turnaround of a failing enterprise scale (200+ FTEs) Oracle - COTS (Commercial Off The Shelf) implementation in a public agency.
When the Business Wants Waterfall: Implementing Agile in a Phase-Based Environment by Marjorie Farmer. This paper covers how Halliburton implemented an agile-based process while still allowing agile software projects to comply with the corporate standard waterfall process framework.
Head On Collision: Agile QA Driving In A Waterfall World by Eric Hile. This report relates how one team did Agile Quality Assurance and challenged old guard attitudes of Waterfall teams as well Agile stereotypes in their organization.
Growing pains - Scaling Agile to achieve greater capability in service delivery by Mia Horrigan. This reports tells how one organization improved delivery times, structured itself for success, and developed a resourcing model for team delivery that scaled from projects to programs by applying Scrum and Lean principles.
Using ATDD To Build Customers That Care by Samuel Hotop, Lav Pathak, and Jeffrey Davidson. This experience report tells how Acceptance Test Driven Development (ATDD) was used to engage product owners, build a ubiquitous language, and promote faster feedback developing Natural Gas Pipeline management software.
Technology-Driven Development: Using Automation and Development Techniques to Grow an Agile Culture by Hiroyuki Ito. This experience report describes a technology-focused practice for a new smartphone application and how it made the work efficient and helped drive cooperation and learning.
Agile in the Federal Space: Best Practices for Keeping Documentation Lean by Olivia Kasilik and Omar Silver . This report tells how the Food and Drug Administration Emergency Operations Network Incident Management System agile team reduced the burden of documentation requirements in their heavily regulated environment.
Using Communities of Practice for Alignment and Continuous Improvement at DigitalGlobe by Andrew Korbel. This experience report tells how several communities of practice (CoP) were started and their impacts on Digital Globe as they grew a project from 4 to 12 teams.
Implementing Disciplined Agile Delivery (DAD) at Panera Bread: A Recipe for Success by Mark Lines. This report describes how Panera Bread learned and applied Disciplined Agile Delivery (DAD) framework on their first project.
Portfolio Kanban - Seeing the Bigger Picture by Sandy Mamoli. This report describes how TradeMe introduced Portfolio Kanban alongside workflow and team restructuring to better manage their project pipeline.
Distributed Team Technology For Co-Located Teams by Daniel Markham. This report presents the advantages, benefits, and challenges when using various tools made for distributed teamwork and collaboration.
Marketing scrum vs IT scrum – two marketing case studies who now ‘act first and apologize later’ by Jeroen Molenaar. This report explains how Scrum principles can be effectively applied to the development of new marketing campaigns, their full commercial expressions, and even to new product development.
Origins of Teams: Darwinian Observations in the Wild by Blake Nyquist and Wade Wachs. This experience report covers the ongoing, 14-year evolution of an engineering team at a web hosting company that powers a sizable portion of the Internet.
Taking Our Agile Passion to a Volunteer Fire Department – A Report From the Fire Line by Tom O’Connor. This report tells how an agile coach applied his leadership and teamwork skills to volunteering at his local fire department and encourages us to take lessons learned from agile experiences to apply to other parts of our world.
Metrics for Understanding Flow by Ken Power. The report presents a useful set of metrics and describes how they reveal how work is flowing: Cumulative Flow, Throughput Analysis combined with Demand Analysis, Cycle Time, and Lead Time.
Our Estimates are Terrible! by Hans Samios. This report tells how at one organization even though they were planning the “agile way” they fell into the trap of over-commitment when the new idea (points) did not line up with the old, familiar estimating approach (hours).
Taking small steps in a big organization (An experience report on implementing Exploratory Testing into a large organization) by John Stevenson. This is a story of how the author implemented Exploratory Testing in a big company, one step at a time.
A ‘Creole Cottage’ pattern for building a Scrum Master Community and solving company-wide problems by Ni Sun. This report describes a pattern for building a Scrum Master community, solving company-wide problems and making continuous improvement for processes.
Converting A Successful Criminal Justice Program From Waterfall To Agile by Craeg Strong. This report explores the motivations for instituting Agile on an already-successful program with 2 million lines of code, the challenges encountered, and the lessons learned.
Mob Programming – A Whole Team Approachby Woody Zuill. This report describes Mob Programming, a software development approach where the whole team works on the same thing, at the same time, in the same space, and at the same computer.