Project Management

Assumptions
MRP II for MIS and then chose components that we can sell Assuming stores and maintenance are not related we start with stores first Since it is a new project allow clearly stated the number of iterations and man-hours over and above which they will be charged

Work Breakdown/Schedules
May
Requirement Gathering for Planning, Marketing and Stores Sandeep learns JSP and starts experimenting the code Contingency plans are discussed with the clients and recovery sites are setup In last week of may programmers are recruited

 June
Specifications need to be approved by the client by the end of 1st week Assuming specifications are completed in May, low level designing starts in June for all 3 modules Sandeep starts developing Beans for the modules Policies are made so as to use the Beans created by Sandeep in the codes by all the programmers Programmers are given training while the low level designs are prepared by the Pls Coding begins for Planning and production module and Marketing modules New MCAs are recruited

 July
New MCAs are given exercises to test their ability Timely reviews are done for the codes of Planning and Marketing module Implementation and testing taking place simultaneously as per the codes developed UAT testing done by the clients and signoffs are taken as and when the patches are applied Low level design is prepared for the Stores module

 August(1st and 2nd week)

Planning and Marketing modules come to completion and final review and testing is done before the final signoff meeting in 1st week Signoff meeting is done and the changes are implemented in a couple of days The final signoff is taken in the 2nd week for planning and Marketing modules

 August (3rd and 4th week)

New MCAs are allotted to the store module Coding, testing and implementation are carried out for store module Timely review is done for the code UAT testing and signoffs for implemented modules are done by client Requirement gathering begins for Maintenance module in the final week

 September (1st and 2nd week)

Signoff meeting for specification of Maintenance module Changes to be incorporated in Maintenance module Signoffs on specifications after changes Low level design is prepared for mainteinance module and coding begins after the low level design is approved

 September (3rd and 4th week)

Testing and implementation of Stores module is completed Final review and testing is done Signoff meeting is held Suggested changes are made Final signoff is taken

 October
Coding, Implementation and testing for maintenance module is done UAT testing is done by the client and signoff is taken for each implemented patch After implementation final code review and testing is done Signoff meeting is held Suggested changes are made Final signoff is taken in 3rd week of october