Define Ideation Develop Idea to working software Operate Working software to business outcomes Requirements backlog Monitor Implement SHORTENED.

Slides:



Advertisements
Similar presentations
© 2000 Scott Moses Action Management Process Scott Moses Assistant Professor School of Industrial Engineering.
Advertisements

Iteration Planning.
Scrum in 10 slides.
Delivering Enterprise Projects Using Agile Methods Brent Barton May 23, 2006.
ITEC 370 Lecture 24 Lifecycles. Review Questions? –Grades for Requirements/Design Doc F give prototype demonstration –Testing plan for your software Maintenance.
UI Application Logic Out of the box approach View ViewModel Model Model-View-ViewModel (MVVM)
Working on an Agile Team with Visual Studio 2012 and Team Foundation Server 2012 Peter Provost Sr. Program Manager Lead Microsoft Corporation DEV318.
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.
Supporting people with a learning disability Introduction to Project Management Presenter: Steve Raw FInstLM, FCMI.
Lecture 6 - Project Planning. Lecture 6: Project Planning Overview Creating an outline plan –Work Breakdown Structure –Identifying tasks Waterfall and.
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.
The New Product and Services Development Process By SK Winning Innovations for Tomorrow (WIT)
Project Life Cycle.
04 | Define a Software Iteration Steven Borg | Co-founder & Strategist, Northwest Cadence Anthony Borton | ALM Consultant, Enhance ALM.
Welcome to Leadership Team Meeting 2 Auburn Wesley Foundation.
OFFICE OF INFORMATION AND TECHNOLOGY Mobile Applications Scrum Framework November 21, :00 am (EST) Seal of the U.S. Department of Veterans Affairs.
Copyright © 2015 Curt Hill Software Development Paradigms What do you need to know?
Collaborative leadership workshop Survey Results Paul Gibson 25/May/09.
Theories of Agile, Fails of Security Daniel Liber CyberArk.
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
Evolutionary Software Development(ESD) Premkumar.
Cultivating Agile Requirements
COPYRIGHT TOM SULZER © 2015 IS 455 Oct 1, 2015 Agenda House Cleaning Quick Review Initiate Second Life Project Teams for Second Life Project are the teams.
SCRUM OFTEN INTERNAL Focus on the customer Sustainable Company.
WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ CA Agile Vision Product Manager Michael Lester.
We’ll cover:  1. What is a Kanban System and how does it apply to anything you want to do?  2. How to set up a Kanban System 2.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
OFC308 Hilton Giesenow Development Manager - 3fifteen Host –
Introduction to Agile. Introduction Who is this guy?
Scrum Overview. Agenda What is scrum…and what it isn’t Scrum’s Characteristics The Scrum Process Scrum Phases Measurements Key Practices Backlogs Sprint.
MIS 5402 Managing Technology and Systems Week 7: Global Management and Platform Strategies Spring 2017 David S. McGettigan Adapted from.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Copyright © Curt Hill Scrum Software Development Paradigms What is a Scrum?
About Me learn Professor 3 startups. Simplifying Agile – Delivering Value Quickly.
From manual test shop to fully automated test coverage: A How-To session to speed up your journey Jayshree Bhakta ITHAKA/JSTOR.
TechEd /22/2018 7:16 PM © 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks.
Scrum.
Guidewire The Flexible Organization
Agile Scrum Management
Project Management Processes
Improve Business Satisfaction by 10% Through Business Relationship Management Relationship management is the #1 driver of business satisfaction with IT.
Scaled Agile Requirements: What, When & How
Product Backlog List of things that needs to be done to make the product come into existence 
So You Want to Be a Product Owner
Process Improvement With Roles and Responsibilities explained
CSCE 741 Software Process Lecture 04 Availability
Decision Making A quick and simple system for decision making.
Johanna Rothman Agile Team Measurements Chapter 12
How to Successfully Implement an Agile Project
Summarizing Our Models to Date
Scrum Overview.
Case Study: Financial Services
DIGITAL OPPORTUNITY TRUST STARTUP!
CSCE 741 Software Process Lecture 04 Availability
Agile practices for documentation teams
Sprint Planning April 2018.
Initiative Governance Process Model
Program Prioritization
Introduction to Agile Blue Ocean Workshops.
Project management Learning Unit 5.
Project Management Processes
Scrum in 10 slides by Pierre Mengal – Scrum In Ten Slides v2.0 is licensed under a Creative Commons Attribution-NoDerivs 3.0 Unported.
Agile Development – a new way of software development?
Legacy transcripts Planning Meeting March 7, 2019.
Scrum in Action.
Are you measuring what really counts?
Speaker’s Name, SAP Month 00, 2017
Brooklyn Harper and Destiny Konan
Using SCRUM the NHC-IT Way!
Presentation transcript:

Define Ideation Develop Idea to working software Operate Working software to business outcomes Requirements backlog Monitor Implement SHORTENED CYCLE TIMES Team Measure Validated learning

As an executive, I want to expand to new markets so that we can improve overall profitability and lower risk.

To doDoingDoneTo do (3)Doing (4)Ready (3)In Prod Executive/Vision level Ideas are refined, prioritized, budgeted, resourced, tracked through realization Management/Epic level Epics are defined, decomposed into stories, prioritized, and pulled by teams To do (3)Design (2)Dev (3)Test (2)Done Teams/User Story level Stories are implemented; teams self- organize within a common cadence To do (6)Doing (6)Done

Executive/Vision level Sets the priority for ideas Management/Epic level Determines the breakdown and ordering needed to deliver ideas Sets the priority for epics Teams/User Story level Determines the breakdown and ordering needed to deliver epics

As a TechEd attendee, I want to quickly provide session ratings so that I can provide effective feedback and improve future events. Acceptance Criteria: 1)Identify URL in < 10 seconds 2)Persist logins between browser sessions 3)Search for session by number, title or speaker 4)Provide feedback in < 1 minutes

As a TechEd planner, I want a session and speaker rating system so that both good and poor topics and speakers can be identified to improve future events. Acceptance Criteria: 1)System is easy to use 2)Speakers can view all session scores, not only their own 3)Attendees are able to easily rate sessions and speakers

To doDoingDoneTo do (3)Doing (4)Ready (3)In Prod Executive/Vision level “Backlog” items potentially persist for 6 months to several years Management/Epic level Backlog items look ahead 2-6 months To do (3)Design (2)Dev (3)Test (2)Done Teams/User Story level Backlog completed in 2-4 weeks To do (6)Doing (6)Done

To doDoingDoneTo do (3)Doing (4)Ready (3)In Prod Definition of done Criteria for final acceptance The what, not the how More than functional: -ilities, standards Ready state A definition of done for to-do column What’s needed to get started Not necessarily all info needed to finish To do (3)Design (2)Dev (3)Test (2)Done Let teams figure out their how To do (6)Doing (6)Done