Today I was exposed to a new (actually old) way of planning for a project. Vinay taught me how to use Micrsoft project for making a work break structure. In my own words, wbs is a document in which we list all the tasks during the project life cycle and we use this task list to determine the time required, allocation of resources, precedence of tasks, determination of the shortest path to complete the project. Its helps to breakdown the project into smaller steps, to identify the critical path, to enable us to see the project from a prespective of a project manager.
Microsoft Project 2003 was used to create the wbs. Its an amazing tool. One of the key features is the way it shows the graph in a calender as we type in the tasks and as we assign the number of hours required for each tasks it updates the graph instantanesouly. Well this graph consists of the nodes which are tasks and the background is calender and the length of the tasks represent the time they take in calender. we can also assign the precedence of tasks. which will give the graph a structure. other wise all the tasks are shown in one single time block i.e the project assumes there are unlimited resources avilable to achieve the target and that one task is not dependent on the other. All this aside, to talk in more mathematical terms. Microsoft project will enable us to schedule all the tasks properly and to assign the resources at the critical points which will decrease the congestions and shorten critical path. It helps us to solve one big operation research problem. To increase efficiency. Psycologically speaking having listed down all tasks we can easily keep our goals short and focused. As we see task by task striken off our confidence builds up. Here is my current wbs
Project Start:
Project Finish: |
Tasks
ID | Task Name | Duration | Start | Finish | Resource Names | % Complete |
---|
1 | Password Vault | 28.38 days | Mon 7/27/09 | Thu 9/3/09 | | 0% | 2 | Project Kickoff Phase | 0.5 days | Mon 7/27/09 | Mon 7/27/09 | | 0% | 3 | Identify Stakeholders | 0.5 days | Mon 7/27/09 | Mon 7/27/09 | Developer | 0% | 4 | Requirements | 2.5 days | Mon 7/27/09 | Wed 7/29/09 | | 0% | 5 | Conduct Functional Requirment Meeting | 4 hrs | Mon 7/27/09 | Mon 7/27/09 | Developer | 0% | 6 | Requirment Document | 8 hrs | Tue 7/28/09 | Tue 7/28/09 | Developer | 0% | 7 | Create Use Cases | 8 hrs | Wed 7/29/09 | Wed 7/29/09 | Developer | 0% | 8 | Design | 9.25 days | Thu 7/30/09 | Wed 8/12/09 | | 0% | 9 | Identify business entities and relationships | 3 hrs | Thu 7/30/09 | Thu 7/30/09 | Developer | 0% | 10 | Database schema design | 8 hrs | Thu 7/30/09 | Fri 7/31/09 | Developer | 0% | 11 | Identifiying business rules | 8 hrs | Tue 8/11/09 | Wed 8/12/09 | Developer | 0% | 12 | Identifying subsystems | 6.88 days | Fri 7/31/09 | Tue 8/11/09 | | 0% | 13 | Design forms | 30 hrs | Fri 7/31/09 | Thu 8/6/09 | Developer | 0% | 14 | Information flow diagrams | 10 hrs | Mon 8/10/09 | Tue 8/11/09 | Developer | 0% | 15 | Screen layout diagrams | 15 hrs | Thu 8/6/09 | Fri 8/7/09 | Developer | 0% | 16 | Configure Build Test (CBT) | 13 days | Wed 8/12/09 | Mon 8/31/09 | | 0% | 17 | Configure | 0.5 days | Fri 8/28/09 | Fri 8/28/09 | | 0% | 18 | Setting up repository | 4 hrs | Fri 8/28/09 | Fri 8/28/09 | Developer | 0% | 19 | Build | 10.75 days | Wed 8/12/09 | Wed 8/26/09 | | 0% | 20 | Develop database | 2 hrs | Wed 8/12/09 | Wed 8/12/09 | Developer | 0% | 21 | Develop Procedures | 12 hrs | Wed 8/12/09 | Thu 8/13/09 | Developer | 0% | 22 | Build Admin forms | 24 hrs | Thu 8/20/09 | Mon 8/24/09 | Developer | 0% | 23 | Build Login module | 8 hrs | Tue 8/25/09 | Tue 8/25/09 | Developer | 0% | 24 | Build User forms | 8 hrs | Wed 8/26/09 | Wed 8/26/09 | Developer | 0% | 25 | Build Application Forms | 32 hrs | Fri 8/14/09 | Wed 8/19/09 | Developer | 0% | 26 | Testing | 2.25 days | Thu 8/27/09 | Mon 8/31/09 | | 0% | 27 | Test database Integrity | 2 hrs | Mon 8/31/09 | Mon 8/31/09 | Developer | 0% | 28 | Test Database Procedures | 4 hrs | Fri 8/28/09 | Fri 8/28/09 | Developer | 0% | 29 | Test Forms | 8 hrs | Thu 8/27/09 | Thu 8/27/09 | Developer | 0% | 30 | User Aceptence Testing (UAT) | 2 days | Mon 8/31/09 | Wed 9/2/09 | | 0% | 31 | Testing | 16 hrs | Mon 8/31/09 | Wed 9/2/09 | Developer | 0% | 32 | Deployment | 1.13 days | Wed 9/2/09 | Thu 9/3/09 | | 0% | 33 | Install database | 2 hrs | Wed 9/2/09 | Wed 9/2/09 | Developer | 0% | 34 | Create Website | 3 hrs | Wed 9/2/09 | Wed 9/2/09 | Developer | 0% | 35 | Deploy code | 1 hr | Wed 9/2/09 | Wed 9/2/09 | Developer | 0% | 36 | Configure database and other runtime settings | 3 hrs | Thu 9/3/09 | Thu 9/3/09 | Developer | 0% |
|
Resources
ID | Name | Group | Max Units | Peak Units |
---|
1 | Developer | | 100% | 100% |
|
Assignments
Task ID | Task Name | Resource Name | Work | Start | Finish | % Work Complete |
---|
3 | Identify Stakeholders | Developer | 4 hrs | Mon 7/27/09 | Mon 7/27/09 | 0% | 5 | Conduct Functional Requirment Meeting | Developer | 4 hrs | Mon 7/27/09 | Mon 7/27/09 | 0% | 6 | Requirment Document | Developer | 8 hrs | Tue 7/28/09 | Tue 7/28/09 | 0% | 7 | Create Use Cases | Developer | 8 hrs | Wed 7/29/09 | Wed 7/29/09 | 0% | 9 | Identify business entities and relationships | Developer | 3 hrs | Thu 7/30/09 | Thu 7/30/09 | 0% | 10 | Database schema design | Developer | 8 hrs | Thu 7/30/09 | Fri 7/31/09 | 0% | 11 | Identifiying business rules | Developer | 8 hrs | Tue 8/11/09 | Wed 8/12/09 | 0% | 13 | Design forms | Developer | 30 hrs | Fri 7/31/09 | Thu 8/6/09 | 0% | 14 | Information flow diagrams | Developer | 10 hrs | Mon 8/10/09 | Tue 8/11/09 | 0% | 15 | Screen layout diagrams | Developer | 15 hrs | Thu 8/6/09 | Fri 8/7/09 | 0% | 18 | Setting up repository | Developer | 4 hrs | Fri 8/28/09 | Fri 8/28/09 | 0% | 20 | Develop database | Developer | 2 hrs | Wed 8/12/09 | Wed 8/12/09 | 0% | 21 | Develop Procedures | Developer | 12 hrs | Wed 8/12/09 | Thu 8/13/09 | 0% | 22 | Build Admin forms | Developer | 24 hrs | Thu 8/20/09 | Mon 8/24/09 | 0% | 23 | Build Login module | Developer | 8 hrs | Tue 8/25/09 | Tue 8/25/09 | 0% | 24 | Build User forms | Developer | 8 hrs | Wed 8/26/09 | Wed 8/26/09 | 0% | 25 | Build Application Forms | Developer | 32 hrs | Fri 8/14/09 | Wed 8/19/09 | 0% | 27 | Test database Integrity | Developer | 2 hrs | Mon 8/31/09 | Mon 8/31/09 | 0% | 28 | Test Database Procedures | Developer | 4 hrs | Fri 8/28/09 | Fri 8/28/09 | 0% | 29 | Test Forms | Developer | 8 hrs | Thu 8/27/09 | Thu 8/27/09 | 0% | 31 | Testing | Developer | 16 hrs | Mon 8/31/09 | Wed 9/2/09 | 0% | 33 | Install database | Developer | 2 hrs | Wed 9/2/09 | Wed 9/2/09 | 0% | 34 | Create Website | Developer | 3 hrs | Wed 9/2/09 | Wed 9/2/09 | 0% | 35 | Deploy code | Developer | 1 hr | Wed 9/2/09 | Wed 9/2/09 | 0% | 36 | Configure database and other runtime settings | Developer | 3 hrs | Thu 9/3/09 | Thu 9/3/09 | 0% |
|
Microsoft Home Page
Microsoft Project Home Page
No comments:
Post a Comment