Agile Development and Quality process

Date of presenting
(11th feb,2008)
 Software Development Process

1. Information gathering
2. Analysis
3. Designing
4. Development
5. Testing
6. Release
7. Maintenance
 A simple example….
1. Getup from bed
2. Have bed coffee
3. Toilet
4. Brush
5. Bath
6. Have Breakfast
7. Go to office
 Principles of Agile manifesto
• Satisfy the customer through early and continuous
delivery of valuable software
• Welcomes changing requirements,even late in
development
• Deliver working software frequently,from a couple of
weeks to couple of months.
• Business people and developers must work together
daily throughout the project.
• Face to Face conversation with Team members.
• At regular intervals,team reflects on how to become
more effective, turns and adjusts its behavior accordingly
Phase -1 - Design Workshop
•Client requirement stacked in Caliber and NIT Decides which ones to be
developed in Agile – GS Lead co-ordinates it.
•Defined and Documented Customer Requirements
•Project Manager ensures that Project Plan aligns with Agile Dev: Process
•Domain Experts, Solution, NIT Team, Development Lead, QA and Test
Leads have been identified
•A stable Network Design.

Entry Criteria
NIT NIT
Duration ~ 1-3 days/DN
Review
QG-1 Workshop Release
Design Workshop Design & Development Design & Dev QG-3 UAT
&
QG-2
Participants Test Test

•NIT Team*
•Network Design Team
•PM
•Development Lead*
•Design Team
•QA (only last day of the workshop)
•Test Lead* DESIGN WORKSHOP ACTIVITIES

Aim – Workshop members collocated in the same

room brainstorms on the design and prepares first
draft of Config guides – in the form of Visio’s.

During the Scoping stage, if it is found there is a technical or architectural

dependency of any other DN for the development of this DN, a decision
should be taken immediately by the PM to take this out of Agile development.
Quality Gate -1 - Design

The Workshop concluded with all members

Each Document owner to guaranty that their
collocated in a room and offshore participated
document is up-to-date during each QG’s
through Video Conference/Net Meeting.

Entry Criteria

NIT NIT
Review
QG-1 Workshop Release
Design Workshop Design & Development Design & Dev QG-3 UAT
&
QG-2
VV&T VV&T

Exit Criteria

DESIGN QUALITY GATE ACTIVITIES - DESIGN

