Lean Software Management: BBC Worldwide Case Study Dr Peter Middleton MBA 13 th June 2014 IASA Ireland, Dublin Irish Computer.

Slides:



Advertisements
Similar presentations
Metrics and Databases for Agile Software Development Projects David I. Heimann IEEE Boston Reliability Society April 14, 2010.
Advertisements

Iteration Planning.
© eComScience Pvt. Ltd OffshoreSoftwareDevelopment eComScience Consulting perspective.
Tech Next - Scrum Vs Kanban practiced in product development Tech Next, May 7, 2011
Lean Software Management: BBC Worldwide Case Study submitted to Professor Shervin Shirmohammadi in partial fulfillment of the requirements for the course.
Delivering Enterprise Projects Using Agile Methods Brent Barton May 23, 2006.
We ensure collaboration through a unique Moneyball-style approach to team assembly Agile Team, Custom-Designed for You Works well together Fits seamlessly.
An Approach to Managing Projects Hadeel Elamin Lead Project Manager
Public March 4, 2013 Head SDLC & ITIL Development and Consulting Peer M. Künstler The Journey to Agile WM IT and UBS Switzerland IT.
Ni.com Introduction to Agile and Scrum Speaker/Author: Paul Packebush Section Manager, Corporate Metrology Author:Logan Kunitz Staff Calibration Engineer.
Agile and Scrum: Executive Summary June 2, 2011 Bob Schommer, CSP, PMP, MCTS Senior Project Manager Skyline Technologies, Inc.
Sharif University of Technology Session # 3.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
ITEC 370 Lecture 25 Lifecycles. Review Questions? F give prototype demonstration –Testing plan for your software Life cycles –Scrum (Roles, Meetings,
Scrum introduction XP Days Agenda Introduction The Scrum process – roles, ceremonies and artifacts Backlog management Conclusions and questions.
Agile development By Sam Chamberlain. First a bit of history..
© ThoughtWorks, 2008 Improving Productivity and Quality With Agile Patrick Kua.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Discover how to improve productivity by going DevOps and SAFe.
Coming up: The Manifesto for Agile Software Development 1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 3 Agile Development Software Engineering:
Agile Project Management PMI Metrolina PDD Saturday September 27, 2014 UNCC Uptown Mike Ryan.
ALTERNATIVE METHODOLOGY -KANBAN CMIS-570 Jacob Adams.
Programming with eyes wide open. Your host today Subby Angelov Team
The Product Owner prioritizes the requirements or features through feedback from the Stakeholders & interaction with the core team The Team.
Agile Methodologies for Project Management By – Komal Mehta.
Is Agile Any Better? Damon Poole 2009 Scrum and Kanban Like Chocolate and Peanut Butter Damon Poole – CTO, AccuRev.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
Kanban “Signboard”.
Get quality results faster: Agile Projects and your team Presenters: Laurie Barnas and Wendy Taylor, Associate Registrars, University of Victoria.
Agile Software Development Brian Link
Tuesday, June 8 th, Agile Development-Successful Delivery & Implementing Across the Enterprise.
By Saravanan Bala. General Report 31 % of Software projects are cancelled 75 % of the software projects are considered failures by the people who initiated.
4/23/ :45 PM © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered.
Rapid Application Development. What is RAD……..?  Rapid Application Development (RAD) is a software development process.  first developed during the.
Coming up: The Manifesto for Agile Software Development 1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 3 Agile Development Software Engineering:
Computer Science and Software Engineering© 2014 Project Lead The Way, Inc. Software Design Process.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
The Confounding World of Process Methodologies By Thelma Hataria.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 4 Agile Development Discussion of Agile Development and Agile Process.
Agile Information Management Development. Agile Project Management Characteristics  Acceptance and even welcome of changing requirements  Incremental.
Chapter 3 Agile Development
Theories of Agile, Fails of Security Daniel Liber CyberArk.
Dr. Rob Hasker. What if every project used Scrum?  Why might Scrum not be perfect for every project? Hard to get the big picture Early choices may have.
User Group Meeting 2/11/2010 – 6:00 p.m.. Meeting Agenda 1. Group Goal: To create a forum in our local area where we can exchange ideas related to agile.
2 nd Class -Business Cases – Value Proposition -Agile vs. Waterfall Development Process Bus100: Building Software Products: From Strategy to Sales John.
Lean Software Management: BBC Worldwide Case Study EECS811: IT Project Management Case Study Cody Mock February 8, 2016.
Dr. Rob Hasker. Should every project use Scrum?  When might Scrum not be an appropriate model?  What are some of its limitations? Hard to get the big.
APMG-International Webinar Integrating Agile into PRINCE2® Thursday 19 December 2013 / 13:00 GMT Presented by Melanie Franklin,
Kanban Advanced Software Engineering Dr Nuha El-Khalili.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Agile = regular iterations, releases time-boxed incremental regular heartbeat streamlined collaboration co-located team on-site customer face-face communication.
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Agile Gintarė Bernotaitytė © 2013.
Barnes & Noble Alonda Morgan. Agile UX Agile.
Introduction to Agile Project Management Presented by Maury Richards, CSP.
Manifesto for Agile Software Development
Continuous Delivery- Complete Guide
Agile Training Day 2 November 17, 2015.
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Real Metrics for Real Decisions
Agile Software Development Brian Moseley.
Navigating an Agile Transformation
Waterfall and Agile Quality Techniques
How to Successfully Implement an Agile Project
Teaching slides Chapter 1.
Introduction to Agile Blue Ocean Workshops.
Agile Development.
Adapting Agile in Pharmaceutical Industries
Using SCRUM the NHC-IT Way!
Presentation transcript:

Lean Software Management: BBC Worldwide Case Study Dr Peter Middleton MBA 13 th June 2014 IASA Ireland, Dublin Irish Computer Society

IASA 1.Business Technology Strategy 2.IT Environment 3.Quality Attributes 4.Design 5.Human Dynamics

Volume + Constant change Requirements / Budgets / Business Sponsors Users Hardware / Networks Database Software Staff skills and availability Culture / Privacy / Legal / Learning

UK Government advice PRINCE2: ‘Ensuring that the information required for the project team is available.’

BBC Worldwide Digital Hub Software Team Waterfall Agile Lean London 9 staff: Analyst, Architect, QA, Developers Operating cost: £1.5m p.a. C#,.NET, MS SQL Server RISK

Lean Software – key ideas Reduce Work in Process: –Minimum Marketable Feature –Analysis / Specifications –Design –Untested code Reduce total end to end time –Visible management & less risk –Flexibility

BBC

Lead time to customers -37% Variance -47%

Throughput: smaller, incremental deliveries

Fewer Bugs: -24%; Variance: -33%

Possible problems 1.Space needed for Kanban & info boards 2.Plan driven, document centric process 3.Poor fit with standardised reporting 4.Remit of IT – upstream & downstream 5.Command & control compliance model 6.Staff initiative and multi skilling Lean handles risk by low WIP, transparency, small units & frequent deliverables

Conclusion Lean provides discipline and agility Software under quantitative control Frequent, small, high value deliverables Experiments to demonstrate: –End to end time measure –Work in Progress – white board & post notes Lean Software Management: BBC Worldwide Case Study, P. Middleton & D. Joyce, IEEE Trans. on Engineering Management

Continual Improvement Days lost: -81% 26 to 5 days

Development Time -73%; Variation -78%

Differences Agile and Lean Batch / Push versus Pull –Time-boxed iterations Reliance on Data –Focus on people Continual Improvement – ‘impediment list’ / ‘improvement backlog’‘ Multi skilling –Velocity’, features, story points

Engineering Practices Decoupling – improve legacy code Test Driven Development (unit tests) Automated Acceptance Testing Source Control Software Bug tracking software Daily Stand Up (15 minutes)

Follow up to the IEEE article /04/09/lean-software-management-bbc- worldwide-case-study/ /04/09/lean-software-management-bbc- worldwide-case-study/ (lean tool)