Summary:
- Managing large multi-tool global projects
We started with participants offering project scenarios from various sectors (public, private, academia, ...). Five of these are shown in the mindmap.
The discussion highlighted the following challenges:
- time-lines: projects tend to take much longer than expected (estimating is difficult)
- obsolescence: planned features are obsolete by the time they are implemented
- versions: the vendor may release new versions of base software while extensions to the previous version are being developed for the client - the new release may work differently or even have excluded functionality critical to these extensions/customisations.
- various platforms - clients and servers: each with their own upgrade schedules
- GNU/Linux, Debian, Ubuntu, ...
- Solaris
- Windows
- Android
- etc.
- 32 bit vs 64 bit - unforeseen issues when upgrading hardware
- challenges over elapsing years:
- things (requirements, versions, ...) change but management doesn't change or keep up with management leadership styles
- requirements change and vendors don't understandÂ
- they generally don't want to cooperate and want the functional requirements to be written in stone (vendors' ideal) - even though they might have signed up to a collaborative organic process.
- Multiple consultants competing for the same work.
|
Recommendations:
- Educate management to keep up with modern management styles in changing environments requiring agility.
- Communication and transparency at all times.
We did not really solve any problems, but is comforting to know that we are not alone in facing the challenges. The participants felt the conversation could have continued.
So, feel free to add notes and insights below ... and possibly put a post-it on the launchpad for a follow-up session.
Notes
|
