Managing Projects in “Internet Time”:

1. Managing Projects in“Internet Time”: Genova Technologies Dawn Ainger

2. Background • Genova Background • IT Consulting/Software Engineering • Founded 1993 • Staff averages 15 years experience • Projects Range from 1 month to 7 years • Medicare BPA winner • Rockwell Collins Enterprise Provider • DOT Certified Woman-Owned Small Business... • 8A Certified

3. Two of Genova’s Eastern Iowa Customers

4. How Does Genova’s Methodology Work? How is it Different From Traditional Techniques?

5. How Does Genova’s Methodology Work? • Let’s Look at What’s NOT working….

6. Traditional Techniques • Functional Requirements • System Requirements • Business Requirements • Hardware Requirements • Software Requirements • Logical Data View • Physician Data View • Logical System Architecture • Physical System Architecture • Design Requirements • Legal Requirements • Usability Requirements • Security and Privacy Requirements • Performance Requirements

7. “I've got ten bucks in my pocket, nothing to offer you” • “She is made of iron” • “I'm King of the World!” • “God himself can't sink this ship”

8. Traditional Techniques • Like taking a script from a movie and… • Grouping script by who is saying a line • Asking Someone to figure out the story… • Why Did this Develop? • Information Overload • Traditional Techniques are NOT Working because… • Don’t “tell a story” • Not technically detailed for the IT Professional • Too technically detailed for the user to know what is going on • No rigorous methodology

9. Genova’s Requirements Methodology Tells the story by keeping the it tact with different levels of detail for different readers to avoid information overload

10. Full Book

11. Reader's Digest

12. Movie

13. Soundtrack

14. Movie Full Book Reader's Digest Soundtrack

15. When Something Goes Wrong… • “The System shall track user non-compliance….”

16. Seminar Overview • Balancing Between Bureaucracy and “Adhocracy”; One Process Does NOT Fit All: THE MISSION • Starting a Project Right; A Successful Requirements Gathering Methodology • Teamicide: How to Kill Otherwise Happy Productive People and Projects

17. The System…..

18. Let’s Get Started! • Dawn Ainger • Genova Technologies • 319-378-8455 • dawn.ainger@genovatech.com

19. The Mission • Functional Purpose • Business Purpose • Measures of Success

20. Examples • House • Class Example • Project Example

21. On to the Workshop….

22. The 10 top reasons for not doing requirements • We have already started writing code, and we don’t want to spoil it • It’s easier to change the system later than to do the requirements up front • The problem is too complex to write requirements • It’s not in the budget • We never did requirements before • We don’t have time to do requirements • Who cares what the users want • We know what the users want • The users don’t know what they want • We don’t need requirements, we’re using objects

23. Cost of a Requirement

24. Requirements Analysis • Mission • Functional Purpose • Business Purpose • Measures of Success • Stakeholders • Risks/Constraints (time, budget, personnel) • Work Context Diagram (not a business process model)

25. Requirements Analysis • Events • Scenarios • Alternative Scenarios • Non Scenarios – What to document • Non Events • Scenarios • Alternative Scenarios • Non Scenarios • Functional and Non Functional

26. Requirements Analysis • How to write a requirement • N-V-N • Put design options in notes – tough to do! • Quality Gateway • Fit Criteria • Customer Value • Viable • “Not” ‘s • Exceptions to non-scenarios put in notes (things the system does NOT need to do, but were discussed)

27. Examples • House • Class Example • Project Example

28. On to the Workshop….

29. Summary • Functional Purpose • Business Purpose • Measures of Success • Events/Scenario Structure

30. Thank You!