Agile Development and Quality process Date of presenting

(11th feb,2008)

Software Development Process 1. 2. 3. 4. 5. 6. 7. Information gathering Analysis Designing Development Testing Release Maintenance

A simple example«.
1. 2. 3. 4. 5. 6. 7. Getup from bed Have bed coffee Toilet Brush Bath Have Breakfast 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 Duration ~ 1-3 days/DN

NIT

NIT Review Workshop Design & Dev QG-3 & QG-2 Test
Release

Design Workshop
Participants ‡NIT Team* ‡Network Design Team ‡PM ‡Development Lead* ‡Design Team ‡QA (only last day of the workshop) ‡Test Lead*

QG-1

Design & Development

UAT

Test

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 collocated in a room and offshore participated through Video Conference/Net Meeting.

Each Document owner to guaranty that their document is up-to-date during each QG¶s

Entry Criteria

NIT

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

Design Workshop

QG-1

Design & Development

UAT

VV&T
Exit Criteria

DESIGN ‡NIT Config Process (Visio's) ‡Design ‡Estimation Calculation ‡Naming Convention Document ‡Screen Mock-ups (from Draft DN)

QUALITY GATE ACTIVITIES - DESIGN Aim ± To ensure that minimum documents are in place to start development and also ensuring the understanding of design by Development Lead. 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 ‡Failures captured in Bugzilla ‡Design & Development starts based on Config process (Visio's). ‡Iterating it based on NIT/VV&T Test results/Issues & Updates DN ‡VV&T tests based on draft test spec and raises issues if any. ‡Updates Test Spec with new CR. Design, Dev, and VV&T sharing same DN and keep on updating it as it changes using and Bugzilla for Issue tracking

NIT

NIT Review Workshop Design & Dev QG-3 & QG-2 Test
Release

Design Workshop

QG-1

Design & Development

UAT

Wait time to 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) between Dev lead, NIT and Testing. Daily Scrum calls between these teams to be arranged by PM or Scrum master

Test

Regular (2 weeks) demo/feedback sessions with entire workshop team during the development phase and any CR¶s will be captured and modifies DN/Config Guide. Design lead 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 Workshop Design & Dev QG-3 & QG-2 VV&T
Release

Design Workshop

QG-1

Design & Development

UAT

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, ASG, VV&T

VV&T

P1 ± Priority 1 Bugs P2 ± Priority 2 Bugs

Quality Gate -2 ± Release 0

‡Review Workshop completed in the presence of all stakeholders
Entry Criteria

NIT

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

Design Workshop

QG-1

Design & Development

UAT

VV&T

Exit Criteria

QUALITY GATE ACTIVITIES ± RELEASE 0 Aim ± To freeze the Requirements and to get written user sign-off on requirements. Responsible person ± PM

‡Demo of features to Client and Requirements (detailing scope and out-of-scope) Sign-Off ‡Draft Test Cases & Test Spec prepared by VV&T ‡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 Workshop Design & Dev QG-3 & QG-2 VV&T
Release

Design Workshop

QG-1

Design & Development

UAT

VV&T

Any change in design should be updated in DN and must come from design team

Exit Criteria

QUALITY GATE ACTIVITIES ± RELEASE 1 Aim ± To forward the build to Quality Assurance stage and freeze development , VV&T and NIT Responsible person ± PM

‡Final Test Results & Test Spec by VV&T ‡Final DN ‡Final Visio ‡Demo to 3rd line support and ASG ‡Draft QA Test Spec

Quality Assurance and Release

NIT

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

Design Workshop

QG-1

Design & Development

UAT

VV&T

Exit Criteria

UAT QUALITY ASSURANCE ACTIVITIES Aim ± To forward the Build from VV&T stage to User Acceptance stage. Responsible person ± QA Manager to arrange the review and invite stake holders Participants QA Representatives VV&T Lead. ‡Test Spec & Results ‡Sign off from Acceptance Test Manager

Agile Development Process ± E to E
‡Client requirement stacked in Caliber and NIT Decides which ones to be developed in Agile ‡Defined and Documented CR exists. ‡Project Manager ensures that PM Plan aligns with Agile Dev: Process ‡Domain Experts, Solution, NIT Team, Development Lead, QA and Test Leads have been identified ‡A stable Network Design exists &Service Solution Design exists. Entry Criteria

‡NIT does manual Configuring based on Config Process & also tests configs from development ‡Failures captured as Issues ‡Design & Development starts based on Config process (Visio's). ‡Iterating it based on NIT/VV&T Test results/Issues & Updates DN ‡VV&T tests based on draft test spec and raises issues if any. ‡Updates Test Spec with new CR.

NIT, Design, Dev, and VV&T sharing same DN and keep on updating it as it changes using VSS or Live Link

NIT

NIT Review Workshop Design & Dev QG-3 & QG-2 VV&T UAT QG2-DEVELOPMENT± R 0
Sign-off from the client on the requirements and freezing it. Sign off from Acceptance Test Manager Release

Design Workshop

QG-1

Design & Development

UAT

Wait time to start VVT

VV&T

Exit Criteria

QG1-DESIGN
Ensures Configs (Visio¶s) are available for development

DESIGN
The workshop members brainstorms on the design and prepares first draft of Design ± in the form of Configs (Visios)

QG3-DEVELOPMENT ± R 1 REVIEW WORKSHOP
First cut Development of DN to be demonstrated to the client. Completion of development and VV&T. Final Build, DN, Detailed Design, Test spec and Test cases are ready for UAT

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

Sign up to vote on this title
UsefulNot useful