•NIT Config Process (Visio's)
Aim – To ensure that minimum documents are in
•Design
place to start development and also ensuring the
•Estimation Calculation
understanding of design by Development Lead.
•Naming Convention Document
•Screen Mock-ups (from Draft DN)
Responsible person – Design Lead
Phase 2 – Design/Development/VV&T •NIT does manual Configuring
based on Config Process & also
tests the configs send from the
development Design, Dev, and
•Failures captured in Bugzilla VV&T sharing same
•Design & Development starts based DN and keep on
on Config process (Visio's). updating it as it changes
•Iterating it based on NIT/VV&T Test using and Bugzilla for
results/Issues & Updates DN Issue tracking

•VV&T tests based on draft test spec

and raises issues if any.
•Updates Test Spec with new CR.

NIT NIT
Review
QG-1 Workshop Release
Design Workshop Design & Development Design & Dev QG-3 UAT
&
QG-2
Wait time to Test Test
start VV&T

First Drop to Test from

Development.
VV&T To be ready with
test Spec based on
Draft DN

Continuous Agile working (Close interaction) Regular (2 weeks) demo/feedback sessions with entire
between Dev lead, NIT and Testing. Daily Scrum workshop team during the development phase and any CR’s
calls between these teams to be arranged by PM or will be captured and modifies DN/Config Guide. Design lead
Scrum master organizes this call.
Development - Review Session

•Development ready for the first release of DN with 90-95%

•NIT Completed testing the configs
•Unit test and VV&T completed with no P1 & P2 remaining

Entry Criteria

NIT NIT
Review
QG-1 Workshop Release
Design Workshop Design & Development Design & Dev QG-3 UAT
&
QG-2
VV&T VV&T
REVIEW ACTIVITIES

Aim – To get all stake holders in Design Workshop

again and to review the design and development
(using Net Meeting). Demo will be given to the user
and in case of any minor change requests that
does not involve Visio changes, will be
incorporated. No more CRs will be taken from this
point

Organized by – Delivery Manager

Demo given by – Development Lead
Participants - User Representative
Network Designers, NIT,
Design & Development Lead, P1 – Priority 1 Bugs
ASG, VV&T P2 – Priority 2 Bugs
Quality Gate -2 – Release 0

•Review Workshop completed in the

presence of all stakeholders

Entry Criteria

NIT NIT
Review
QG-1 Workshop Release
Design Workshop Design & Development Design & Dev QG-3 UAT
&
QG-2
VV&T VV&T

Exit Criteria
QUALITY GATE ACTIVITIES – RELEASE 0

Aim – To freeze the Requirements and to get

•Demo of features to Client and Requirements (detailing written user sign-off on requirements.
scope and out-of-scope) Sign-Off
•Draft Test Cases & Test Spec prepared by VV&T Responsible person – PM
•Draft DN – updated taking user inputs during review
Quality Gate -3 – Release 1

•Development ready for final release of features

•Development incorporated all CR’s raised by the client during
R0 and Visio & DN is updated
•NIT Completed testing all the configs
•Unit Test and VV&T completed on all test cases with no P1/P2

Entry Criteria

NIT NIT
Review
QG-1 Workshop Release
Design Workshop Design & Development Design & Dev QG-3 UAT
&
QG-2
VV&T VV&T

Any change in design should be updated in Exit Criteria

DN and must come from design team

QUALITY GATE ACTIVITIES – RELEASE 1

•Final Test Results & Test Spec by VV&T
•Final DN
Aim – To forward the build to Quality Assurance
•Final Visio
stage and freeze development , VV&T and NIT
•Demo to 3rd line support and ASG
•Draft QA Test Spec
Responsible person – PM
Quality Assurance and Release

NIT NIT
Review
QG-1 Workshop Release
Design Workshop Design & Development Design & Dev QG-3 UAT
&
QG-2
VV&T VV&T Exit Criteria

UAT

QUALITY ASSURANCE ACTIVITIES •Test Spec & Results

•Sign off from Acceptance
Aim – To forward the Build from VV&T stage to Test Manager
User Acceptance stage.

Responsible person – QA Manager to arrange the

review and invite stake holders

Participants - QA Representatives
VV&T Lead.
Agile Development Process – E to E •NIT does manual Configuring
•Client requirement stacked in Caliber and NIT Decides which based on Config Process & also
ones to be developed in Agile tests configs from development
•Failures captured as Issues NIT, Design, Dev, and
•Defined and Documented CR exists.
VV&T sharing same
•Project Manager ensures that PM Plan aligns with Agile Dev: •Design & Development starts based DN and keep on
Process on Config process (Visio's). updating it as it changes
•Iterating it based on NIT/VV&T Test using VSS or Live Link
•Domain Experts, Solution, NIT Team, Development Lead, QA results/Issues & Updates DN
and Test Leads have been identified
•A stable Network Design exists &Service Solution Design •VV&T tests based on draft test spec
exists. and raises issues if any.
•Updates Test Spec with new CR.

Entry Criteria

NIT NIT
Review
QG-1 Workshop Release
Design Workshop Design & Development Design & Dev QG-3 UAT
&
QG-2
Wait time to VV&T VV&T Exit Criteria
start VVT
UAT

Sign off from Acceptance Test

QG1-DESIGN QG2-DEVELOPMENT– R 0 Manager

Ensures Configs (Visio’s) are available Sign-off from the client on the
for development requirements and freezing it.
QG3-DEVELOPMENT – R 1
DESIGN
Completion of development and
The workshop members brainstorms
REVIEW WORKSHOP VV&T. Final Build, DN, Detailed
on the design and prepares first draft
Design, Test spec and Test
of Design – in the form of Configs
First cut Development of DN to cases are ready for UAT
(Visios)
be demonstrated to the client.
 To implement Agile process..
• The culture of the organization must be
supportive of negotiation.
• People must be trusted.
• Fewer but more competent people.
• Organizations must live with the decisions
developers make.
• Need to have an environment that facilities
rapid communication b/w team members.
 Thank you

Please send your feedback