Methods

How shall this be done? Most of the things we are doing in projects have been done by someone before. Why not take advantage of it and use a well-proven structured method instead of inventing everything on an ad-hoc basis. Selecting methods that suit project needs is helping team members know how to approach activities and is promoting teamwork through joint ways of doing things and joint terminology.

Selection of methods can be straightforward e.g. By using methods already implemented in the company, it can be a huge investment in itself. In some cases, new methods can require organizational transformation since established ways of doing things are challenged and changed.

Methods in projects cover areas like project management, product development, software, development, IT management, documentation, test, data migration, stakeholder management and organizational implementation.

Activities
Identify methods for project execution
Project management
Product development
Development
Test
Test management
IT management
Release management
Data migration
Organizational implementation
Training
Select and implement method
Define responsibilities for implementation and usage
Is the method available in the Company / shall project introduce a new method?
Document how method is used in project
Define plan for introducing method
Get prerequisites in place (e.g. Setup and Access to relevant systems)
Introduce method to team members (information, training)
Evaluate method

Risks
Methods are not being adjusted to the settings
Problem: Careful attention is not being paid on how to apply the methods in the specific context. Consequence: Methods may not fit culture, team and purpose. Team members waste time trying to adapt to methods.
Defining and establishing methods becomes a project in itself
Problem: Establishing the required methods is a big task in itself and require substantial effort, focus and time within the project. Consequence: There is a risk that defining and establishing methods may divert the focus from the primary purpose of the project.
Lack of experience with required methods
Problem: The project team lacks experience in the needed methods. Consequence: Team members do not have the required skills to realize the project plan and benefits.
No well-defined method for project execution
Problem: The approach for project execution within the important areas (e.g., development, testing, project management) is inadequate. Consequence: The project is exposed to the risk of spending a significant amount of time and money developing its own methods. All project phases would suffer.

Good Projects Knowledge Base

Methods

About