CS 435 - Week 5 Lecture 2 - 2014-02-22
*****************************
PROJECT - FIRST 3 Milestones
*****************************
* what now happens with Team Meeting forms?
* directory, place team meeting forms
* KEEP naming these files with the date
in the PDF file's name
* yes, it will be a problem if I don't
see at-least-weekly-meetings (in general)
from here on out
==========================================
Milestone 1 - initial list of user stories
==========================================
* Homework 5 will NOT come out tonight
so you can get this by NEXT FRIDAY FEB. 28 11:59 pm
* what needs to be on GitHub project repo?
* updated team meeting forms, of course
* initial list of user stories -- for EACH
user story:
* short name
* user story (1-3 sentences, in client-
friendly language)
* ROUGH estimate, in hours or days (your
choice) of how long you think that
story will take to implement <--
for release-planning purposes!
==========================================
Milestone 2 - Iteration 1 Plan -
==========================================
* DUE by FRIDAY MAR. 7 11:59 pm
* need to know: WHICH user stories are
to be implemented in the first iteration
(I think a list of the names of those
stories should be fine)
* you've determined these in consultation
with the client...!
* AND the agreed-upon date that the first
iteration is to be completed.
* AND: I want a file -- testing-plan-1.txt
or testing-plan-1.pdf -- that DESCRIBES
how you plan to approach and attempt testing
for the first iteration
* hint: this better not be empty
* hint: think XP attitude...
* hint: better include: HOW will you handle UNIT testing?
* hint: better include: HOW will you handle ACCEPTANCE testing?
==========================================
Milestone 3 - Iteration 1
==========================================
* DUE by: the date you gave in Milestone 2
(keeping in mind: you need 3 iterations
by Friday, 11:59 pm of Week 15)
* code for running deliverable in the team's
project repo
* running!
* client can run it!
* does something useful! (little is OK!)
* implements the user stories you
said it would implement
* attempts at testing included!
* a README.txt file
* it needs to at LEAST include a clear
description of what I need to do to
run your deliverable
* significant deduction if I cannot
run your iteration...!
* a file testing-1.txt or testing-1.pdf
that describes how you actually accomplished
the testing for this iteration
* hint: better include: how DID you handle UNIT testing?
* hint: better include: how DID you handle ACCEPTANCE testing?
* your latest user stories should be
pushed along with your first iteration