Projects come in all shapes and sizes, from the small and straight-forward to extremely large and highly complex. Project management can be concerned with anything: people, products, services, materials, production, IT and communications, etc…. One of the most important services always initiates as a project and need to be developed in a dynamic manner is the Instructional Design (ID). Any ID starts and ends as a project. Therefore, the development of instructional design should be always without exception associated with specific rules, terms and regulations that govern and control the processes and successes of the project.
The project rules should be an accurate description of what the project aims to achieve, and the criteria and flexibilities involved, its parameters, scope, range, outputs, sources, participants (stakeholders’ identification), funds and timeline. Usually the project manager must consult with others and then agree the project specification with superiors, or with relevant authorities. The specifications and rules may involve several drafts before it is agreed or can be changed with the course of the project development. A project specification is essential in that it creates a measurable accountability for anyone wishing at any time to assess how the project is going, or its success on achievement. Project rules also provide an essential discipline and framework to keep the project on track, and concerned with the original agreed aims and parameters. A properly formulated and agreed project rules also protects the project manager from being held to account for issues that are outside the original scope of the project or beyond the project manager's control.
Project rules can are to be declared in the Statement of Work (SOW), which should includes:
Describe purpose, aims and deliverables.
State parameters (timescales, budgets, range, scope, territory, authority).
State people involved and the way the team will work (frequency of meetings, decision-making process).
Establish 'break-points' at which to review and check progress, and how progress and results will be measured.
Communication is a serious component of all levels of project management. Communication needs to be on different levels such as formal and informal with stakeholders and within the project team. In order to ensure that communication is controlled a communication map should be produced at the start of the project as part of the project plan. This communication map should identify who needs what information, when they will need it and in what form it will be given to them. It should include the collection and filing structure, reporting structure and the regularity of reporting. This ensures that all parties know what information they are due to receive during the project and whom they must communicate through to get their issues executed. Communication needs to be clear. For example the communication of the project schedule needs to be in such a way that the stakeholders can easily understand the work packages and the program. It is important that the project manger does not rely on gobbledygook to communicate to stakeholders. All the communications between the project manager and stakeholders should through more than one means and documental.
The project rules should be an accurate description of what the project aims to achieve, and the criteria and flexibilities involved, its parameters, scope, range, outputs, sources, participants (stakeholders’ identification), funds and timeline. Usually the project manager must consult with others and then agree the project specification with superiors, or with relevant authorities. The specifications and rules may involve several drafts before it is agreed or can be changed with the course of the project development. A project specification is essential in that it creates a measurable accountability for anyone wishing at any time to assess how the project is going, or its success on achievement. Project rules also provide an essential discipline and framework to keep the project on track, and concerned with the original agreed aims and parameters. A properly formulated and agreed project rules also protects the project manager from being held to account for issues that are outside the original scope of the project or beyond the project manager's control.
Project rules can are to be declared in the Statement of Work (SOW), which should includes:
Describe purpose, aims and deliverables.
State parameters (timescales, budgets, range, scope, territory, authority).
State people involved and the way the team will work (frequency of meetings, decision-making process).
Establish 'break-points' at which to review and check progress, and how progress and results will be measured.
Communication is a serious component of all levels of project management. Communication needs to be on different levels such as formal and informal with stakeholders and within the project team. In order to ensure that communication is controlled a communication map should be produced at the start of the project as part of the project plan. This communication map should identify who needs what information, when they will need it and in what form it will be given to them. It should include the collection and filing structure, reporting structure and the regularity of reporting. This ensures that all parties know what information they are due to receive during the project and whom they must communicate through to get their issues executed. Communication needs to be clear. For example the communication of the project schedule needs to be in such a way that the stakeholders can easily understand the work packages and the program. It is important that the project manger does not rely on gobbledygook to communicate to stakeholders. All the communications between the project manager and stakeholders should through more than one means and documental.

