This action might not be possible to undo. Are you sure you want to continue?
This example is from my book Software Project Management in Practice (2002, Addison Wesley).The project planning here follows the methods and style of the parent company, some of which have been discussed in the Chapter. The plan here does not give the CM plan or the detailed schedule of project tasks – more on these are available in the book. How the plan was evolved and the methods followed for it are also given in the book. PROJECT MANAGEMENT PLAN FOR ACIC PROJECT 1. PROJECT SUMMARY
1.1 Project Overview ACIC is a USA-based Investment firm. This application has 2 components. First, a Brokerage Account Opening application on ACIC’s web-site which will allow any Internet user to open a Brokerage Account with ACIC. Second, an account opening and maintenance application which is primarily for ACIC’s representatives to open accounts for the applications received in Paper format. This is an Intranet application. The application will provide features like account history viewing and account balance, status and activity information. This will allow ACIC to effectively evolve to a client/account servicing application in addition to being an account opening engine. This is an enhancement of an existing application; the earlier development was also done by Infosys.
Project code xxxxxxxxx Project Leader(PL) BB Project Type Development
Project Name ACIC Project Configuration Controller( CC) SB
Customer ACIC Corporation Business Manager(BM) HR Platform Java, Win NT, DB2 Project end date Nov 3rd, 2000 Backup PL BS Backup CC HP Number of Phases Four Phases. Total Estimated Revenue US $ xxx,xxx
Project Start Date (including onsite, offshore) On-site Off-shore April 3rd, 2000 May 15th, 2000
Name and Designation
Project and Customer Contact Personnel Phone Fax number E-mail id. number
efficient means of account maintenance activities To allow reps to access information. Deployment plan for the product Test Plans. and trade activity Increase the intelligence of the update process Provide an interface that is able to display required account history elements Provide capability to close and reactivate an account Project's Value-add to the customer This project will allow ACIC to effectively evolve to a client account servicing application in addition to being the account opening engine. Source code. Iteration plan for the next cycle Source Code. Use-Case catalog. Class diagram. Iteration plan for the next cycle Source Code. Class diagram. Plan for the next cycle Supplementary specifications. Iteration plan for the next cycle Source code. Architecture document. Iteration plan Sequence diagrams. valuation. Infosys Objectives Strengthen relationship with ACIC by delivering high quality software on time. Iteration plan for the next cycle. Review reports. 10. Screens. 1. Test reports Code Test reports Code 2 3 4 5 6 7 8 9. Sequence diagrams. Review reports. order status.2 Commitments made to the customer Sl# 1 Milestone Date 26th May 2000 15th May – 23rd June 2000 26th June – 7th July 2000 10th July – 21st July 2000 20th July – 28th July 2000 31st July – 8th Aug 2000 9th Aug – 1st Sep 2000 4th Sep – 15th Sep 2000 18th Sep – 22nd Sep 2000 18th Sep – 29th Sep Milestones Inception: Requirements Signoff Elaboration: Iteration-1 Elaboration: Iteration-2 Construction: Iteration-1 Construction: Iteration-2 Construction: Iteration-3 Integration Testing Phase Onsite Code delivery and setup Acceptance Test and Production migration Onsite Reconciliation Deliverables Business analysis and requirements specifications.Project Scope To provide an effective. . Become preferred vendor by developing expertise on their products and systems. Test reports. Test reports. Review reports. Provide a complete picture to the client rep for account status. Test reports. Source code.
2000 11. Any impact on cost or schedule due to these changes will be intimated to ACIC ACIC reviewers will get 7 days to approve a milestone document.1 Project Processes Standard Process followed The standard development process of Infosys will be followed.0 will not be done by this team Intelligent update to business partners will be incorporated in only the maintenance part of the application and not in the ‘Account opening’ engine Qualified people will approve ‘Rational Unified Process’ methodology for implementing this project Changes in functional and technical requirements during the life cycle of the project may have an impact on the schedule. If no comments are received within this time period. However. it will be enhanced with Rational Unified Process methodology (RUP). Development of logical object Added/Modified/Deleted Modified Reasons for deviations As iteration based development is being done Modified Conformance to RUP . 2th Oct– 26th Oct 2000 27th Oct – 3rd Nov 2000 and Regression Test Acceptance Test Roll out Support and Test Results Project Sign off Other commitments Sl# 1 Commitments This project will follow the Rational Unified Methodology (RUP). as it is a commitment. PROJECT PLANNING 2. Tailoring Notes Deviations from standard process Only those use cases that are going to be taken up in a particular iteration will be elaborated at that point of time.3 Assumptions Assumptions made while planning Migration to Visual Age for Java 3. The development process will be tailored to match the RUP. it will be considered as approved. 1. 12. • • • • • 2.
re-estimation of the project schedule and effort will be done. A change request form will be submitted to customer for approval. if any one or a group of change requests takes more than 2% of the total estimated effort for the project.2 Estimated Size and Effort Estimation Criteria Program/Function ( Use Case ) Simple Use Case Medium Use Case Complex Use Case Use Case Criteria 3 or Fewer Transactions 4 to 7 Transactions > 7 Transactions Description Complexity .xls and analyzed for impact on the project. As this is a short duration project. Major changes usually have an effort / delivery-on-time impact on the project. The customer needs to formally approve these. as we started with the ‘Scope document’ which serves the same purpose methodology Modified Conformance methodology to RUP Modified Modified Modified Modified Modified Conformance to RUP methodology As iterative approach is being used As iterative approach is being used Conformance to RUP methodology Deviation from RUP Requirements Change Management Process Change Requests Tracking • • • Changes requested by customer will be logged in ChangeRequest. Requirements Traceability Requisite Pro tool will be used. Change requests that are approved will be attached to the project contract as addenda. 2.model will be done incrementally in the first few iterations Development of physical object model will be done incrementally in the first few iterations Physical database design may be refined in later iterations Development of unit test plan will be done in each iteration Logging of defects will be iteration wise Requirement traceability will be done through the Requisite Pro tool No vision document and Business case.
Number Use Case 1 Use Case 2 Use Case 3 Use Case 4 Use Case 5 Use Case 6 Use Case 7 Use Case 8 Use Case 9 Use Case 10 Use Case 11 Use Case 12 Use Case 13 Use Case 14 Use Case 15 Use Case 16 Use Case 17 Use Case 18 Use Case 19 Use Case 20 Use Case 21 Use Case 22 Use Case 23 Use Case 24 Use Case 25 Use Case 26 Screen Navigation Update Personal Details Add Address Update Address Delete Address Add Telephone Number Update Telephone Number Delete Telephone Number Add Email Update Email Delete Email Update Employment Details of a party Update Financial Details of a party Update Details of an Account Maintain activities of an Account Maintain memos of an Account View History of Party Details View History of Account Details View History of Option Level and Service Options View History of Activities and Memos View History of Roles View Account Details View Holdings of an Account View ‘Pending Orders’ of an Account Close/Reactivate Account Intelligent update to business partner of ACIC Complex Medium Medium Complex Complex Medium Complex Complex Medium Medium Medium Medium Medium Medium Complex Simple Complex Complex Simple Simple Complex Simple Complex Complex Simple Complex Estimated Build Effort Program/Function Simple Use Cases Medium Use Cases Complex Use Cases TOTAL Effort (Based on data from earlier project) 1 Person Days 5 Person Days 8 Person Days Number Units 5 9 12 of Total Build Effort (in person-days) 5 45 96 146 Phase-wise Effort Estimate Activity/Phase Requirements Design Build Integration test Regression Test Acceptance test Project management Configuration management Training Others Person-days 50 60 146 35 10 30 75 16 50 40 % of total effort 10 12 29 7 2 6 15 3 10 6 .
2.5) Date 4th May 2000 4th May 2000 15th May 2000 15th May 2000 17th July 2000 1st August 2000 14th August 2000 Area Java DB2 Total People by Skill and Experience Total # 0-12 months experience 7 7 2 0 9 7 People Requirement Plan > 12 months experience 0 2 2 Month May 2000 June 2000 Offshore 4 5 Onsite 1 (50%) 1 Total 5 6 .Estimated Effort Effort Estimate by Iterations 501 Person days 100% % of Effort 5 5 9 7 5 5 4 22 2 15 3 10 8 100% Total Project Initiation Inception Phase Elaboration Phase: Iteration-1 Elaboration Phase: Iteration-2 Construction Phase: Iteration-1 Construction Phase: Iteration-2 Construction Phase: Iteration-3 Transition Phase Project Closure Project Management Configuration Management Training Others Total Estimated Effort 25 24 45 34 27 24 21 110 10 75 16 50 40 501 Person Days 2.4 People Role PL Onsite Co-ordinator Module Leader Developers Developers Developers Developers Total People by Role Required# 1 1 ( 50% time ) 1 3 1 1 1 9 (actually 8.3 Schedule Specified as milestones in the section on Commitments to the Customer.
July 2000 Aug 2000 Sep 2000 Oct 2000 5 8 7 3 1 1 2 2 6 9 9 5 2.7 Tools Tools List Tools to be developed in the project None In-house tools to be used in the project None 2. Java. Win NT 2.6 Hardware and Software Resources Required Item Description PCs with 128 RAM 1 GB space on server Visual Age for Java DB2 Rational Rose Requisite Pro Required # 6 1 6 6 5 1 Date 1st May 2000 1st May 2000 4th May 2000 4th May 2000 15th May 2000 15th May 2000 2. For others on the job training If already trained .8 Training Plan Training Area Technical Java Language Visual Age for Java Java Applets Java Swing Persistence Builder Rational Rose and Requisite Pro OOAD Business domain System Appreciation Process Related Quality system Configuration Management Group Review Duration 7 days 3days 4 hrs 4 hrs 4 hrs 8 hrs 1day 7 days 3 hrs 2 hrs 4 hrs • • • • • • Waiver Criteria If already trained Exposed as part of initial training If already trained If already trained If already trained Mandatory • If already trained • If already trained • • • If already trained If already trained for CC.5 Development Environment Hardware • NT Server • MainFrame • Intel PC Software • WIN NT • DB2 • Visual Age for Java.
Defect prevention SPC tool RUP methodology 4. 6% estimated number defects 50 10% 32% of of (Acceptance defect 5 Productivity Schedule Cost of quality (In %) 57 Delivery on time 32% Estimates of defects to be detected Review / Testing stage Requirements & Design review Code review Unit testing Integration + Regression testing Acceptance Test Total estimated number of defects to be detected Estimated number of defects to be detected 29 % of defects to be detected 20% Basis for estimation Referenced similar Project estimations (Synergy 1.4 % productivity improvement to Synergy 1.9 Quality Plan Quality Goals Goals Total number injected Quality density) of defects Project Quality Goals Value Basis for setting goals 145 0.wide Norms 0. Group Review of Program specs for first few/logically complex Use Cases Expected benefits 10 -20 % reduction in defect injection rate and about 2% improvement in productivity Improvement in quality as overall defect removal efficiency will improve.5 31.5 hrs 2 hrs • • • Mandatory If already trained Mandatory 2. This is 10% better than Synergy 1.052 defects/Person Hour.036 defects/Person Hour 3 % or less of total estimated number of defects 3.033 defects/Person hour.5 hrs 4. use standards developed in synergy for coding.5) and PCB -Do-Do–Do-Do- 29 57 25 5 143 20% 40% 17% 3% 100% Strategy for meeting Quality Goals Strategy Do defect prevention using the standard defect prevention guidelines and process. some benefits in .5% Org. which is 0.5.
Milestone analysis and defect prevention exercise will be done after each Iteration. Test Cases. the understanding of the team may not be complete 0.10 Risk Management Plan Sl # 1 Risks Proba bility 0. Approximately 5 % reduction in defect injection rate and 1% improvement in overall productivity Type of review Group Review SQA Review SQA Review Group Review Group Review Group Review One person review Group Review Group Review One person review One person review Group Review Project Plan DCS set up Project Schedule CM Plan Business analysis and requirements specification document. Introduction of RUP methodology and implementing the project in iterations. Interactive diagrams Code Code Unit Test Plan Integration Test Plan Risk Expo sure 4 Mitigation Plan Support from database architect and the database administrator of the customer • • 2 As RUP is being used for the first time. Use Case Catalog Design Document.5 Imp act 8 Review Item productivity as defects will be detected early. Reviews Review Point End of Project Planning End of Project Planning End of 90% of Requirements ( This should be at the end of First Elaboration Iteration ) End of 90% Design ( This should be at the end of Second Elaboration Iteration ) Beginning of each Iteration End of Detailed design After coding for first few programs After self testing of a process End of Unit Test Plan Beginning of Integration Test 2.7 • • Plan carefully for the time required from each of this groups and give enough prior notice Onsite co-ordinator to work closely with these groups Work closely with experts in the R&D lab of Infosys Keep the customer in the loop throughout the project and escalate for any Schedule/Effort deviations .Group review of design docs/first timegenerated code by Project Leader. Object Model Iteration Plans Complex/first time generated Program Specs incl.9 3 2. Developer and one Consultant.
Daily When Escalated 2 days . desk checking etc.1 Measurement Plan Metric to be collected Size Effort Defects Schedule Unit of Measurement LOC .8 • • Train the team on RUP methodology Assign tasks so that more than one person is aware of the units/use cases in the project Do extra code reviews. Working with customer’s mainframe DB2 over the link – link may not be as efficient as it is expected. 0.3 Issues Tracking Issues Types Onsite Issues Where logged IssueTracker. • Once a week. • Task tracking is done daily.3 7 2. the tasks will show in their respective WARs. FP. PROJECT TRACKING 3. when PL.xl s Who can log Any member of the project Who reviews.• 3 Personnel Attrition: Team members might leave at short notice. • • • • After every iteration 3. 3. Once the Schedule is uploaded to WAR-MSP system.1 • 4 0.2 Task Tracking Activity Task scheduling Task assignment Task status tracking Project meeting Causal analysis meeting Procedure The PL schedules tasks using MS Project Refinement and rescheduling will be done when necessary The latest schedule is made available to the team members.1 8 0. S/M/C count Person-days Number of Defects Elapsed time • • • • Tools used Line counters WAR BugsBunny MSP 3. to minimize the reliance on link Escalate as soon as the link goes down.
Item for review Schedule Project plan Milestone report Frequency of review Every version change When some significant changes are made End of milestones 3. Daily 2 days 5 days 2 days 3.5 Quality Tracking Quality Activity Defect tracking Reviews (requirements. • Customer complaints received will be entered and tracked using CustomerComplaints. The BM files it.xls 3. high level design. Daily BM.7 Status Reporting Report To Business Manager Customer 3. 2. PL Weekly Support Services.4 Customer Feedback Item Customer Feedback Customer Complaints Logging and Tracking Process • The AM/PL gets the customer feedback.Customer Issues Business Manager Issues Issues with Support Services Issues Log. detailed design) Code review Independent unit testing Integration testing/System testing Action Use DCS for logging defects and tracking them to closure Check against project goals in quality plan Check against limits for each program through SPC tool Check against limits for each program through SPC tool Check against project goals in quality plan 3. 3. PL BM Any team member PL.8 Deviation Limits at Milestones Actual vs estimated of: Effort Schedule For the first five milestones 10% 10% For the rest of the milestones 5% 5% Frequency Weekly on Monday by e-mail Weekly on Monday .xls Weekly Status report Request Tracker Onsite team.6 Review by Senior Management (BM) Sl# 1.
11 Escalation Procedures Escalate Where At ACIC At Infosys At Infosys Threshold period 3 days 3 days 3 days Name of person Xxxx Xxxx Xxxx the Designation of person Project Manager Account Manager Business Manager the 4. if any Number of Requirement changes and estimated effort for them Major changes in Plan 3.Defects 20% 20% 3. if any 3.1 Project Organization Customer AM BM (Offshore) PM SQA DP Team ML CC DV .10 Report to the BM • • • • • • Customer feedback Milestones and weekly status reports Issues requiring clarifications/attention Escalation.9 Report to the Customer • • • Milestones reports and weekly status reports Issues requiring clarifications Escalation. PROJECT TEAM 4.
# 1 2 3 4 5 6 7 8 9 10 11 12 Initials BB KP BS SP DD HP NA SH AL JP SDS SB Responsibility Project manager Onsite Co-ordinator Module leader.2 Project Team . Sl.3 Roles and Responsibilities Role Business Manager (BM) Customer Responsibilities Resolve escalated issues Review project status Participate in critical technical reviews Review design Resolve escalated issues Acceptance test planning & testing Customer satisfaction Business growth Project financial plan Interfacing with sales and marketing Training related issues Employee related issues Project planning & scheduling Design Customer interaction Reviews Testing Reporting Task assignment & tracking Interact with software quality advisor from SEPG Ensure delivery as per contract Interface with other departments as per need Ensure open issues/customer complaints are closed properly Ensure project members are adequately trained Design Development Account Manager (AM) Project manager (PM) Module leader (ML) . backup project lead Configuration controller Developer Developer. backup configuration controller Developer Developer Developer Developer Account manager SQA Start date 4th April 2000 4th April 2000 15th May 2000 22nd May 2000 22nd May 2000 22nd May 2000 17th July 2000 1st August 2000 14th August 2000 1st September 2000 4th April 2000 15th May 2000 Expected End Date 3rd November 2000 3rd November 2000 3rd November 2000 13th October 2000 29th September 2000 29th September 2000 3rd November 2000 15th September 2000 31st August 2000 22nd September 2000 3rd November 2000 3rd November 2000 4.4.
Testing Reporting Defect prevention team (DP Team) Developer (DV) Configuration controller (CC) Software quality advisor (SQA) – from the SEPG Onsite Co-ordinator Spread awareness in the team on defects and their prevention Analyze defect data Identify methods to reduce defect injection Detail design for use cases Development Unit Testing & integration testing Prepare the CM plan Manage the configuration as per the CM plan Process consultancy Quality assurance (audits) Install measurement tools & train project personnel Participate in reviews of project Plan & processes as necessary Resolve any issues from Customer/Offshore Support during development 5. 6. . REFERENCES Omitted. ABBREVIATIONS USED Ommitted.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.