Professional Documents
Culture Documents
Dec 2015
2
Agenda
1 2 3 4
ENHANCEMENT &
GLOBAL ROLLOUT IMPLEMENTATION UPGRADE SUPPORT
5
Agile Applicability
GLOBAL
ROLLOUT
• Several Agile teams can be formed and follow Scrum of Scrum to run multiple
enhancements/developments. For very large program SAFe framework can be
recommended.
UPGRADE
• Agile requires frequent releases in span of a few weeks. Larger processes will need
several releases to attain full workable status. During this period it will difficult to
provide demos to the customer on the end to end process
6
IMPLEMENTATION
ENHANCEMENT
• Most important business processes are already in place and working in Production.
Only new enhancements are required which are mostly development projects and do
not impact base configurations.
• Reduced Time to Market and Early ROI is attractive for enhancements rollout
7
SUPPORT
SLA dependent incident resolution is not applicable in SCRUM framework. Need to use
other agile techniques like Kanban
8
Typically Oracle needs big-bang approach with high visibility of the end
Entire development
01 to end (E2E) process/requirements, so it is a challenge to break into
takes place in short
sub-processes and achieve the business value in an iterative approach
Sprints/Iterations
Each iteration with A typical E2E business process cuts across various modules and may
02 demo-able not be fully configured in a single sprint/iteration
functionality A working E2E process may only be ready for demo after several
Sprints/Iterations
Direct Collaboration
Dependency
management
Impediment resolution
User Stories
Onsite
Manager Master
Sprint Sprint Heavy Collaboration Stand Ups
Product Backlog Retrospective
Tasks
Backlog Solution
Product - Story Grooming
Architect/ - Functional/Technical Dev Leads
Manager Discussion
SME - Demos & Feedback
- Dependency
Resolution
Product - Backlog Proxy Product
creation/Prioritization
Owner - Stand Ups/Status Owner
Meeting/Retrospective
Step 2
• Package Evaluation Strategic Planning Workshop
Step 3
• Organizing Project Methodology
Step 4
• Project Scoping
Release Planning Workshop
Step 5
• Requirement Gathering
Step 6
• To-Be Design
Step 7
• Package Configuration
Step 8
• Custom Development
Step 9
• SIT/ IT/User Acceptance
Release Sprint
As Per Release plan
Step 10
• Cutover and Go Live
14
Global Rollout Approach - Waterfall Vs Agile
Agile
Waterfall
Strategic Planning Workshop (Scoping)
• Global Template Validation
Step 1 Global Template Release Planning
Workshop`
• Solution Definition
Step 2
• Go-Live
Step 5
Release Sprint
As per Local Release Plan
15
• Upgrade Assessment
• Study existing Business Processes Release Planning Workshop
Step 1 • New System study
• SIT Upgrade
• Refine Trail Upgrade Solution
Step 3 • Perform Integration and testing
• UAT Upgrade
• Perform UAT and Signoff
Step 4
Note : Team to be collocated with in onsite and offshore. Split of locations with in Onsite and
offshore will make Agile model highly ineffective
17
Model - 1
• Onsite and Offshore have at least a 3 hour overlap in working hours
Typical Team
Recommended Operating Model Composition
Scrum Team Size – 10 to
• Onsite and Offshore operate as a Fully Integrated Scrum Team
12
Onsite to Offshore ratio
• Task Level distribution of work
– 30:70
5 Developers : 2 Testers
• All Scrum Team members attend a single daily ‘Standup’ call
: 1 Designer : 1 Product
• Onsite team may hand over a complex User Story needing frequent Owner : 1 Scrum Master
customer interaction to offshore team once complexities are resolved
18
Model – 2
• Onsite and Offshore do not have a significant overlap Typical Team Composition
Onsite Team Size – 6 to 10
• Total project team size is exceeds 15 members 1 Onsite coordinator for
Offshore team
Recommended Operating Model 3 Senior Developers : 1 Testers :
1 Product Owner : 1 Scrum
• Onsite and Offshore operate as a Fully Integrated Scrum Team Master
Offshore Team Size – 10 to 12
• Task Level distribution of work 5 Developers : 2 Testers : 1
Designer : 1 Proxy Product
• All Scrum Team members attend a single daily ‘Standup’ call
Owner : 1 Scrum Master
Total Onsite to Offshore ratio –
• Onsite team may hand over a complex User Story needing frequent
40 : 60
customer interaction to offshore team once complexities are
resolved
19
Model - 3
• Onsite and Offshore do not have a significant overlap And the total
project team size is less which does not allow splitting into multiple
Scrum team. Typical Team
Composition
Recommended Operating Model Scrum Team Size – 10 to
12
• Onsite and Offshore operate as one Scrum Team Onsite to Offshore ratio –
40:60
• Onsite & Offshore Scrum Team members must attend at least one 5 Developers : 2 Testers :
common daily ‘Standup’ call. 1 Designer : 1 Product
Owner : 1 Scrum Master
• Onsite team members should be assigned Tasks that require close
customer involvement
– Ensure overall release plan is in line with business requirements Product Owner
– Participates in requirements workshop, in case of tie-breakers between requirements in terms
of priority /value, make decisions with regards to requirements
– Define the user stories for the software, work with team to decide iteration schedules and
release plan
– Provide detailed and well groomed requirements along with acceptance criteria before the
start of every iteration.
– As and when required, before and after every iteration, prioritize requirements and keep
product backlog updated
Functional Consultant
23
Governance Mechanism
• There can be multiple scrum teams with different scrum masters. Each team member will attend
only one standup call, but there would be multiple standup calls.
• Usage of a Agile tool to capture everyday data and enforce discipline to update the tool on a daily
basis
• Have governing body over Scrum teams to monitor and guide day to day progress and bottle
necks. It can consists of Scrum masters, Program Mgr (Infy & Client), PO, Architects
• Like daily standup meetings, daily governing body meeting is suggested (this will check proper
update of ALM tool, any show stopper, effort burn rate analysis, scope creep etc..)
• Have playbook/cook book for quick onboarding of new resources. This should include
Introduction to Agile, Overview of the program, Overview of the epic, Program mile stones,
Scrum team structure etc..). Quick onboarding of new team member is highly critical
25
Communication
Estimation
27
• Release planning workshop (RPW) is held at the beginning of every quarter which will pipeline all
stories for the next Release. These stories will be segregated as per the existing Scrum team and
separate work out session will be conducted. Every story will picked up and PO explains the
requirement, acceptance criteria and then team will use voting system to estimate it. A
predefined series of days are provided 1,2,3,5,8,13…(Fibonacci series). Each team member to
pick the estimated date and this will be openly discussed in the workshop until the day is finally
agreed by all (estimation is in days). This will be updated in Rally then and there. PO s/Architects
will help you to validate, but estimation will be done in the call itself
• A typical RPW will be 4 days session (6hrs workshop everyday which can extend based on
progress you make). Normally it happens at onsite hours. Every team member physical presence
at office is mandated. Executed with Webex video call
28
• Pure term effort and people • Well defined scope • Fluctuating work load based
• Lots of unknowns. • IT & Business commitment for business needs
•Suitable for initial engagements successful delivery. • Feasible when the execution
where project team does not have • Controlled outcome and model is matured and proper data
much control over dependencies expectation points are available to define UoW
and SME support • High cost predictability **
• Delivery risk is shared between • Majority of delivery risk is with • Client pays for each service unit,
client and Infosys. Infosys. for the UoW produced.
•Caution points: Scope creep in any • Easier Change Request
form, Gold plating (giving more Management
than what is asked), resourcing • IT & Business commitment for
challenges, low team motivation successful delivery
levels are all risk towards Infosys
** Infosys will evaluate the maturity and the available data points after successful delivery of 2 sprints.
28
Agile Tools and Templates
(Specific to Oracle)
30
Sample Templates
DevOps in Oracle
34
Governance
Adaptive framework which Uplifting the capability of team by Creating DevOps strategy and
addresses key tenets of Iterative role based trainings , upskill team blueprint which will further
Way of Working in Sprints and with Tools training and facilitating accelerate Agility.
Key Levers
Change Management
36
• Clear requirements , better planning , effective tracking Reduced rework & gap
Iterative Way Of Working • Agile , Flexible & Collaborative work culture Deliver what is needed IT Cost
• Build , Test , Show & Tell , Feedback loops , Learn & Adapt Increased Visibility
Case Studies
38
Benefits of Agile
•Bridging the gap between distributed teams – •Staggered offshore working hours to ensure 2 hrs overlap
Customer team , Infosys Offshore with onsite hours.
Development. •Established multiple daily calls for project status - Usage of
tools like Net Meeting, Video Conferencing.
•Agile Offshore requires flexibility from both Customer and
Infosys Onshore teams to make it work.
•Communication enabling tools are highly recommended.
•Unproven methodology and hence likely to •Monitor these projects more closely with respect to
have more challenges than others project management and change management.
•An agile project needs to have a high level project plan as
well as a brief iteration level plan.
•Meeting the release dates •Tracking of each task on a daily basis.
•Daily Stand up meetings with onsite team.
•Tracking of issues
•Preferred overlapping shifts in GDM.
•Lack of scientific methods for estimation •Modified version of the iterative SMC estimation method
can also be used.
•Customizing the existing estimation methodologies to cater
to this need.
•Skill Set Maintenance •Good mix of resource skills to be maintained for all the
applicable technologies.
48
Operational Alignment
• Offshore will align their work schedule during the initial few months to ensure
time overlap of 2-3 hours
• Offshore will attend Iteration Planning and Retrospectives
• Frequent video conferences with offshore team to build a relationship
• Scheduled visits by the onsite client team to the offshore development center
49
Metrics
• Quality and Productivity metrics will be tailored to Agile BI approach and tracked for each
iteration
• Aggressive project schedule and effort tracking and reporting
• Executive reviews
50
• Selection and implementation of right tools for automation • Improving quality and reliability using automation
• Cost and correctness of automation • Measuring Automation benefits
51
Knowledge
Management DevOps IT Agility
51
52
Continuous Integration
Report Build
Failure
Continuous Delivery
Continuous Validation
Auto- trigger of Smoke Test scripts on Auto- trigger of System Tests on successful Auto- trigger of Performance Tests on
successful completion of Build deployment completion of Acceptance Tests. successful completion of System Tests.
Test Monitor
Results Results
PERFORMANCE TESTING
DEPLOYMENT TESTING BUILD ACCEPTANCE SYSTEM TESTING
TESTING
DEFECT MANAGEMENT
TOOL
Infra Models
Script Popular open source
Environment Hardware Stack
infrastructure automation tools
Environments
definitions Provision
Environments Physical include Chef, Puppet, CfEngine,
Infra
Manage scripts Bcfg2 etc.
(infra-as-code) testing
Virtual
Version Control
55
56
Project and Change & Architecture & Development Test & Defect Build, Deploy & Environment
Portfolio Requirement Design Management Release Management
Management Management BuildManagement
OpsHub or
Chef with VS Release Management 3 RC
Kovair omni bus
Chef with VMWare plugin
TFS As ALM
.NET Java SSIS BizTalk MDM
Code FXCop, Coverity, Visual Studio Coverity, Pragmatic Works - BizTalkCop
Quality tools - Static Code Analysis, SONARQUBE, Best Practices
Tools Code Metrics, Code Coverage & CheckStyle, Emma, Analyzer
Code Profiling, SONARQUBE, Clover for Code No Standard Tools
StyleCop Coverage
Unit NUnit, Visual Studio Unit Test Jtest, JUnit, ssisUnit, SSISTester BizUnit, BizMock
Testing Framework
End of Presentation