Please enable JavaScript.
Coggle requires JavaScript to display documents.
Practical project management tools - Coggle Diagram
Practical project management tools
Organisational goals
Stakeholders
Professionally led
(seeks to be marked out as a professional organisation using commercial tools)
• Benefits: the programs are already designed and are often available within existing organisational management tools.
• Risks: the software will have its own internal language and processes which cannot be changed and which need to be learned.
EX branded software which can be used offline or online may be most suitable (e.g. Slack and XXXXXXXX).
Community led
(wants to use tools which its beneficiaries would use)
• Benefits: the program can be employed in a way that fits the project, such as by using beneficiary language and XXXXXXX.
• Risks: it is difficult to ensure consistency of approach and quality if multiple projects are being run across an organisation.
EX free or open source software (e.g. Google Sheets, Microsoft Office Excel Online and LibreOffice Calc).
Aiming for standardisatio
n (would like a system that can be used for every project it runs)
• Benefits: each new project has a standard starting place and there is consistency in project management style throughout the organisation.
• Risks: the organisation’s projects may not be managed in a consistent style, which could result in the organisation delivering patchy work.
EX may want to choose either commercial software (see examples in ‘Professionally led’ above) or agreed organisational templates, such as XXXXXXXXXXXXXX.
Aiming for flexibility and tailoring (would prefer those leading each project to make their own tool choice)
Core values
Transparency ( select a tool which allows the appropriate people to easily access it)
• Benefits: desired transparency
• Risks: potential for inappropriate people to access data
Supporting staff (committed to training and supporting staff)
good user information and which includes dedicated organisational support may be most appropriate (e.g. XXXXXXXXX and XXXXXXX)
• Benefits: this approach maximises the chance that everyone employing the tool feels secure in how to use it.
• Risks: [?? querying the example given]
Innovation
Requirements
• project size;
• number of staff;
• need for flexibility.
• project cost;