Software Projects Delivery Process

1
Software Projects Delivery Process Mrinal
Bhasker 12/17/07
2
Need

• A lightweight and efficient delivery process that
  is customized to our unique needs to improve
• Client Satisfaction
• Predictability
• Resources
• Budget
• Timelines
• Repeatability
• Trackability
• Improvability

3
Uniqueness of our environment

• Work with an off-shore development team
• Cross-company challenges
• Cultural challenges
• Time zone challenges
• Smaller projects, shorter and aggressive
  timelines
• A lot of web projects
• Short on onsite technical staff

4
Regular SDLC Steps
SDLC Software Development Life Cycle
5
AIs Development Process Model
Client
AI
OSD
Vision and Scope
Functional Spec
Project Plan
Detailed Design
Test Plan
High Level Design
Review and Start next Phase, if required
Develop
Test
Code Review Verification
UAT
Deployment
Business Analyst/PM
Developer
OSD Offshore Development Team
Process Flow Direction
UAT User Acceptance Testing
Sent for review
Architect
Tester
6
Process Components

• Process Model
• Phases
• Stages
• Checkpoints
• Deliverables
• Project Roles and Responsibilities
• Tools
• Communication Protocol

7
Phased approach to bigger projects

• Split bigger projects into smaller phases
• Involve the client in all the phases
• take feedback
• Repeat the Process Model for all phases

8
Stages

• Envision
• Spec Plan
• Design
• Build
• AI QA
• UAT
• Deploy
• Review

9
Delivery Roadmap
Continued on to the next page..
Checkpoint
10
Delivery Roadmap (contd.)
Checkpoint
11
Roles and Responsibilities
12
Tools
13
Communication Model
OSD
AI
As needed
Daily communications
Client
Continuous Communication
Continuous Communication
JIRA
14
Closing

• One process model for all projects, to keep
  things simple.
• If you think the process or a part of it cant be
  applied to your project, fake it.
• Effective use of the Issue Tracking System (JIRA,
  in our case) is your road to success. Period.