Adopting an Agile Approach for Siebel

Prepared by: EJM Associates

Typical situation for many Siebel customers

Challenged to balance Daily Operations with: Responsiveness to Backlog Responsiveness to Business imperatives Responsiveness to Changing Requirements Responsiveness to End User Demands Quality of Software Delivered Contains bugs Not what business wanted

Software Development Cycle Heavy on Documentation Takes too long to deliver

Our Recommendation
Adopt Agile Methodology with SCRUM Project Management Approach

Employ small team for initial use & fully transition to Agile
Use Backlog of enhancements & trouble tickets Use an experienced Team to ensure smooth transition and train internal staff.

Weve seen it work at other clientsSiemens Medical, Motorola and Others

Why Agile Methodology?

Shortens delivery cycle providing more flexibility to re-prioritize and adapt to hot change requests Better aligns business with technical delivery Improved quality of deliverables testing throughout / earlier vs. at the end

Simplified Project Management Approach Incremental, iterative & collaborative, rather than distinct stages

Agile Benefits
Results from various surveys with percentage of respondents citing improvements in productivity, quality, and costs

Agile Methodology Key Characteristics

Short, fixed length Sprints resulting in working, testing & accepted software
Value-Driven Development based on business prioritization Continuous & Adaptive Planning Relative Estimation of each Backlog Item Emergent Feature Discovery vs. Detailed Requirement Specifications

Continuous Testing
Continuous Improvement Cross-functional Teams
6

Agile Methodology Overview .

SPRINT
Analysis
Collect Details Discuss with SME Analysis and Initial Design

Design
Create Use Case

Finalize Design with Technical Team

Design Review with SME

Develop
Build Demo with SME

Test
Create Test Plan

Create Test Labs

Test Execution
Execute Test Labs Resolve Defects

Complete
Update Production Task List Complete/Update Functional Specification

Doneness Check Complete

7

Case Study: Siemens Medical

Implemented 2 years ago

Why? Never Ending Projects Missed Requirements Management & the business unit found IT to be too inflexible and not responsive to changing business needs ITs existing Water-fall Methodology & Approach was Too rigid Relied heavily on documentation Resisted change even if the path they were going down was wrong or misaligned.

Case Study: Siemens Medical (Continued) The Results.

High Customer Contact and Satisfaction Deliver more in less time Continue to Increase Velocity through reuse and improved practices Rapid response to Business changes and Business Priorities Flexibility Reduced Defects

Why does the Business like it?

We Get what we want !!!
9

Our Getting Started Approach

Use a blended team comprised of our resources with Agile/Siebel experience and your internal resources. Get Backlog Prioritized & Estimated

Define SPRINT time-box & work packet Execute SPRINT 1

Revisit & Refine Execute SPRINT 2 Evaluate & Adjust to institutionalize Agile Approach

10

Why EJM Associates?

We have over 10 years of Siebel implementation & support experience Our experience spans more than 50 different customers in numerous industries including:
Health Sciences (Pharma / Clinical / Medical Devices) Finance & Insurance Consumer Goods / Retail Media Telecom Technology

We have successfully delivered:

Initial Phase 1 implementations Upgrades Enhancements Managed support services

We have experience with offsite & hybrid teams

11