Agile/Scrum Case study Code name: ninja.  2 scrum teams  One product backlog  8 months so far  Long term project  External integrations  R&D and.

Slides:



Advertisements
Similar presentations
Agile Lifecycle, Tools, Techniques IM Symposium.
Advertisements

Iterative Development: Done Simply Emily Lynema NCSU Libraries Code4Lib 2010.
Tech Next - Scrum Vs Kanban practiced in product development Tech Next, May 7, 2011
> Sprint Planning Presentation API Release: Date: Presented by:
An Agile Retrospective Clinton Keith Overview Retrospective format What works (clear wins)? What doesn’t work so well? What do we need to start doing?
Building an Effective SDLC Program: Case Study Guy Bejerano, CSO, LivePerson Ofer Maor, CTO, Seeker Security.
Agile at ON.Lab Bill Snow VP of Engineering. What is waterfall? RequirementsDesignDevelopTest Or Requirements Design Develop Test Time.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
C O N F I D E N T I A L 4-May-15 1 Attendee Management - Being Agile Attendee Management.
Release Planning – Test Role and Responsibilities Emergence Tech Training / emergencetechtraining.com.
Clinton Keith CTO, High Moon Studios Agile Methodology in Game Development: Year 3.
Agile-Scrum in QA – Case study at TraderTools Amitay Itskovitch TraderTools LLC QA Manager Phone: ,
Walter Bodwell Planigle. An Introduction – Walter Bodwell 18 years in software First did agile at a startup in 1999 Went back to waterfall (after acquisition)
Scrum in 30 minutes! Oddly, a 45-minute presentation by Carl Chatfield Content Project Manager, Microsoft Puget Sound MPUG September 2009.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
Rules of the Game  Loosely based upon the TV show, “Who wants to be a millionaire.®”  Once the question is read, you will have 30 seconds to discuss.
Agile development By Sam Chamberlain. First a bit of history..
© ThoughtWorks, 2008 Improving Productivity and Quality With Agile Patrick Kua.
Introduction to Agile.
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
Adopting Agile for Enterprise Software Joe Bedell, Software Engineer Jason Breen, Software Engineer Peter Melko, Scrum Master June 15 th, 2015.
Software Development Landscape
Technical Documentation in Agile Colin Greenberg.
Agile Assimilation & Scaling. 2  About me…  How did we start?  Bottom-up  Task Force  Learning  Pilots  First stage analysis + recommendations.
Agile Software Development Brian Link
What is Scrum Process? Where is it used? How is it better?
Resource Systems.  The need for agility  History of Product Development  Delivery of EPCOT  Future Challenges & Recommendations  Reflection  Questions?
Software Development and Release Management By James Lawrence Software Development Manager.
Agile Adoption GMAS Product / Practice Teams PMO Meeting – May 2014.
SCRUM Not your average bacon and eggs. The Basics Product Backlog Sprint Backlogs Sprints – The Daily Scrum – Burn-down chart Sprint Retrospective.
When is Agile the Best Project Management Method? Lana Tylka.
Enterprise Project Management
4/23/ :45 PM © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered.
1 - Agile in a nutshell. 2 - Basic principles ●Relies on an iterative, incremental development mechanism with continuous adaptation to customer requirements.
Copyright © 2012 by Mark J. Sebern Scrum Overview (from
Het einde van het beroep van tester - Wat Agile, DevOps en Scrum betekenen voor het testvak -
WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ CA Agile Vision Product Manager Michael Lester.
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
Learning to Craft Code is Challenging Every skill we have acquired was trick at first We need to take baby steps We need proper support.
Who is Gregg? 1 Mile
Geoff Davis Software Development Leader Software Development at eWater.
Agile Ceremonies. Agile - Ceremonies cer·e·mo·ny serə ˌ mōnē noun 1. a formal religious or public occasion, typically one celebrating a particular event.
1 Development with Agile methodology Scrum Lifecycle DEVELOPMENT PROCESS IN DROISYS INC.
Strategy Mapping Clear path to a successful Agile strategy Dave Neuman Sep 24, 2015 LinkedIn:
Created By:-
Utilize Agile Project Management for GIS Projects Jennifer Prather and Lana Tylka.
Skiing and Boxing Coaching Product and Enterprise Teams 黃馨誼 蘇育光 修訂.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Flight Software Conference 2016
Change your look and feel to how you work! Let’s SCRUM Change your look and feel to how you work!
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Product Sprint Backlog Backlog Up to 1 Month The Scrum Framework
Delta Shell Technical Aspects
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Real Metrics for Real Decisions
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
By: By: Agile Scrum Master Online Training.
SAFe Workshop - Oct 17 Presenter: Ray Brederode
Product Backlog List of things that needs to be done to make the product come into existence 
CSCE 741 Software Process Lecture 04 Availability
Fast, Agile, Simple Decemebr 2017 Think Simple, Run Faster.
CSCE 741 Software Process Lecture 04 Availability
Scrum Overview.
Agile practices for documentation teams
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Introduction to Agile Blue Ocean Workshops.
Scrum in 10 slides by Pierre Mengal – Scrum In Ten Slides v2.0 is licensed under a Creative Commons Attribution-NoDerivs 3.0 Unported.
Training 01: Project Lifecycle & Business Technology Analysis
Scrum: Daily Stand Up Meeting
Presentation transcript:

Agile/Scrum Case study Code name: ninja

 2 scrum teams  One product backlog  8 months so far  Long term project  External integrations  R&D and QA Off shore About the Project

Getting The Project Rolling Planning Release planning Backlog grooming Pre planning Tech planning Content planning Capacity calculations Sprint length Team work Day to day Intense work Daily monitoring Daily meetings Visible value Effort estimation Focus & time management Quality Accurate test plan Continuous Builds Automation On going BUG fixing Stabilization sprint System test Handover to QA

Two teams, one backlog, one sprint review Empowerment Daily meeting Sprint review Retrospective Scrum philosophy Knowledge sharing Personal opportunities Intensive relationships PO/PdM QA Scrum master Developers PjM Tech writers Group manager Benefits and Challenges Hyper productive Visible value Off shore Stabilization Integrations Shared code ownership

PBL Developer/s Agile as a Rich Tool Box In sprint QA Architecture design Stabilization Sprint Automated testing Design Review Release Planning Technical Planning Pre-Planning Backlog grooming Sprint Review Retrospective Scrum of Scrum Cross teams Sprint Review

Feedback: Privacy Policy Feedback
Do Not Sell My Personal Information
About project: SlidePlayer Terms of Service

© 2025 SlidePlayer.com. Inc. All rights reserved.