1. Secrets of IBIS’ Success (or Lois’ parting shots) 12/18/07

2. Has IBIS-PH Been Successful? November 2007 –7,298 visitors, made –10,680 visits Other states using IBIS or actively implementing an IBIS Website –Arizona –Alaska –New Jersey – Washington, DC – New Mexico – NCHS

3. 1. Take Responsibility for the Product Your job doesn’t end when you hire a contractor. You are liaison between the developer and the end-user. You have a different role than that of the contractor, but to do it right takes a lot of time, a lot of work.

4. 2. Communicate Early, Often To ensure a good user experience, one must: –Communicate with users to understand requirements –Communicate with developer to help him/her understand user perspective –Communicate with sponsor for needed resources (Good user experience is necessary but not sufficient.)

5. 3. Cultivate Trust, Credibility With customer: –Under-promise –Over-deliver With contractor: –Shouldn’t need antagonism between software development contractor and UDOH client –it’s not productive, not necessary, not nice.

6. 4. Take the Long View Keep the vision in sight. Choose a path that won’t preclude programming options further down the road. Lead.

7. 5. Frequent User Evaluation and Feedback Rapid prototyping, Short development cycles. (We hadn’t heard this gospel 7 years ago, it happened by accident, but it worked.)

8. 6. Competent Staff You don’t need to be a genius, BUT you do need staff who: Are competent Pay attention to detail

9. 7. Champion Champion the product, advertise your success as you reach milestones (or when a good opportunity arises). Cultivate champions as far up the food chain as possible.

10. 8. The Power Paradox Power is only granted to those who give it up. You’re not in it alone. –Corollary 1. You can’t do it by yourself, so get the right people to help. –Corollary 2. You didn’t do it yourself, so give credit where credit is due.

11. 9. “Not too loose, not too tight.” Don’t be too laissez-faire – keep tabs on what is going on, stay involved, stay motivated and energized about the project. Don’t be too controlling – let others help you, be open to advice, don’t be defensive in the face of user feedback.

12. 10. Luck Right place. Right time. Right contractor. Adequate funding.

13. The “Top 10” List 1.Take responsibility 2.Communicate 3.Cultivate trust 4.Long-term thinking 5.Short development cycles 6.Competent staff 7.Champion 8.Power paradox 9.Not too loose, not too tight. 10.Luck

14. Project Management Roles Source: Project Management Process Guide, Brigham Young University, Enterprise Project Management Strategy & Enterprise Architecture Project Management Development Lifecycle Product Management Operations Customer Project Portfolio Management

15. Project Management Roles Source: Project Management Process Guide, Brigham Young University, Enterprise Project Management Strategy & Enterprise Architecture Project Management Development Lifecycle Product Management Operations Customer Project Portfolio Management Project has a … defined beginning, defined end, specific deliverable, budget

16. Project Management Roles Source: Project Management Process Guide, Brigham Young University, Enterprise Project Management Strategy & Enterprise Architecture Project Management Development Lifecycle Product Management Operations Customer Project Portfolio Management Project manager is “IT- side” not business- side.

17. Project Management Roles Source: Project Management Process Guide, Brigham Young University, Enterprise Project Management Strategy & Enterprise Architecture Project Management Development Lifecycle Product Management Operations Customer Project Portfolio Management Where resources are assigned to projects

18. Project Management Roles Source: Project Management Process Guide, Brigham Young University, Enterprise Project Management Strategy & Enterprise Architecture Project Management Development Lifecycle Product Management Operations Customer Project Portfolio Management Makes decisions re: strategic direction for organization I.T. architecture.

19. Project Management Roles Source: Project Management Process Guide, Brigham Young University, Enterprise Project Management Strategy & Enterprise Architecture Project Management Development Lifecycle Product Management Operations Customer Project Portfolio Management Product: Something we offer to customers.

20. Project Management Roles Source: Project Management Process Guide, Brigham Young University, Enterprise Project Management Strategy & Enterprise Architecture Project Management Development Lifecycle Product Management Operations Customer Project Portfolio Management Product manager is business-side, not IT- side.

21. Project Management Roles Source: Project Management Process Guide, Brigham Young University, Enterprise Project Management Strategy & Enterprise Architecture Project Management Development Lifecycle Product Management Operations Customer Project Portfolio Management Critical communication path!

22. Project Management Roles Source: Project Management Process Guide, Brigham Young University, Enterprise Project Management Strategy & Enterprise Architecture Project Management Development Lifecycle Product Management Operations Customer Project Portfolio Management Close alignment is needed here (can’t offer something we’re not able to do in our architecture).

23. Project Management Roles Source: Project Management Process Guide, Brigham Young University, Enterprise Project Management Strategy & Enterprise Architecture Project Management Development Lifecycle Product Management Operations Customer Project Portfolio Management “Requirements Triangle”