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 |
-
Recorded commentary on Layton: Chapter 7
-
Recorded commentary on Layton: Chapter 8
-
Recorded commentary on Layton: Chapter 9
-
Recorded commentary on Layton: Chapter 10
-
Recorded commentary on Layton: Chapter 11
|
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
|