Weekly Course Schedule – Spring 2016

INFOST 490 - 201 (Online)

Week 3 (February 8 – February 14)



Monday, February 8   (6:30 P.M. – 7:20 P.M., GoToMeeting)
Optional Session
Online Dropin Session
    On Monday evenings, I will be holding an Online Drop-In Session using the GoToMeeting platform. Students are invited to join us to discuss questions and issues concerning the class. This will serve as an opportunity to meet and start discussions with other students in the class. I expect this to be particularly useful during the early part of the semester when we are forming teams. Your experience will be best when you are using a headset. You may join the GoToMeeting session using this link.


Thursday, February 11   (3:00 P.M. – 5:00 P.M., NWQB-3472)
Optional Session
Office Hours
    Every Thursday afternoon, I will be holding Office Hours in my UWM office. Please feel free to drop by to ask a question, to discuss a problem, or just to say hello.


Sunday, February 14, @  11:55 P.M.
Weekly Assignments Deadline
Topics
  • Defining the Product Vision and Product Roadmap
  • Planning Releases and Sprints
  • Working Through the Day
  • Showcasing Work and Incorporating Feedback
  • Preparing the Release
Required Readings
  • Layton: Chapter 7
  • Layton: Chapter 8
  • Layton: Chapter 9
  • Layton: Chapter 10
  • Layton: Chapter 11
Required Recordings
Class Participation Assignments Due
  • User Stories vs. Use Cases
    Description: In the SOIS Systems Analysis class, we use Use Cases (and sometimes Data Flow Diagrams) to express user requirements. In this class, we will be following the methodology laid out by Layton in "Agile Project Management for Dummies". In this agile methodology, user requirements are expressed using User Stories. How do you see this User Stories approach as similar to or different than the more traditional approaches to expressing user requirements? What impact (if any) do you expect this new approach to have on your project?
    Submit to: Weekly Discussion Forum
  • Team Formation - Select (Step 2 of 4)
    Description: During this second week of team activities, our goal is to narrow the list of potential projects and rank them as potential opportunities. Potential projects may be attractive for a variety of reasons. Clients with whom some student or students have a strong relationship are attractive. Projects that would allow the team to demonstrate the skills identified for the project in the syllabus are attractive. Projects that are getting a lot of attention from potential student team members are attractive. At the conclusion of this week, we should have a short list of projects that we are pursuing and be ready to have staffing discussions with potential team members.
    Submit to: Team Formation Forum