1. Senior Projects Meeting 7 September 9, 2009

2. Agile Development Process The players are Product owner: sets priorities, owns in the sense of is responsible for, represents the stakeholders in their absence Scrum master: manages development process, removes blocks to success Team members: develop product Stakeholders: observe, advise. Includes the customer

3. Agile Process (2) Driven by the backlog, a list of tasks that lead to project completion Sprint review –Monthly meeting of Team members Stakeholders Product owner –Led by scrum master –Report on project status –Plan work for next sprint

4. Agile Process (3) Release –Usually every three months –Newest version of software –Evolved from previous release based on stakeholder feedback Key observation –Monthly sprints allow software requirements to evolve as stakeholders see the results of the development process.

5. Our Agile Process Team members: as you chose Product owner: chosen by team Scrum master: same as product owner, since our teams are small Stakeholders: all those not on the team including the instructor, acting as –The customers –The users –The evaluators

6. Our Agile Process (2) Sprint reviews and “code” releases coincide Approximately 40 WAGs per team member per sprint –WAGs are typically measured in person hours –WAGs appear in the backlog as measures of effort required for backlog entries –Backlog is the outline of tasks to be completed

7. Our Agile Process (3) Sprint reviews and “code” releases –Short team presentation –2 or 3 slides –Encourage stakeholder interaction –Depending on project and sprint number Prototypes of input and output screens Models of user interaction using Task/Action Grammar or GOMS Working code that is installable and testable against release cases and their equivalents

8. Our Agile Process (2) Sprint reviews and “code” releases occur on: –September 16 (Wednesday) –October 7 (Wednesday) –November 4 (Wednesday) –November 23 (Monday) –December 14 (Monday) Final code release

9. First “Code” Release Examples of possible “code” releases: Prototype of output screen (or screens) Prototype of input screen –Shows data necessary and its format and naming One or more classes with a driver program that can be used to test the methods of the class Sample data and its visualization

10. Friday Team Meetings For Friday, September 11, or as arranged differently 12:30 – 12:45 Vince, Mike, & Jim 12:50 – 1:05 AJ & Kristin 1:10 – 1:25 Tom, Tara & Kristin