Successful Project Management
| Line 7: | Line 7: | ||
== Meeting Strategies == | == Meeting Strategies == | ||
| − | A meeting can be defined in many ways, one of which is: “a focused interaction of cognitive attention, planned or chance, where people agree to come together for a common purpose, whether at the same time and the same place, or at different times in different places” <ref name=''Rom''> 'Romanco, N. and Nunamaker, J. (2001). Meeting Analysis: Findings from Research and Practice. Proceedings of the 34th Annual Hawaii International Conference on System Science, http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.570.6650&rep=rep1&type=pdf'' </ref>. Or as Kayser defines: “A meeting is a gathering where people speak up, say nothing, and then all disagree” <ref name=''Rom'' | + | A meeting can be defined in many ways, one of which is: “a focused interaction of cognitive attention, planned or chance, where people agree to come together for a common purpose, whether at the same time and the same place, or at different times in different places” <ref name=''Rom''> 'Romanco, N. and Nunamaker, J. (2001). Meeting Analysis: Findings from Research and Practice. Proceedings of the 34th Annual Hawaii International Conference on System Science, http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.570.6650&rep=rep1&type=pdf'' </ref>. Or as Kayser defines: “A meeting is a gathering where people speak up, say nothing, and then all disagree” <ref name=''Rom''>. The last definition indicates how unproductive and unconstructive meetings can be. In fact, research shows that even though managers spend more than 50% of his/her official work time in meetings, many meetings fail and cause great and unnecessary costs on wasted working time. |
However, meetings can be very essential for larger groups of people working together, in order to agree upon key project management activities such as scheduling, cost, and quality. For this reason good meeting strategies can be helpful and in some cases necessary. There are many tools which can be applied in order to make meetings more efficient, and in this article some of the most common ones are explained. | However, meetings can be very essential for larger groups of people working together, in order to agree upon key project management activities such as scheduling, cost, and quality. For this reason good meeting strategies can be helpful and in some cases necessary. There are many tools which can be applied in order to make meetings more efficient, and in this article some of the most common ones are explained. | ||
Revision as of 14:50, 23 February 2020
Building 310
Contents |
Abstract
Meeting Strategies
A meeting can be defined in many ways, one of which is: “a focused interaction of cognitive attention, planned or chance, where people agree to come together for a common purpose, whether at the same time and the same place, or at different times in different places” [1]. Or as Kayser defines: “A meeting is a gathering where people speak up, say nothing, and then all disagree” Cite error: Closing </ref> missing for <ref> tag.
Another tool which can be used together with the project phase model is to identify the costs throughout the whole project’s life cycle. In most projects the costs will be low in the beginning (Initiation) and will start to increase from the end of the planning phase Cite error: Invalid <ref> tag;
refs with no content must have a name. It is important to make the meetings as efficient as possible when the costs are high, which such a model can help you identify. An example of the model is illustrated in Figure xx.
Insert model of cost and staffing level model.
A collection of tools for meeting strategies
Avoid unnecessary meetings
First of all it is important to avoid unnecessary meetings. This is especially important when the costs are high and the time is scarce, since people are not fond of wasting their time and this will cause higher costs. A good method is therefore to set up some guidelines for when it is acceptable to call a meeting in order to avoid unnecessary meetings. There are a couple of things that indicates when a meeting is needed Cite error: Closing </ref> missing for <ref> tag]]
Customer Profile
- Gains: the benefits which the customer expects and needs, what would delight customers and the things which may increase likelihood of adopting a value proposition.
- Pains: the negative experiences, emotions and risks that the customer experiences in the process of getting the job done.
- Customer jobs: the functional, social and emotional tasks customers are trying to perform, problems they are trying to solve and needs they wish to satisfy.
Value Proposition
- Gain creators: how the product or service creates customer gains and how it offers added value to the customer.
- Pain relievers: a description of exactly how the product or service alleviates customer pains.
- Products and services: the products and services which create gain and relieve pain, and which underpin the creation of value for the customer.
How to wiki
How to add a reference?
Do it in the text like this:
write [2]
Refer to the same reference again by writing: Cite error: Invalid <ref> tag;
refs with no content must have a name
It automaticly print it under References :-)
How to add a picture: Click on the botton "Upload file" on the left. Give the file a name you can remember Go into the wikipage to edit. write: [File:name.jpg|300px|thumb|right|picture text]
Application
Limitations
Annotated Bibliography
References
- ↑ 'Romanco, N. and Nunamaker, J. (2001). Meeting Analysis: Findings from Research and Practice. Proceedings of the 34th Annual Hawaii International Conference on System Science, http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.570.6650&rep=rep1&type=pdf
- ↑ Author (year) title, link
