Aus der Praxis von Projektmanagmenteinführungen aller Art (klassisch, agile und Critical Chain) ist eine Liste der typsichen Anforderungen, die eine zugehörige PM-Software erfüllen muss entstanden. Auf dieser Seite möchte ich diese zur Verfügung stellen und um Ergänzungen bitten.
Die meisten Punkte hängen von der Wahl der Steuerungemethode ab ...
Achtung: in der Praxis hat sich heraus gestellt, dass die sich diese Liste aber letzt endlich nicht wirklich zu Auswahl eignet. Die allermeisten der Punkt sind "muss"-Punkte und werden von den meisten der PM-Software-Pakete erfüllt. Die Liste ist jetzt schon in A-B-C-Punkte gegliedert (Priority A=muss, B=wäre sehr gut, C=nice to have). Darüber hinaus auch welche Funktionalitäten mindestens notwendig sind um bestimmte Steuerungen zu implementieren - conventional (klassisch Plan-Ist-Vergleich), Critical Chain (Fortschritt-Pufferverbrauch) und Agile.
Anforderungsliste für PM-Software ...
| Groupe | Criteria | Priority | Mandatory if you want to use ... | ||
| conventional | Critcal Chain | Agile | |||
| General | Ease of use | ||||
| Search function over all projects, within a project | |||||
| Flexible reporting, directly on database | |||||
| Price | |||||
| no further lisence required | |||||
| Tool support | |||||
| Tool stability | |||||
| Web based access to the tool | |||||
| Performance of the tooling | |||||
| SaaS tool | |||||
| local installation within the data center of the company | |||||
| Planning | |||||
| Resource levelling | A | x | x | x | |
| Skillmap, assign skill/Team, n:m relationship possible? | A | x | x | ||
| Calculating, displaying CC | A | x | |||
| Inserting project/feeding buffer | A | x | |||
| Easy use of templates | A | x | x | ||
| Analysing longest chain and other chains | A | x | |||
| Manipulating single tasks (fixed length, SNET, buffer contribution, …) | B | ||||
| Nesting of Tasks / sub projects / project links / checklist per task | B | ||||
| Multiuser access to the same project plan | C | ||||
| Online colaboration in project plan, completely integrated in tool, | C | ||||
| Calendars, inherits from parent, availability schedule | C | ||||
| Milestone buffer | A | x | |||
| Visualization of project plan for the team | B | ||||
| Pipelineing | |||||
| manual staggering | A | x | x | ||
| automatic staggering | B | ||||
| Virtual Drum concept | B | ||||
| Physical Drum | A | x | |||
| fast scenario (trad-off) descision preparation, What if scenario | A | x | x | ||
| Management of DRUM-Tasks (Buffer, length, pipeline capacity) | A | x | |||
| Virtual drum parameters for all projects (eg in % of project, capacity buffer for all projects) | A | x | |||
| Variable resource capacity (monthly, individual schedules) | B | ||||
| Nested Projects | C | ||||
| Execution Control | |||||
| Tasklist with easy reporting of remaining duration | A | x | x | ||
| Escalation, if remaining duration is not reported or RDU trend in wrong direction | A | x | |||
| checklists for a the task to µmanagement the work within a task effectively | B | ||||
| Easy & consistent role management TM, PM | A | x | |||
| Changing plans during execution and sustaining consistent control | A | x | x | x | |
| Taskmanagement, reports for external suppliers (e.g. easier report of RDU) | B | ||||
| Full kit indication, all prereqisites ready? | A | x | |||
| Compliance reports (RDU reporting, early/late start, …) | A | x | |||
| Szenario simulation within tool, setting effective date and look at consequnces | B | ||||
| Integrationn of Jira and other task/bug/ticket systems | C | ||||
| Management Control | |||||
| Portfolio chart | A | x | x | ||
| Single project buffer chart /trend | A | x | |||
| most penetrating task below the fever curve of a project | B | ||||
| statistics about overproportional buffer consumption per team --> driver of continuos improvement process | B | ||||
| Flowtrend, detection of local constraints - increasing task inflow compared to output | B | ||||
| Overview for duedates which are probably not met | B | ||||
| Overview for escalated tasks and buffer recovery actions | B | ||||
| KPIs like project completion rate, task completion rate, Throughput Dollar Days | B | ||||
| Project Memos / Comments | B | ||||
| Continual Improvement | |||||
| delay reasons reporting | B | ||||
| Statistical analysis based on project buffer consumption | A | x | |||
PMBackstage über Anforderungen an PM-Software:
Comments:
|
Ein Screencast von Stefan Hagen von pm-blog.com mit Mark Mey-Meyer zum Thema Auswahl der richtigen PM-Software.
Posted by bschloss at 11. Jun 2013 21:36
|