Abstract
The chapter “Comprehensive Topics” considers topics that could not be assigned directly to project phases. These are requirements, project culture, communication, documentation, quality, and risk management. Additionally, the chapter presents methods proven to be helpful in a project. Requirements engineering helps to deal with requirements, to identify the characteristics of a product or a system for a high customer value. In a typical project first the requirements have to be identified and to be assessed. If these are known, the requirements have to be managed: They are fulfilled, they may drop out and get changed, or maybe some are added. The project culture describes the cooperation of the project members in the project. Additionally, the image of a project plays a role. Globalization results in international projects with different cultures and value systems converging. This has to be considered. A common language has to be defined. The key success factor for a project is good communication. Which communication devices are used in a project? A communication plan shows the communication channels in a project.An important aspect is the quality of a project. Quality measures should help to achieve the required quality in a project. A good quality in a project results in high-quality project results.Risk management enables project success, even with possible difficulties. For this risks are collected and assessed regularly to initiate counteractions if necessary. Presented methods support the project progress. Brainstorming is a simple and effective method that could be used during the complete project life cycle. With the flashlight method, it is possible to get a group status concerning a closed question.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
A stakeholder is everyone who could influence a project and is concerned by a project or is interested in a project.
- 2.
See Sect. 3.1.7.
- 3.
In the literature occasionally requirements management is used synonymously with requirements engineering.
- 4.
Consider that sensitive contents may not be published in general. Often corresponding written authorizations are required.
- 5.
Also known as “Gemba principle”.
References
Angermeier, G.: Projektmanagement-Glossar des Projekt Magazins (2016). https://www.projektmagazin.de/glossar/. Checked on 27 June 2016
Buzan, T., Buzan, B.: The Mind Map Book: How to Use Radiant Thinking to Maximize Your Brain’s Untapped Potential. Penguin Books, New York (1996)
Campbell, M.: Communication Skills for Project Managers. AMACOM American Management Association, New York (2009)
Cave, C.: Creativity Web - Resources for Creativity and Innovation (2005). http://members.optusnet.com.au/charles57/Creative/index2.html. Checked on 27 June 2016
DeMarco, T., Lister, T.: Peopleware: Productive Projects and Teams. Dorset House, London (1987)
Deming, W.E.: Out of the Crisis. Massachusetts Institute of Technology, Cambridge (1982)
GPM Deutsche Gesellschaft für Projektmanagement e. V.: PM Methoden (2016). http://www.gpm-infocenter.de/PMMethoden/Startseite. Checked on 27 June 2016
IEEE Standards Board: lEEE Std 610.12-1990; IEEE Standard Glossary of Software Engineering Terminology. Technical Report, IEEE (1990). https://standards.ieee.org/findstds/standard/610.12-1990.html. Checked on 27 June 2016
International Requirements Engineering Board: IREB - Home (2016). http://www.ireb.org/. Checked on 27 June 2016
International Software Testing Qualifications Board: Standard Glossary of Terms Used in Software Testing, Version 3.01 (2015). http://www.istqb.org/downloads/. Checked on 27 June 2016
Leffingwell, D., Widrig, D.: Managing Software Requirements: A Unified Approach. Addison-Wesley, Boston, MA (1999)
Lehrstuhl für Technologie und Innovationsmanagement (TIM), RWTH Aachen: WiPro Innovative mit Methode (2016). http://www.innovationsmethoden.info/. Checked on 27 June 2016
Mehrabian, A., Ferris, S.R.: Inference of attitude from nonverbal communication in two channels. J. Couns. Psychol. 31 (3), 248–252 (1967)
Pohl, K., Rupp, C.: Basiswissen Requirements Engineering; Aus- und Weiterbildung zum “Certified Professional for Requirements Engineering”. dpunkt.verlag, Heidelberg (2011)
Project Management Institute: A Guide to the Project Management Body of Knowledge (PMBOK Guide 5), 5th edn. Project Management Institute, Newtown Square, PA (2013)
Project Management Institute: The high cost of low performance: the essential role of communication (2013). https://www.pmi.org/~/media/PDF/Business-Solutions/The-High-Cost-Low-Performance-The-Essential-Role-of-Communications.ashx. Checked on 27 June 2016
Rajkumar, S.: Art of Communication in Project Management. Project Management Institute, Newtown Square, PA (2010). http://www.pmi.org/learning/effective-communication-better-project-management-6480. Checked on 27 June 2016
Rohrbach, B.: Kreativ nach Regeln, Methode 635, eine neue Technik zum Lösen von Problemen. Absatzwirtschaft 12 Heft 19, 73–76 (1969)
Schienmann, B.: Kontinuierliches Anforderungsmanagement. Prozesse - Techniken - Werkzeuge. Addison-Wesley, Reading, MA (2001)
Wikipedia: Requirements management (2016). https://en.wikipedia.org/wiki/Requirements_management. Checked on 27 June 2016
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2016 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Alam, M.D., Gühl, U.F. (2016). Comprehensive Topics. In: Project-Management in Practice. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-662-52944-7_2
Download citation
DOI: https://doi.org/10.1007/978-3-662-52944-7_2
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-662-52943-0
Online ISBN: 978-3-662-52944-7
eBook Packages: Computer ScienceComputer Science (R0)