This page is for the work on Chapter 10: Working the Project Plan
Owners of this page, please introduce yourself:
Name/ID
Name a hobby or
Something that you like to do:
Say something about your
experience with software
What would you like
to learn frhttp://spmsummer10.wikispaces.com/Working+the+Project+Planom this course?
How would you like
to learn from this course?
Chowdhury Tanvir Jalil (ID:092-25-129)
Watching Movies and traveling
I was involved in the implementation of a banking software in our bank.After implementation i am involved in bug testing,maintenance and support of Banking Software.
New and cost effective techniques to manage a software project.
By sharing knowledge and experience with my teacher and course mates.
Abdur Rahman Bhuyian
[ID: 093-25-140]
Traveling, Reading ........etc
Fully automated system can help to reduce delay time and processing of any task.
Overall, software project management that helps me to develop automated system design and implement the effective project in context of Bangladesh by which we can complete most of our regular jobs automatically and without corruption.
Sharing ideas and group study.
Task 1: Summarise the chapter below in terms of bullets: (10 marks)
Answer: Working with project planAuthorizing the Project work by proper authority: Making a work authorization system for the project
The work authorization system is a document that includes information on the following matters.
Project tasks that need to be completed
Sequence for completing required tasks
Documents and deliverable that need to be developed
Methods of tracking project progress
Required approvals for authorizing work
Project start date
Project end date
Required resources
Utilizing a project management information system:
Project management information system enables us to do the following things:
Track resources to find out whether team members are available, over extended, and on track with their deadlines.
Control project changes, making updates as needed.
Track project activities, such as writing specifications, documenting unit test plans, or creating CBTs.
Report on the status of project activities using templates. The template may be a dashboard that is incorporated into the PMIS; it could also be a standard report set up in the PMIS.
Compare the current status of your project to a baseline.
Track risks associated with the project.
Analyze project conflicts, such as a resource being overextended or two activities being assigned sequentially when they should be consecutive.
View and share project calendars.
Check the status of project costs and schedule. Ensuring the Quality in Execution:
1. Quality planning
2. Quality assurance
3. Quality control Following Quality Assurance: Using the quality assurance process, we can ensure that the project meets the project specifications that were set out at the start of the project in the planning stage. Following the Quality Policy: During the planning phase of all software projects, we should define our quality management plan and outline how we plan to ensure quality in our project and product. We document how we plan to confirm that the project will satisfy the stated requirements. We also outline how we can continue to make quality improvements. Managing Software Project Risks: Risk management is concerned with identifying potential risks for your project and then putting a plan together to deal with them if they occur. Gathering the ingredients for a solid risk management plan
1. The project scope statement
2. The project management plan
3. Your organization’s risk tolerance strategy Analyzing the risks in the project: Some examples of risks are given below:
Key Resources leaving the project
Technology becoming obsolete
Stakeholders attempting to enhance the scope of the project
Leadership changing direction
Labor disputes
Schedule delays due to issue with off-site resources
Personal resources being squeezed because they are involved on too many projects simultaneously
Lack of commitment on project funding
Software testing revealing major bugs that could impact the time line.
Risk Managemant Process: Each of the risk management process has particular tools and techniques that we can use when we develop our risk management plan.
Risk management planning
Risk identification
Qualitative risk analysis
Quantitative risk analysis
Risk response planning
Risk monitoring and control
Gathering information to identifying real risks Monitoring and Controlling Risks: We may create a database to keep track of each previously identified risk, identify and document new risk and track the response plans for each risk. Tackling secondary and residual risks: Secondary risk occurs because of a planned risk response. A residual risk is a risk does not go away. We cannot avoid it. But still we need to mange those risks. Documentingeffectiveness ofrisk management :
1. We can use the data that demonstrates the project effectiveness as we start developing the plans for the next project.
2. We can use the documentation to improve the risk management planning on our current project and the next phase of our current project.
3. We can use this documentation to improve our chances of getting a promotion for being intelligent enough to create a strong risk management plan and the documentation to support it.
Task 2: Explain the bullets in terms of the Grameen Bank Form 15 system. (10 marks)
Owners of this page, please introduce yourself:
Something that you like to do:
experience with software
to learn frhttp://spmsummer10.wikispaces.com/Working+the+Project+Planom this course?
to learn from this course?
[ID: 093-25-140]
Answer:
Working with project plan Authorizing the Project work by proper authority:
Making a work authorization system for the project
The work authorization system is a document that includes information on the following matters.
Project tasks that need to be completed
Sequence for completing required tasks
Documents and deliverable that need to be developed
Methods of tracking project progress
Required approvals for authorizing work
Project start date
Project end date
Required resources
Utilizing a project management information system:
Project management information system enables us to do the following things:
Track resources to find out whether team members are available, over extended, and on track with their deadlines.
Control project changes, making updates as needed.
Track project activities, such as writing specifications, documenting unit test plans, or creating CBTs.
Report on the status of project activities using templates. The template may be a dashboard that is incorporated into the PMIS; it could also be a standard report set up in the PMIS.
Compare the current status of your project to a baseline.
Track risks associated with the project.
Analyze project conflicts, such as a resource being overextended or two activities being assigned sequentially when they should be consecutive.
View and share project calendars.
Check the status of project costs and schedule.
Ensuring the Quality in Execution:
1. Quality planning
2. Quality assurance
3. Quality control
Following Quality Assurance: Using the quality assurance process, we can ensure that the project meets the project specifications that were set out at the start of the project in the planning stage.
Following the Quality Policy: During the planning phase of all software projects, we should define our quality management plan and outline how we plan to ensure quality in our project and product. We document how we plan to confirm that the project will satisfy the stated requirements. We also outline how we can continue to make quality improvements.
Managing Software Project Risks: Risk management is concerned with identifying potential risks for your project and then putting a plan together to deal with them if they occur.
Gathering the ingredients for a solid risk management plan
1. The project scope statement
2. The project management plan
3. Your organization’s risk tolerance strategy
Analyzing the risks in the project: Some examples of risks are given below:
- Key Resources leaving the project
- Technology becoming obsolete
- Stakeholders attempting to enhance the scope of the project
- Leadership changing direction
- Labor disputes
- Schedule delays due to issue with off-site resources
- Personal resources being squeezed because they are involved on too many projects simultaneously
- Lack of commitment on project funding
- Software testing revealing major bugs that could impact the time line.
Risk Managemant Process: Each of the risk management process has particular tools and techniques that we can use when we develop our risk management plan.- Risk management planning
- Risk identification
- Qualitative risk analysis
- Quantitative risk analysis
- Risk response planning
- Risk monitoring and control
Gathering information to identifying real risksMonitoring and Controlling Risks: We may create a database to keep track of each previously identified risk, identify and document new risk and track the response plans for each risk.
Tackling secondary and residual risks: Secondary risk occurs because of a planned risk response. A residual risk is a risk does not go away. We cannot avoid it. But still we need to mange those risks.
Documenting effectiveness of risk management :
1. We can use the data that demonstrates the project effectiveness as we start developing the plans for the next project.
2. We can use the documentation to improve the risk management planning on our current project and the next phase of our current project.
3. We can use this documentation to improve our chances of getting a promotion for being intelligent enough to create a strong risk management plan and the documentation to support it.
Task 2: Explain the bullets in terms of the Grameen Bank Form 15 system. (10 marks)