User Request BAU Prioritisation process Investment Prioritisation process PM BRD Stakeholders BA BRD Product Backlog Ranked list of requirements from BRD.

Slides:



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

Armstrong Process Group, Inc. Copyright © , Armstrong Process Group, Inc., and others All rights reserved Armstrong Process.
Software Testing How has agile changed the game? Karen Greaves.
> Sprint Planning Presentation API Release: Date: Presented by:
Connect Team Connect Team Outside Contrib Outside Contrib Unscheduled Backlog Bugs Feature Requests BA Review Requirement Docs Epic Large Tasks or Features.
Renato Pinto López TUM18 - UPM. Sprint Planning Meeting ATTENDED BY PRODUCT OWNER (PO), SCRUM MASTER AND SCRUM TEAM PO DESCRIBES THE HIGHEST PRIORITY.
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.
Agenda −Scrum with TFS 2010 using MSF for Agile 5.0 −Planning the Project −How do you plan the project? −Project planning in TFS 2010 −Planning a Sprint.
C O N F I D E N T I A L 4-May-15 1 Attendee Management - Being Agile Attendee Management.
SCRUM © University of LiverpoolCOMP 319slide 1. SCRUM history In 1986, Hirotaka Takeuchi and Ikujiro Nonaka More an observation of good practise in manufacturing.
Scrum Jarred Payne Ashrith Pillarisetti. Scrum Prepare for Project Plan the Project Plan a Sprint Run a Sprint Track the Sprint.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
Visual Studio Online. What it Provides Visual Studio Online, based on the capabilities of Team Foundation Server with additional cloud services, is the.
Muthu Swamy S, APSM, PMP, CSM, PM-2008 Friday, October 1, 2010
Agile development By Sam Chamberlain. First a bit of history..
The Product Owner prioritizes the requirements or features through feedback from the Stakeholders & interaction with the core team The Team.
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.
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
Scrum’s Product Owner Role Jeff Patton Agile Product Design
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
Agile Adoption GMAS Product / Practice Teams PMO Meeting – May 2014.
SWEN 302: AGILE METHODS Roma Klapaukh & Alex Potanin.
Software Testing Life Cycle
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
When is Agile the Best Project Management Method? Lana Tylka.
SCRU M Scrum Overview - Commonly Used Terms Ali Qureshi, parorrey.com – 31 st Aug, 2015 PI Media parorrey.com.
Page 1 Scope and Objectives Achievements Past Week Plans Next Week/Month Project Status Project ManagerDavid PlouffProgram DirectorGene Saadi Project Start.
EVS Product Development Life Cycle Charles Griffin 9/19/2007
Rapid software development 1. Topics covered Agile methods Extreme programming Rapid application development Software prototyping 2.
Visual Studio Online Visual Studio.NET Work BuildTest Deploy Insights Code Visual Studio Online.
Presenter:Mohit Dhagat Student ID: Date:19 November 2014.
Sprint Plans and Burndown Charts David Millard | davidmillard.org.
SCRUM.
Personal Training Assistant – Sprint#1 Group Gamma.
Planning Extreme programming
Page 1 Scope and Objectives Achievements Past Week Plans Next Week/Month Project Status Project ManagerDavid PlouffProgram DirectorGene Saadi Project Start.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
NEM201 Week 4 Project Plan Create and complete outstanding items. 01. Front Cover 02. Document details 03. Scope Document 04. Technical Design 05. Creative.
SCRUM © University of LiverpoolCOMP 319slide 1. SCRUM history In 1986, Hirotaka Takeuchi and Ikujiro Nonaka More an observation of good practise in manufacturing.
Who is Gregg? 1 Mile
Geoff Davis Software Development Leader Software Development at eWater.
PDM-Project Delivery Methodology iDeaWORKS Journey from Good to Great Version: 1.0 Date: Feb 27, 2012.
1 Development with Agile methodology Scrum Lifecycle DEVELOPMENT PROCESS IN DROISYS INC.
Created By:-
#msdevcon Community Track IMPLEMENTATION OF SCRUM Bernardin Katić Insa Investment Software AG.
QA process for Business Catalyst projects.. Starting a project What QA needs to start testing::  Specifications – A detailed description of the product,
Project inceptionPlanning Requirements analysis DesignDevelopment OperationsDeployment User acceptance testing System integration testing Project conclusion.
From manual test shop to fully automated test coverage: A How-To session to speed up your journey Jayshree Bhakta ITHAKA/JSTOR.
Scrum.
Integrate Agile Testing into the Process
By: By: Agile Scrum Master Online Training.
Creating User Documentation in an Agile World
So You Want to Be a Product Owner
Chapter 3: The Project Management Process Groups: A Case Study
Summarizing Our Models to Date
SCRUM PROCESS RELEASE SCRUM PROCESS M SCRUM ROLES
Four Ways to Successfully Engage Stakeholders
Quality Assurance in an Agile Development Team Michelle Wu 2018 PNSQC
Introduction to Agile Blue Ocean Workshops.
APT – Planning the Next Phase & Resourcing Risk 2 Nov
Training 01: Project Lifecycle & Business Technology Analysis
Iteration Planning.
Software Development In Agile
Scrum in Action.
Scrum: Daily Stand Up Meeting
Walking dead. How to save project?
Planning the Prepare Stage
Executive Project Kickoff
Software Development In Agile
Presentation transcript:

User Request BAU Prioritisation process Investment Prioritisation process PM BRD Stakeholders BA BRD Product Backlog Ranked list of requirements from BRD. -Prioritised -Ordered -Sized Process: BA + Dev + PO: to work out the priority and ordering of items in the Product Backlog. Dev to provide high level estimates on the requirements. Meetings: BA Process: BA: To run workshops with the business to expand upon and signoff subset of requirements from the BRD which are to be picked in the next sprint. Meetings: Regular Workshops with stakeholders specific to the subset of requirements picked up from the backlog. Stakeholders Signed off items Backlog Bi Weekly Sprints Sprint Backlog Iterative delivery Dev & testing Dev Team

2 KSOR/BAU - BA User Request Technology Team Production Support JIRA – BAU Unscheduled Process: KSOR / BAU requirements from the below stakeholders are registered by the BAU BA: 1)User Requests Bugs / Issues Enhancement to existing functionalities Small size new functionalities 2)Production Support Automation requests for manual tasks User requests directed to production support 3)Technology team Performance improvements Infrastructure/system upgrades (ARM, DMS, etc.) Technical enhancements to improve the system (stability etc.) JIRA (BAU Unscheduled) Process: 1.For each of these requests the BA adds / modifies a JIRA in the “BAU Unscheduled” release. 2.This may require some workshops with the stake holders to understand and clarify the requirements. 3.All details must be entered in JIRA, which is the only true version of the exact requirement.

3