2: Engage the stakeholders. Well duh! No project is going to be successful without stakeholder buy in. But few projects rarely engage with the stakeholders so that they feel as though they have been heard. If you run the BPMS project along Agile lines you will improve the rate of adoption. Hold regular progress show-and-tell meetings and invite comments every two to three weeks. Make sure the project task list is available online and that they are prioritized so teams can see when their piece is going to be implemented and so priorities can be adjusted to meet user needs. Transparency in everything is critical so put project information online and keep it up to date. Whenever new functionality is available record it being used and put this online too. This aids with the feedback and with the training.
Themes in my blog
Things I’m thinking about
- Vocation or job
- Full Unemployment
- IT Peers Overspend
- Enterprise DevOps is different: here’s why
- Change you can believe in: why change isn’t to be feared
- Do you lock the door when you go shopping?
- Sherlock Holmes and the mystery of the VW Emissions Code Cheat
- Taking the wait out of waiter
- I am a customer – I do not need any other title
Things I thought about
- A day is coming when we switch from full employment to a world where full unemployment becomes possible #FullUnemployment 2 weeks ago
- As technology advances it frees us to go from humans doing things to become humans being things. #FullUnemployment 2 weeks ago
- "xChange16: Registration Now Open" by @kevinparkerusa on @LinkedIn linkedin.com/pulse/xchange1… 3 months ago
From @kevinparkerusaMy Tweets
Tell us what you thinkClick here to take a brief 7 question survey to help me improve my blog. Thanks.