For Details - Read “Project Assumptions” Post.
Project assumptions.
· Lists and describes the specifi c project assumptions associated with the project scope and the potential impact of those assumptions if they prove to be false.
· Project teams frequently identify, document, and validate assumptions as part of their planning process.
· Information on assumptions may be listed in the project scope statement or in a separate log.
General:
· We assume that because the weather forecast is for a sunny day, and there is not a cloud in the sky, it will not rain so we will not take an umbrella with us to work.
· We assume that the washing machine will not break down and overflow before we set a load of washing as we walk out the door.
· We assume the bus will come on time when we go to the bus stop at a certain time.
Here is the list.
Below is the categorization of assumptions:
1. Scope : There will be no scope change after the ‘Analysis’ phase is over
2. Schedule: Client will not introduce any presssure to complete the project before scheduled time.
3. Schedule: All the phases will be completed on time.
4. Financing : Project funding will not be withdrawn
5. Resources: Development resources will be available since Analysis Phase to the end of the project.
6. Resources: BA resource will be allocated for the entire project life cycle.
7. Resources: An onsite co-ordinator is available to clarify the issues
8. Resources: Resources will not be pulled to do other projects in between
9. Customers/Client: Client will provide the related information and answer to queries on time and thus not affecting project timelines
10. Technologies : Client will not introduce ‘Technology Change’ in b/w of the project
11. Technologies: There will always be technology support from Microsoft.
12. Expectations:
13. SponsorShip
14. Other Assumptions: There will be no natural calamity delaying project timelines.
Regards,
Arun Manglick
No comments:
Post a Comment