ISQA8950: Capstone for MS in Management Information Systems

1. ISQA8950: Capstone for MS in Management Information Systems Dr. Deepak Khazanchi Assisted by: Shonna Dorsey (Project Consultant) Zac Fowler and Roni Myers (Web Design Gurus)

2. Agenda for today • Introductions - Students/Instructors (6:00pm) • Course overview (6:30pm) • Course Organization & Logistics • Resources & Templates • Requirements • Grading Policy • Social Break (6:45pm) • Introduction to Agile Development and Project Management with Scrum (7:00pm) • Meet your Client (7:30pm)

3. Introductions

4. Brief Introductions • Dr. Deepak Khazanchi • Shonna Dorsey • Zac Fowler • Roni Myers • and • Students

5. Contact information • Email • khazanchi@unomaha.edu • shonna.dorsey@gmail.com • Voice • 402.554.4968 (Khazanchi) • 402.301.8814 (Dorsey) • 402.554.4909 (Fowler and Myers) • In person • PKI 172 (Khazanchi) • PKI 376 (Fowler and Myers) • Blackboard • http://blackboard.unomaha.edu/ (Blackboard)

6. Course overview

8. Background Two out of three IT projects fail to deliver planned outcomes resulting in cost overruns, schedule delays, and unmet requirements. (Standish 2004) Project failures cost the US economy at least $24 billion and possibly as high as $75 billion between years 2000 and 2005. (Charatte, 2005)

9. Course overview • The Capstone course is unique! • Single system design & development challenge for whole class • Students function as single project team with subteams • The class room is a learning theater rather than a lecture hall • In-depth practical experience

10. Course Objectives • Apply concepts as covered in the MIS Core classes. • Understand how MIS core subjects interplay in real projects • Perform MIS analysis and design in a mid-sized project • Match MIS problems to MIS analysis and design methods • Provide effective leadership in mid-sized MIS projects • Prepare and run project meetings • Handle design problems from multiple perspectives, including a technical, managerial, and end-user perspective • Make professional presentations and reports • Choose and use appropriate tools for project completion, including communication tools and modeling tools

11. Structure • Class is run as a single IS development project • Each weekly project meeting (class): • Has a chair and secretary • Has a preplanned agenda (including goals) • Has been pre-discussed with the professors • May include lectures • Concludes with the definition of work assignments for subgroups (Action Items)

12. Class Structure • Project includes: • Conceptualization, Analysis, and Design, Prototyping, User testing • Presentations • Reports (weekly, progress report, final report) • Readings • As posted on course web site in Blackboard • http://blackboard.unomaha.edu

13. Working as a Team • Shared... • Knowledge and Understanding • Responsibilities • Efforts • Challenges: • How to deal with slackers? • How to deal with disagreement? • How to involve the professors? • Strategies: • Roberts Rules of Order (or other team coordination procedure) • Communication (cc profs on all outside communication) • Peer evaluation • Firing from team?

14. Being a meeting chair • Responsibilities: • Defining the meeting goal • Defining the meeting deliverables • Defining the meeting agenda • Applying Robert’s Rules of Order • Monitor meeting progress • Maintain an open, participative atmosphere • Facilitate task assignments

15. Being a meeting secretary • Responsibilities: • Record meeting results: • Summarize results, not record verbatim discussions • List decisions • List action items and PTA’s (persons to act) • Prepare meeting minutes • Keep attendance record • Announce the meeting • Invite guests to the meeting • Handle official correspondence on behalf of team

16. Timings • Class rhythm: • Class time: 18:00 – 20:40, Thursday • Meeting minutes: 08:00, Monday (secretary) • Agenda: 18:00, Tuesday (chair) • Subteam status reports: 21:00 Mondays (subgroups) • Peer reviews: Assigned Friday by 18:00 (SharePoint) • Send reports to Shonna • Use [CAPSTONE]in the subject line of all e-mail communications • Office hours • By appointment only (Khazanchi) • By appointment only (Dorsey)

17. Deliverables – Syllabus Review

18. Grading • Functional prototype 40% • Final presentation 10% • Final report 10% • Individual assessment 20% • Peer review 10% • Chair/secretary 10% TOTAL 100%

