|
How to Choose Project Management Software
About this Blog
RSS
Recent Posts
The Scores in Project Management Maturity Assessments Don’t Matter!
Give the Project Manager Authority to be Successful
Meetings Are (Usually) Just Not Worth the Time!
The Importance of Benefits Management
How to Get Real Value from Lessons Learned
Categories
accountability, agenda, agile, Artificial Intelligence, authority, BAC, Benchmarking, Benefits, Benefits Realization, Change Management, communication, Complexity, Consulting, CPI, delegated authority, EAC, Earned Value Management, entrepreneurship, ISO21500, Knowledge Transfer, Leadership, Lessons Learned, Management, managing change, meetings, mental health, Methodologies, methodology, OPM, Organizational Project Management, outcomes, outputs, people, People Skills, people skills, PMBOK Guide, PMO, PMP, PMP Exam, portfolio management, practitioner development, professional development, project delivery, project management, Project Management Professional, project manager, project success, responsibility, risk, skills, soft skills, software, SPI, standards, strategic management, strategy, tailoring, teamwork, tools, Total Project Management, TPM, travel, waterfall, Wellbeing
Date
Comments (6)
Interesting These 5 Tips On Choosing A Project Management Software
I would add a sixth tip:
- Be aware of what happens in the market.
There are situations where project management software proposals are disruptive and increasingly approach our needs for planning and gathering relevant information for project performance monitoring and, consequently, for support in the decision making process. decision
In addition to your points, I'd add scalability and sustainability. Needs are fleeting. Ensure the chosen solution can support any growth; for example, integrations with new systems.
Andrew raised a good point scalability. Maybe a project management tool fits perfectly for the technology department (as Jira) and doesn't make any sense for the product development team, or marketing.
Generally I saw that Tech team choose their tool, and try to engage the other departments without understanding the needs of the other potential users in the organization.
For me, the requirements exercise should cover more than features: who will maintain the data, what needs to integrate with existing systems, what reporting PMs and leadership actually need, and how much flexibility the PMO will require as processes evolve.
I’d also strongly support the recommendation to treat implementation as a change-management effort. Whether an organization ends up with Microsoft Project, Planview, Smartsheet, or Celoxis, the software itself won’t solve much if users aren’t trained, supported, and involved in shaping how it is used.
Please Login/Register to leave a comment.
|
"640K ought to be enough for anybody." - Bill Gates, 1981 |
