scrum overview for kingfisher
Post on 30-Jan-2016
222 Views
Preview:
DESCRIPTION
TRANSCRIPT
1
Scrum Methodology Application Development
2
Agenda
Overview – Why did we change the way we execute mRFCs (Minor
Requests for Functional Changes)?– AGILE Software Development overview
SCRUM Methodology (New Minor RFC process) Business Benefits Demo Tool
3
Customer Background
Products for MusiciansProducts for MilitaryProducts for Home Products for Testing
A Research company - Founded in 1964 Global Company
Geographies across North America, Europe & Asia Pacific Headquarters in Framingham, MA Automotive Division in Stow, MA
Privately held Vision ‘ Better Sound Through Research’
Primary Business divisions Home Entertainment Division Automotive Services Division Noise Reduction Technology Division Professional Products Group Electroforce Systems Group
Products for Auto ind
4
Global SAP Snapshot
Services in Scope
L2 – Application Support - Business Process Support (How-to’s), Analysis & Troubleshooting
Monitoring, Patch maintenance Root Cause Analysis , Documentation Break-fix support: Configuration , FRICE Standard Requests (SLRC) Monitoring Activities Incident Resolution Governance SLA Reporting – Response & Resolution
Application in Scope
SAP R/3 4.7 SAP ECC 6.0 SAP SCM 7.0 SAP SRM 7.0 SAP CRM 7.0 SAP GTS 8.0 SAP BI 7.3 SAP SOLMAN 4.0 (Charms)
Modules in Scope
SAP SD / LE SAP GTS SAP FICO SAP MM / WM SAP CRM SAP BI SAP HR SAP BPC SAP BASIS SAP XI SAP APO – DP, SNP SAP ABAP SAP ABAP CRM SAP Security (user administration)
Geographies in Scope
US Landscape-US, Mexico, Canada, Japan, Ireland, Germany, Australia , India ,Middle East and Africa, China , MalaysiaEU landscape-Netherlands, UK, Luxembourg, Belgium, France, Italy, Hungary, Scandinavian countries, Switzerland, Poland, Ireland
Support Window Coverage
24x5 global support leveraging an onsite / offshore model for SAP for most of the modules. For detailed Coverage, pl refer Subsequent slides.
24x7 on call support for Critical & High tickets
Detailed Support window is given in the subsequent slide
Tools used
Remedy – Ticket logging tool Share point – As data repository Cronacle / Autosys SOLMAN – Documentation
Out of Scope
Non – SAP Applications Network / Infrastructure
support Minor RFC Major Projects Security (Role Admin) Master Data Mgmt SAP WCEM
Support locations
US – Stow / Framingham Mexico – Queretaro India - Mumbai China - Shanghai Netherland – Amsterdam Belgium - Brussels
SLA
5
The Goal
The Goal:– To increase the productivity 3 to 5 times faster than what was
currently done.
The Problem:– Demand for mRFC tickets was high.– Cycle time to close a ticket was slow– Business priority was constantly changing
• Agile Software Development: A project management Process that encourages frequent
inspection and adaptation, a leadership philosophy that encourages team work, self-organization and accountability, a set of engineering best practices that allow rapid delivery of high quality projects and a business approach that aligns development with customer needs and company goal.
6
What is Scrum?
An agile software development framework: Self-managed, co-located teams comprised of IT
and business members (SMEs) Work is structured in cycles of work called Sprints.
We have decided to start with monthly Sprints. During each Sprint, team pulls from a prioritized list
of customer requirements so that the highest value features are developed and tested first. This list is created by the Product Owners.
Visual management techniques to manage and communicate daily activities and progress
7
Scrum Roles
Act as the facilitator Buffer between the team and any distracting influences. Remove impediments
Owns definition of Success Focus on ROI Represents the stakeholders and the business Maintain and prioritize the product backlog
Typical 5-9 members team Cross-functional group of people Members should be full time Responsible for self managing the development
8
Scrum Practices
9
Scrum Artifacts
Scrum (Agile Methodology)
Sprint backlog
Sprint2-4 weeks
24 hours
Demonstrable New functionality
Productbacklog
10
Team Composition
Scrum team– 1 to 2 Developers– 3 to 4 Analysts ( Analysts from various modules like MM,
SD, FI CO etc)– 1 Scrum Master– 1 BCM analyst
Scrum teams
– 12 SAP Scrum Teams
– 10 in US, 1 in India, 1 in China
11
What is a Product Owner?
All business-driven minor requests for change (mRFC) will be approved, prioritized and supported by a member of the business
• Reviews business requirements to determine whether the stated requirements are unclear, incomplete, ambiguous, or contradictory, and then resolve these issues to arrive at a clear problem statement
• Owns the vision, backlog (open tickets) & ROI analysis for the business
• Assess priority and business benefit & aligns priorities across other businesses
• Representative in the Sprint planning meeting – recommends which tickets to include and coordinates business SMEs to answer detailed questions about tickets
• Works with Scrum team to assign & schedule subject matter experts (SME) to the Sprint
12
Old Process for Prioritization and Scheduling
13
New Process with Product Owner
14
High Level Scrum Process
mRFC tickets submitted by SAP
Service Desk
Sprint backlog aligned with Business by Product owner
Grooming/ T Shirt sizing done for tickets by Scrum team,DA, Product owner and SME
Sprint retrospective meeting at the end of the sprint cycle.
Proposed Sprint backlog created by Product owner
Execute sprint cycle i.e.Develop & Test with the Business user or SME
Product Owner evaluates, cleanses & prioritizes tickets based on business value
Sprint demo (KT session) with Product owner, Business and support team
Sprint planning session with scrum teams for allocation of tickets
15
What is SCRUM ??Scrum is an iterative and incremental agile software development method for managing software products and projects or application developments.
Why SCRUM ??To increase the productivity 4 times• Early and regular Deliveries• Inspection And Adaptation• Transparency• Greater business involvement in design process• Prioritize business requirements effectively
Who does SCRUM??•The Product Owner•The Scrum Master•The Team
How SCRUM works??
16
SCRUM Inception at Customer
Agile Transformation Journey
oPilot Scrum project was started in 2009 at US with 3 people team
oPost success of the pilot team in US, customer had decided to start the new Scrum team at offshore India at 2011.
oScrum Master training was provided to one of the project manager
oCustomer had provided the training for Scrum to the offshore TCS team
oTeam has successfully completed 28 sprint cycles from offshore with the weekly velocity of 40 points. In all The team has complete around 100+ enhancement / developments
oAfter the success of India scrum team, new Scrum team has been started in China in Sep 2013
oScrum Master from India travelled to China, to train the China scrum team on Clients Scrum principles and also completed 1st sprint cycle from China
oAs part of the clients agile transformation roadmap, currently there are 9 scrum teams across US, Europe India & China which are taking care of projects and minor enhancements.
oTCS SAP team has been appreciated by the client time and again for achieving very high client satisfaction through outstanding performance.
17
Sprint Demo Meeting (Handshake between Tier2 and Tier 1)
One per Sprint Team invites Product Owners and Tier 1 to see an
overview (business process and technical)•Standard formats for presentation•RFS Documents available on share point portal with detailed advance intimation on the HD tickets
•Adequate time spend on each ticket with actual SAP transaction testing and explanation of code/configuration documentation
•Feedback on Demo given by each team member for improvements and clarifications
18
Scrum Business Benefits
Dedicated cross-functional team focused only on minor requests for change
Increased throughput by reducing churn in the “test, fix, then test again” pattern
Greater business involvement in design process to achieve better first pass quality results
Improved focus on prioritization
100% offshore model to minimize the cost.
Overall reduction of Non-Value Adds or waste while resolving minor requests for change(Nearly 84% reduction)
On time delivery increased to nearly 70% using this methodology
19
Tasks in mRFC
User Contact Establish USER
Story correctly formatted STORY
Research completed RESRCH
Functional specification s Completed RFSDOC
ARIS model complete ARIS
Tech Spec completed TECH
Configuration completed CONFIG
Development completed DEV
Unit testing completed UNTTST
QA Approved QAAPPR
Batch Jobs/Process change finished BTCHJOB
Code Review completed CODREV
Test script written TSWRT
User approval USAPPR
Domain Architect ( Solution Architect) Reviewed DAREV
Communication completed COMPREP
Communication approved COMAPPR
Training Documents TRNGDOC
Cut-over activities completed CUTOVER
Demo Posted DEMO
BI/Security BI/SECURITY
PRD
QA
DEV
USER
STORY
RESRCH
RFSDOC
ARIS
CONFIG
BTCHJOB
TSWRT
TECHDEV
UNTTST
CODREV
TRNGDOC DEMO
USAPPR
DAREV
COMPREP COMAPPR
Sequence of Tasks
CUTOVER
20
DEV
STORY
As a: As a planner at Bose Automotive GmbHI want to be able to: Send one ASN to Porsche Leipzig (ship-to 90204) per each demand time slice for a given day, while packing all materials in all the time slices for that day onto a single pallet. Please see details of requirement in the attached Word doc.
So that: we can fulfill a customer requirement.
I will know this is done when: I can process each time slice during a day as a unique ASN but still be able to pack multiple time slices into a single pallet. Pallet may be single or mixed materials.
What is the impact of NOT implementing this change: We will be charged a fine (EUR 105) for each ASN which is not compliant. Note: We currently sell approximately EUR 1M per month to this customer.
USER
User is contacted •To confirm availability during the sprint time line•Clarification for the additional inputs if the story is not clear
RESRCH
• Scrum team will start research on the ticket based on the initial understanding of story and the additional inputs if any provided by the user.
Tasks details
21
RFSDOC
Functional specification document will be prepared by functional analyst incorporating the required configuration and development
DAREV
Functional specification document will be sent to the DA (Domain architect/ solution architect ) for vetting.FS may under go a change based on the feedback received from DA after approval the subsequent steps will be followed.
CONFIG DEV
Once the FS is approved the functional analyst and developer will initiate the configuration and development for the required changes as per the story.
TECH
Based on the development the developer will prepare the technical specification document.
and
DEV
CODREV
Code review will be performed for the development done with reference to technical specification.The development / tech spec may under go a change in case of any suggested changes by the technical reviewer.
UNTTST
Unit testing will be performed under development environment by the functional analyst to check whether the configuration and development done are aligned with the story.
Tasks details
22
QA
TSWRT
Once the unit testing is successful the configuration and development will be moved to Quality environment for the integration testing.Test script will be prepared by the functional analyst for the integration testing done.
USAPPR
Test scripts are tested by the business user under quality environment and approval for moving the changes to the production environment will be provided accordingly.
ARIS
BTCHJOB
COMPREP
A Communication will be sent to stake holders who all would be impacted by the changes done so that they are aligned with the new changes which would be moving to production environment.
Create request to set up Batch job if applicable
Check if existing business process module needs to be rebuilt or new process to be mapped in Aris
Tasks details
23
PRD
CUTOVER
Cutover activities are required to be performed under the production environment once the changes are moved.
COMAPPR
The communication is accorded by the stake holders.
TRNGDOC
DEMO
The training document will be prepared by functional analyst for the stake holders.
Demo document will be prepared and presented as a knowledge sharing to the production support team.
QA
Tasks details
24
Tools Used for Monitoring Scrum
Online task board by Bigvisible
https://seenowdo.com/index.xhtml
25
Scrum Monitoring Tools/Burnt Down Chart
26
Enhancement & Development – Matrix Scrum Project
Weekly Sprint points
Business Points
top related