19. The Honor Code • Working as an individual: • Do your own work • Do not copy from other sources without citing those sources • If you copy someone else’s words, word for word, then put that passage in quotation marks and cite the author or source. It does not matter whether your source is from a book, the web, the spoken word – this rule applies to all sources. • See & sign plagiarism statement on Blackboard • Read and abide by the UNO Student Code of Conduct, http://www.unomaha.edu/~saffairs/studentcode.php

20. Expectations • Final goal of class: A working prototype • Leadership & Initiative • Ownership & Responsibility • Respect & Integrity • Amount of work • Role of the professors

21. Break

22. Introduction to Agile and project management Putting it all together

24. Our Development Approach • Agile software development • Scoping and requirements prioritization • Concurrent analysis, design, and implementation • Small and fast iterations • Focus on delivery of a working system • Intensive interaction with client • Agile approaches include Scrum, Crystal, XP, ASD

25. What makes Agile development special? • Self organizing teams • Potentially shippable product available at the end of the first cycle (sprint) • Retrospectives at the end of each sprint instead of at the end of project only • Project leads • Project Manager • Scrum Master

26. Agile Development Process

27. Product backlog This is the product backlog The requirements A list of all desired work on the project Ideally expressed such that each item has value to the users or customers of the product Prioritized by the product owner Reprioritized at the start of each sprint

28. Sprint planning Code the middle tier (8 hours) Code the user interface (4) Write test fixtures (4) Code the foo class (6) Update performance tests (4) As a vacation planner, I want to see photos of the hotels. • Team selects items from the product backlog they can commit to completing • Sprint backlog is created • Tasks are identified and each is estimated (1-16 hours) • Collaboratively, not done alone by the ScrumMaster • High-level design is considered

29. Product owner Define the features of the product Decide on release date and content Prioritize features according to market value Adjust features and priority every iteration, as needed  Accept or reject work results

30. The ScrumMaster • Responsible for enacting Scrum values and practices • Removes impediments • Ensure that the team is fully functional and productive • Enable close cooperation across all roles and functions • Shield the team from external interferences

31. The Team • Typically 5-9 people • Cross-functional: • Project Manager, programmers, testers, user experience designers, etc. • Members should be full-time • May be exceptions (e.g., database administrator)

32. The Team • Teams are self-organizing • Ideally, no titles but rarely a possibility • Membership should change only between sprints

33. Sprint prioritization Sprint planning Sprint goal Sprint backlog • Analyze and evaluate product backlog • Select sprint goal • Decide how to achieve sprint goal (design) • Create sprint backlog (tasks) from product backlog items (user stories / features) • Estimate sprint backlog in hours Sprint planning meeting Team capacity Product backlog Business conditions Current product Technology

34. Weekly Standup Meeting 1 2 3 What did you do last week? What will you do this week ? Is anything in your way? • These are not status for the ScrumMaster • They are commitments in front of peers

35. The sprint review • Team presents what it accomplished during the sprint • Typically takes the form of a demo of new features or underlying architecture • Informal • 2-hour prep time rule • No slides • Whole team participates • Invite the world

36. Sprint retrospective • Periodically take a look at what is and is not working • Typically 15–30 minutes • Done after every sprint • Whole team participates • ScrumMaster • Project Manager • Team • Possibly client and others

37. Start / Stop / Continue This is just one of many ways to do a sprint retrospective. Start doing Stop doing Continue doing Whole team gathers and discusses what they’d like to:

38. Details Product Backlog Sprint Backlog Iterative and incremental development Stand up meetings

39. Starting on the project? • Strategies: • Determine domain of the project • Determine scope • Decompose project challenge • Form subteams • Roles: • Meeting Chair • Secretary • Scrum Master • Project manager • Technology Manager • QA Manager • Database Admin • Client liaison • Tools: • Robert’s Rules of Order • IT Project tools

40. Assignments for next week • Read more about Agile Methods: Resources section on blackboard • Prepare 5 discussion questions (chair and secretary) • Determine team roles by the second class meeting • Establish schedule of Chair and Secretary assignments for remainder of semester • Decide on team collaboration environment (Version One, SharePoint, etc.) • Develop Initial Draft of Scope of Project • Plan on submitting the “Initial Project Plan” by the third class meeting

41. Resources • Readings (URLs and Documents on Agile Methods) on Course Blackboard Page • UNO Library – library.unomaha.edu • AISNET – aisnet.org (e-library) • Templates on Blackboard

42. Questions?

43. Client Introductions