User Story Descriptions

ID:
1
2
3
4
5
6
7
8

10

11

12
13
14

15
16

17
18
19
20
21
 User Story Descriptions
Story:
The user must be able to access a product from the landing page.
The user must be able to access a project from the landing page.
The user must be able to access a sprint from the landing page.
The user must be able to view all user stories that belong to a selected sprint
The user must be able to move/copy stories from backlog to sprint or between sprints
The user must be able to select a story and view the details via the user-story page
The user must be able to sort the user stories without re-fetching data from server/database.
The user must by able to edit the user story details in a fast and easy fashion.
Using an interface object visible on the screen a listing of sprints is available for the currently selected project and on
selected to change the current sprint being worked on
From the list of stories available for this sprint, each story is selectable and will load the user story page for that story
can also be filtered on each column so that individual stories can be located easier
All available statuses for a task are visible for each user story and tasks are logically arranged to visually determine t
status for each task. Tasks are able to be dragged to different statuses to update that field
Using a max of one intermediate window, an interface object is visible to create a new story which will then load the
page for the newly created story
Groups of stories can be selected so that mass operations can be preformed with minimal user interactions
From the list of the task in the user interface a user can add, edit, delete, and view task
In a task a user is able to edit name, description, hours worked on task, acceptance Criteria and mark whether the tas
finished
User is able to reorder the tasks using drag and drop
Users can view the following information on the Story page: Story Name, Story ID, Stakeholder, Story Owner, Bus
Priority, Size and Description
User can Save and Revert all edited able information
User can login to the system using a username and password
User can retrieve forgotten account information
User can reconnect to the system if their connect has been lost
Status:
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started
Not Started

Not Started

Not Started

Not Started

Not Started
Not Started
Not Started

Not Started
Not Started

Not Started
Not Started
Not Started
Not Started
Not Started
 Project Backlog
ID: Task: Priority:
Landing Page

Create initial view for the hierarchy of

L1 0
Product/Project/backlog/sprint

Connect the database to the explorer view to enable

L2 0
the selection of products from the view
Connect the database to the explorer view to enable
L3 0
the selection of projects from the view

Connect the database to the explorer view to enable

L4 0
the selection of sprints from the view

Create inital view to display user stories and associated

L5 0
details

Implement drag and drop functionality between the user

L6 0
stories view (L5) and the hierarchy view (L1).

Create a link between user stories displayed in a sprint

L7 0
and their user-story page.

Implement client side sorting of user stories based on

L8 0
user story details using ajax.

Implement single click editing of user story details in the

L9 4
story list view (L5).

Update L1 view to meet feedback provided by project

L10 0
sponsor.

Update L5 view to meet feedback provided by project

L11 0
sponsor.

Populate storylist with data from the database when

L12 0
landing page is loaded.
Implement Ajax functionality on explorer view for
L13 0
product creation.
Implement Ajax functionality on explorer view for project
L14 0
creation.
Implement Ajax functionality on explorer view for sprint
L15 0
creation.
L16 Display percent completed for user stories. 0
Implement a 3 link column in the story list to move user
L17 5
stories to 3 specified sprints.
L18 Calculate the current sprint based on the current date. 0
Story Board
Implement an interface feature to select from a list of
S1 0
available sprints

S2 Update (S2) to include different products/projects 0

S3 Update User story view when new sprint is selected 0

S4 Create initial interface to display the list of User stories 0

Implement links so user story names open the User

S5 0
Story Page

Set up communication to Landing page so filtering

S6 0
information can be transferred

Create a search mechanism to find user stories based

S7 0
on story name

All available statuses which a task can fall under are

S8 0
visible in the User story grid

Initial layout provided of each task visually associated

S9 0
with its User story

Implement the dragging a dropping feature to update

S10 5
the status of the task in the database.

S11 Allow User Stories to be hidden in the interface 0

Create required statuses: Not Started, Impeded, WIP,

S12 0
Done
S13 Create an interface element to create a new user story 0

Add Story Name input element to new user story

S14 0
window

Set up intermediate window to link to new User Story

S15 0
page

S16 Allow groups of user stories to be deleted 0

S17 Allow groups of stories to be hidden 0

 Update S4 view to meet feedback provided by project
S18 0
sponsor.

Update S9 layout to meet feedback provided by project

S19 0
sponsor.

Implement the interface for dragging and dropping of

S20 0
tasks between statuses in storyboard partial

S21 Add Owner input element to new user story window 0

Selecting a new sprint from the sprint selection element
S22 0
will change the list of stories
Alter the storyboard interface to load values from the
S23 0
database.
Restrict dropping a draggable task to only its droppable
S24 0
target.
Maintain borders of table when tasks are dragged and
S25 0
dropped.
Fix dropping of task when mouse leaves droppable
S26 0
area.
S27 Visually separate tasks in the storyboard. 5
Load user stories in the display when a sprint is
S28 5
selected on the explorer page
User Story Page
Create initial view for the user stories that contains a list
U1 0
of tasks based on the story selected, the list is ordered.

Create a add buttton that will insert a new row into the
U2 0
task list.

Create a delete button that will remove the task from

U3 0
the task list.

Create an edit button that will pop up a dialog box with

U4 0
the editable fields of the task.

Create a checkbox inside the done column of the task

U5 0
list

Create initial text boxes for Acceptance criteria and

U6 0
Description on U1 view.

Implement drag and drop sorting of tasks in the task

U7 0
list.
Create a hidden field that will keep the track of the
U8 0
order upon drag and drop.
 Access the database to Display the following
information on the page: Story Name, Story ID,
U9 0
Stakeholder, Story Owner, Business Value, Priority,
Size and Description

Create a save button that will save story and task

U10 0
information to the database

Revert - If items have been changed the revert button

will changed everything back to original place.
U11 0
Should read refresh until a change is made, then it
should read revert.

Update U1 view to meet feedback provided by project

U12 0
sponsor.

Update U6 text boxes to meet feedback provided by

U13 0
project sponsor.

U14 Inline editing of table rows for Userstory partial 0

U15 Create a unique page for each user story. 5

Implement a drag and drop link in the leftmost column

U16 0
of the task list portion of the user story window.

Enable drag and drop on new task rows when they are
U17 0
created by the user.

U18 Restructure layout of the user story page. 0

Create popup window for task editting from the user

U19 0
story page.
Other Programming Tasks
O1 Create Login controller for Username and Password 4

O2 Create Storyboard controller and view 0

O3 Create User Story controller and view 0

O4 Create Landing controller and view 0

Implement method to retrieve forgotten login
O5 1
information

O6 Create a 'Reconnect' feature if connection is lost 1

O7 Implement multiple web-server capability 0

 Create initial interface element to contain all views
O8 0
within the system.
Update O8 interface to meet feedback provided by the
O9 0
project sponsor.
O10 Implement Minimize function in [Link] 0
O11 Implement Maximize function in [Link] 0
O12 Implement Restore function in [Link] 0

O13 Implement Pin function in [Link] 0

O14 Add pin button to [Link] 0

O15 Implementing layout for windows 0

O16 Create functional prototype for table row drag and drop 0

O17 Add min button to [Link] 0

O18 Add max button to [Link] 0

O19 Add restore button to [Link] 0

Explorer Window is located in left portion of the screen
O20 0
when landing page is loaded.
User Story Window is located in the right top portion of
O21 0
the screen when the window is displayed.
Story Board is located in the bottom right portion of the
O22 0
screen when the window is displayed.
Story List is located in the right portion of the screen
O23 0
when the landing page is loaded.

Fix Z-Ordering of Explorer Window, User Story Page,

O24 0
Story Board, and Story List

O25 Implement position for multiple minimized windows 0

Create a session object to keep track of who is logged
O26 4
on
Design / Documentation

E1 Identifying User Stories for Landing Page 0

E2 Identifying User Stories for Storyboard 0

E3 Identifying User Stories for User Story Page 0

E4 Identifying User Stories for Other Programming Tasks 0

E5 Create Tasks for Landing Page User Stories 0

E6 Create Tasks for Storyboard User Stories 0

E7 Create Tasks for User Story Page User Stories 0

Create Tasks for Other Programming Tasks User

E8 0
Stories
E9 Design the initial version of the software system 0

E10 Develop initial version of class diagrama 0

E11 Develop initial A3 Architecture Diagram 0

Testing
T1 Generate test plan 0
T2 Test new features from sprint (Each Sprint) 0
T3 Regression test old features (Each Sprint) 0
T4 UAT for Performance Characteristics (Each Sprint) 0
T5 UAT for Usability Characteristics (Each Sprint) 0
Database
D1 Set up physical server 0
D2 Develop database schema 0

D3 Set up CVS/Subversion Revision System 0

Create Product table in the database with defined
D4 0
product attributes.

Create Project table in the database with defined

D5 0
project attributes.

Create Sprint table in the database with defined sprint

D6 0
attributes.

D7 Populate Fixtures with valid record data. 0

Web
W1 Install Web-server on Project Environment 0
W2 Implement Scripts to Update Web-site Automatically 0

Feedback
Make storylist same height as explorer window when
F1 5
application loads.
F2 Implement loading status display during loading. 5
F3 Rearrange edit task window to go horizontal. 5
F4 Setup intial size of edit task window. 5
Implement popup of user story window when add new
F5 5
story button has been pressed.

F6 Restrict size of move sprint in storylist 4

F7 Implement age instead of modified date in storylist 4

F8 Restrict size of age field in storylist 4

Implement scrollbar for overflow in storylist and

F9 5
storyboard.

Author: Dustin Keller

 Project Backlog
Acceptance Criteria: Status: Story ID:

Selection of a Product, project, backlog, and sprint are available through

a hierarchy view. Selection of user stories and tasks are available
Completed 1
through an associated view once a sprint is selected. Hierarchy of
objects must be maintained through the views.
Products can be selected from a hierarchical view (L1). Products exist at
Completed 1
the highest level in the hierarchy.
Projects can be selected from a hierarchical view (L1). Projects belong
Completed 2
to products in the hierarchy.

Sprints can be selected from a hierarchical view (L1). Sprints belong to

Completed 3
projects in the hierarchy. The backlog belongs to the project as well.

User stories can be selected from the view. The view must only display
user stories that belong to the selected sprint in the hierarchical view Completed 4
(L1).

User stories can be dragged and dropped into any sprint that belongs to
the same project as the current selected sprint. If the user story is
dragged from the backlog, it will be copied to the dropped sprint. If the Cancelled 5
user story is dragged from any other sprint, it will be removed from the
selected sprint and placed in the dropped sprint.

User stories can be double clicked from the user stories view (L5) and
Completed 6
their user-story page will be displayed.
User stories can be sorted/filtered based on user story details displayed
in the user stories view (L5). The sorting will not re-fetch data from the Completed 7
database (client side sorting).
User story details can be edited from the user stories view (L5) without
going to the user-story page. Only details that can be changed based on Completed 8
user privilages will be editable.
Selection of a Product, project, backlog, and sprint are available through
a hierarchy view. Selection of user stories and tasks are available
Completed 1
through an associated view once a sprint is selected. Hierarchy of
objects must be maintained through the views.
User stories can be selected from the view. The view must only display
user stories that belong to the selected sprint in the hierarchical view Completed 4
(L1).

The storylist should display the current stories for the selected sprint. Completed N/A
Products will be updated in the hierarchical view (L1) without a refresh
Cancelled 1
of the page.
Projects will be updated in the hierarchical view (L1) without a refresh of
Cancelled 1
the page.
Sprints will be updated in the hierarchical view (L1) without a refresh of
Cancelled 1
the page.
Number of tasks completed over total tasks for the given story. Completed N/A
A user story can be moved into the backlog, current sprint +1, and
Completed N/A
current sprint -1 from the column.
The current date is stored so that there is a knowledge of the current
Completed N/A
sprint for each project.

The list of sprints is viewable in an interface feature available on the

Cancelled 9
storyboard.
Projects and Products not immedietly associated with the currently
selected sprint are now visible in the interface. The new values are
Cancelled 9
selectable and the required information about the new sprint being
viewed is updated within the storyboard.
The list of sprints (S4) is updated and all functionality is retained when
Completed 9
the viewable sprint is updated.
All of the user stories associated with a sprint are viewable within the
Completed 10
storyboard.
The correct user story page is opened when the user selects the story
Completed 10
name located in the list (S4).
When the list of user stories is filtered on the landing page (L8) the list of
user stories on the storyboard exactly matches the updated list on the
Cancelled 10
landing page. This feature will only happen when the correct property is
set to allow it.
The list of stories viewable in the interface is reduced to only the stories
that match the searched criteria. When the search field is cleared the Cancelled 10
search will return all the user stories.
Without using any keystrokes or mouse clicks, each of the available
Completed 11
statuses that a task can potentially be in are visible on the interface.

Without using any keystrokes or mouse clicks the status of a particular

Completed 11
task associated with a story is obvious to anybody viewing the interface.

Using drag and drop functionality the status of a particular task can be
Completed 11
changed by moving its location on the interface.
When the user story is hidden it is either no longer visible in the list of
user stories, or it is minimized into a smaller item to take us less space.
Cancelled 11
If the story disapears from the list it will re-appear if the list is filtered or
re-retrieved from the database.
The available statuses on the storyboard are exactly the options written
Completed 11
in (S12).
By clicking or otherwise interacting with the element a new interface is
Completed 12
opened to allow the creation of a new user story.

The interface window contains fields which will retrieve all the
Completed 12
information which is required to create even the most basic user story.

When the complete operation is performed in the interface from (S14),

the required fields are validated and if no problems are encountered the
new user story is created and the new user story page is linked to. If a Completed 12
problem is encountered an explanation is displayed to the user to help
them correct the problem.
All marked user stories are deleted from the system when the delete
functionality is performed. The list of user stories is updated and none of Cancelled 13
the deleted stories appears in the list.
All marked user stories are hidden from the user using the same
Cancelled 13
functionality as in (S11).
All of the user stories associated with a sprint are viewable within the
Completed 10
storyboard.

Without using any keystrokes or mouse clicks the status of a particular

Completed 11
task associated with a story is obvious to anybody viewing the interface.

Each status can be dragged to another status cell in its own row. When
dropped on the cell the task is visually moved from the original cell to the Completed N/A
new cell.
User can input the name of the story's owner in the new story window
Completed 12
before the story is created.
The sprints are selectable so that the sprints can be changed using the
Cancelled 9
element.
When the storyboard window is displayed all of the stories for the
Completed N/A
currently selected sprint are visible in the scrollable table.
The task can only be dropped in its droppable target. Completed N/A

Table borders are always visable before, during and after drag and drop. Completed N/A
When mouse leaves the droppable area nothing happens and the state
Completed N/A
before the drag is maintained.
Tasks are visually distinguishable. Completed N/A
Storyboard contains user stories of selected sprint. Completed N/A

Inside the Story View there will be a list of tasks that are order by their
Completed 14
database ordering.

By clicking a button a user is able to add a task to the list. The program
will assign it an order and TaskID, the first item in the list will be assigned
Completed 14
order 1 and if there are already items in the list then it will be assigned
the highest task plus one.
Selecting a view and clicking delete will remove the list item. The list will
update without refreshing. Each task after that item will have there order
Completed 14
decremented by one or more depending on how many task have been
deleted. Only delete the task if save is selected.

A user can click inside the list item to edit any of the editable fields. completed 14

There should be a checkbox for the user to click to have the task shown
up as done. Done cannot be clicked if lower numbered tasks haven’t Completed 15
already finished. To Be Verified(TBV)
There should two edit boxes in the Story View; one to include
acceptance criteria tasks and the other one to include description of the
Completed 15
task. When a user clicks a task these should be automatically
populated. User can input text in each box.
User should be able drag a task in the task list. The task that is being
Completed 16
dragged should be visible.
Dragging then dropping a task in the task list should automatically
Completed 16
reorder the tasks.
The following information will be displayed in the story view: Story Name,
Story ID, Stakeholder, Story Owner, Business Value, Priority, Size and Completed 17
Description

User can click save button to save all the information that has been
changed in the tasks list. The save button will be grayed out if nothing Completed 18
has been saved.
If the user does not like his changes then the user is able to click revert
and it will undo all the changed before last save. If no tasks have been
changed that warrant database change then the button will read refresh. Completed 18
Refresh will query the database and refresh the page if any changes
occur.
Inside the Story View there will be a list of tasks that are order by their
Completed 14
database ordering.
There should two edit boxes in the Story View; one to include
acceptance criteria tasks and the other one to include description of the
Completed 15
user story. When a user clicks a task these should be automatically
populated. User can input text in each box.
All fields are editable through one click editing in the task list on the User
Completed 14
story page.
Able to access manipuilate a user story from a unique url that specifies
Completed N/A
the user story id in the url tag.

A row in the task list and be sorted by draging and dropping the row
Completed N/A
using the leftmost column.

New task rows have the ability to be drag and drop sorted. Completed N/A

Story requestor, owner, developer must be displayed as names in a drop

down menu. Task name is displayed for 50 characters in the task list.
The basic user story details need to be displayed along the top of the
Completed N/A
page. The id must be read only, the status and proirity need to be drop
downs. Vertical resize of description and acceptance criteria. Decrease
size of font.
When edit button is clicked, popup window with all task details is
Completed N/A
available to edit the task.

The user cannot use the system until they enter a valid user name and
Completed 19
password.
a web page with the title Storyboard page will be accessible from a web
Completed N/A
browser.
a web page with the title User Story page will be accessible from a web
Completed N/A
browser.
a web page with the title Landing Page will be accessible from a web
Completed N/A
browser.
the user will be able to retrieve their password by having it sent to their
Cancelled 20
email or another secure means
if the last timed synchronization with the server times out the status will
Cancelled 21
be displayed to the user.
Setup an alternate server machine and synchronize the database
Cancelled N/A
between the two.
All other views exist within the bounds of the element. Completed N/A
All other views exist within the bounds of the element. Views can be
Completed N/A
moved and closed within the element.
Windows within the application can be minimized. Completed N/A
Windows within the application can be maximized. Completed N/A
Windows within the application can be restored to their last position. Completed N/A
A buttons appears on the window titlebar that when clicked changes the
dialog so that the user can no longer drag or resize the window. And Completed N/A
when reclicked the window will be draggable and resizeable.
A button exists in the upper right corner of the windows that allows the
Completed N/A
window to be pinned.
Each window exists in its own portion of the screen with proper sizes and
positions. As well as changes size respectively when the browser is Completed N/A
resized.
Basic functionality is created and demonstrated to the customer to prove
Completed N/A
that implemenation into the project is possible.
A button exists in the upper right corner of the windows that allows the
Completed N/A
window to be minimized.
A button exists in the upper right corner of the windows that allows the
Completed N/A
window to be maximized.
A button exists in the upper right corner of the windows that allows the
Completed N/A
window to be restored.
The explorer window appears in the top left portion of the screen when
Completed N/A
landing page is loaded
The user story window appears in the right top portion of the screen
Completed N/A
whenever the window it is displayed.
The story board window appears in the bottom right portion of the screen
Completed N/A
when the window is displayed
The story list window appears in the right portion of the screen when the
Completed N/A
landing page is loaded
Windows appear above other windows whenever they are selected, by
clicking anywhere within the window including the titlebar as well as Completed N/A
while dragging the window.
Minimized windows have a specific position on bottom of application
Completed N/A
based on other minimized windows.
Session object is created and keeps track of what user is logged in. User
Completed N/A
cannot get into program without being logged in.

Basic functionality of the interface is obvious based on user story

descriptions. Uninformed user can tell what the landing page interface Completed N/A
should be used for simply by reading the stories.
Basic functionality of the interface is obvious based on user story
descriptions. Uninformed user can tell what the storyboard interface Completed N/A
should be used for simply by reading the stories.
Basic functionality of the interface is obvious based on user story
descriptions. Uninformed user can tell what the user story page Completed N/A
interface should be used for simply by reading the stories.
Extra functionality is obvious to an uninformed user by reading the
Completed N/A
stories.
All points on the project proposal under the Landing Page section of the
Goals for the project are completely covered by at least one Landing Completed N/A
Page task.
All points on the project proposal under the Storyboard section of the
Goals for the project are completely covered by at least one Storyboard
Completed N/A
task. Visual task status should be obvious to the user to allow for easy
drag and drop functionality.
All points on the project proposal under the User Story Page section of
the Goals for the project are completely covered by at least one Completed N/A
Storyboard task.
All points on the project proposal not covered by the other three sections
Completed N/A
are completely covered by at least one Storyboard task.
All intended functionality and non-functional characteristics have been
Completed N/A
modeled within the design of the overall system.
All model, view, controller, and supporting objects will be displayed
within the diagram. All relationships between the objects will be Completed N/A
represented on the diagram as well.

Entire system functionality along with flow control is summed up in a one

page document on a letter size sheet of paper. Complete coverage of Completed N/A
the User Stories can be explained on a basic level by the document.

Web Application should be able to access/query the Database. Completed N/A

The database schema has been created as defined by project sponsor. Completed N/A
Be able to checkout, update, and commit files for the web application via
Completed N/A
CVS/SVN from a remote machine.
Product table exists within the database and contains all necessary
Completed 1
attributes for correct application functionality.
Project table exists within the database and contains all necessary
attributes for correct application functionality. A project must belong to at Completed 2
least one product.
Sprint table exists within the database and contains all necessary
attributes for correct application functionality. A sprint must belong to
Completed 3
only one project. A special sprint named backlog must exist, which is a
collection of all tasks for the project.
All database tables will contain at least 10-20 valid records. Completed

Be able to open a web browser and input the URL and view the web
Completed N/A
application.
The script should populate a website template whose visual appearance
can be changed without affecting the data displayed. The script should
create HTML links for each relevant document in the public_html Completed N/A
directory. It should also change the permissions of all files linked to be
readable by any group (i.e. User, Group, Other)

Completed N/A
Completed N/A
Completed N/A
Completed N/A
Completed N/A

The row to move a sprint stays the same size and is only large enough
Completed N/A
to contains the element which changes which sprint the story is in.

The number of days since the story was last updated is displayed in the
Completed N/A
table to the user.
The size field is only large enough to fit 3 digits along with any text on a
Completed N/A
single line.
The storylist/storyboard are scrollable independent of the size of the
Completed N/A
window.
Priorities:

Highest = 5

Lowest = 1

Completed / Not
Needed Yet = 0

Status:

Completed

In Progress

Not Started

Cancelled

Split
 Sprint 6 - Ba
Task: ID #: Assigned To: Priority: Est Time:

Implement single click editing of user story details in the

L9 Dustin 4 360
story list view (L5).

Implement the dragging a dropping feature to update the

S10 Nick 5 120
status of the task in the database.
Create a unique page for each user story. U15 Nick 5 30
Implement a 3 link column in the story list to move user
L17 Chad 5 300
stories to 3 specified sprints.
Visually separate tasks in the storyboard. S27 Dustin 5 30
Create Login controller for Username and Password O1 Chad 4 60

Create a session object to keep track of who is logged on O26 Chad 4 30

Make storylist same height as explorer window when
F1 Nick 5 5
application loads.
Implement loading status display during loading. F2 Mike 5 90
Rearrange edit task window to go horizontal. F3 Mike 5 30
Setup intial size of edit task window. F4 Nick 5 60
Implement popup of user story window when add new
F5 Mike 5 60
story button has been pressed.
Restrict size of move sprint in storylist F6 Dustin 4 30

Implement age instead of modified date in storylist F7 Dustin 4 30

Restrict size of age field in storylist F8 Dustin 4 30

Implement scrollbar for overflow in storylist and
F9 Dustin 5 45
storyboard.
Load user stories in the display when a sprint is selected
S28 Nick 5 60
on the explorer page
 Sprint 6 - Backlog (4/29/08 - 5/12/08)
Est End Date: Actual Time: Start Date: End Date:

5/6/2008 377 5/1/2008 5/6/2008

5/7/2008 100 5/1/2008 5/6/2008

5/5/2008 16 5/5/2008 5/5/2008

4/28/2008 500 4/24/2008 5/6/2008

5/6/2008 44 5/2/2008
5/7/2008 95 4/29/2008 5/6/2008

5/7/2008 30 5/5/2008 5/5/2008

5/5/2008 5 5/5/2008 5/5/2008

5/6/2008 72 5/1/2008 5/4/2008
5/6/2008
5/5/2008 6 5/5/2008 5/5/2008
5/6/2008 30 5/4/2008 5/4/2008

5/6/2008 7 5/1/2008 5/1/2008

5/6/2008 57 5/1/2008 5/6/2008

5/6/2008 7 5/1/2008 5/1/2008

5/6/2008 69 5/1/2008 5/6/2008

5/6/2008 90 5/5/2008 5/5/2008

 Acceptance Criteria: Status: Milestone ID:
User story details can be edited from the user stories view (L5) without going
to the user-story page. Only details that can be changed based on user Completed
privilages will be editable.
Using drag and drop functionality the status of a particular task can be
Completed
changed by moving its location on the interface.
Able to access manipuilate a user story from a unique url that specifies the
Completed
user story id in the url tag.
A user story can be moved into the backlog, current sprint +1, and current
Completed
sprint -1 from the column.
Tasks are visually distinguishable. Completed
The user cannot use the system until they enter a valid user name and
Completed
password.
Session object is created and keeps track of what user is logged in. User
Completed
cannot get into program without being logged in.
#REF!
Completed
Completed
Completed
Completed
The row to move a sprint stays the same size and is only large enough to
Completed
contains the element which changes which sprint the story is in.
The number of days since the story was last updated is displayed in the table
Completed
to the user.
The size field is only large enough to fit 3 digits along with any text on a
Completed
single line.
The storylist/storyboard are scrollable independent of the size of the window. Completed

Storyboard contains user stories of selected sprint. Completed

 Sprint 5 - Ba
Task: ID #: Assigned To: Priority: Est Time:

Create a add buttton that will insert a new row into the
U2 Mike 0 60
task list.

Create a delete button that will remove the task from the
U3 Mike 0 60
task list.

Create a save button that will save story and task

U10 Mike 0 200
information to the database

Create a checkbox inside the done column of the task list U5 Mike 0 60

Revert - If items have been changed the revert button will

changed everything back to original place.
U11 Mike 0 360
Should read refresh until a change is made, then it
should read revert.

Create a hidden field that will keep the track of the order
U8 Mike 0 90
upon drag and drop.
Explorer Window is located in left portion of the screen
O20 Nick 0 30
when landing page is loaded.
User Story Window is located in the right top portion of
O21 Nick 0 30
the screen when the window is displayed.
Story Board is located in the bottom right portion of the
O22 Nick 0 30
screen when the window is displayed.
Story List is located in the right portion of the screen
O23 Nick 0 30
when the landing page is loaded.
Implement links so user story names open the User Story
S5 Dustin 0 30
Page
Implement position for multiple minimized windows O25 Nick 0 60
Maintain borders of table when tasks are dragged and
S25 Dustin 0 15
dropped.
Enable drag and drop on new task rows when they are
U17 Dustin 0 60
created by the user.
Create a link between user stories displayed in a sprint
L7 Dustin 0 30
and their user-story page.

Implement single click editing of user story details in the

L9 Dustin 4 30
story list view (L5).

Update User story view when new sprint is selected S3 Nick 0 90

Implement links so user story names open the User Story
S5 Dustin 0 30
Page
Implement the dragging a dropping feature to update the
S10 5
status of the task in the database.
Create an interface element to create a new user story S13 Mike 0 30

Add Story Name input element to new user story window S14 Mike 0 30

Set up intermediate window to link to new User Story

S15 Mike 0 30
page

Add Owner input element to new user story window S21 Mike 0 20

Create a unique page for each user story. U15 5

Fix dropping of task when mouse leaves droppable area. S26 Dustin 0 100

Restructure layout of the user story page. U18 Mike 0 100

Create popup window for task editting from the user story
U19 Mike 0 240
page.
Display percent completed for user stories. L16 Dustin 0 30
Implement a 3 link column in the story list to move user
L17 Chad 5 300
stories to 3 specified sprints.
Calculate the current sprint based on the current date. L18 Chad 0 60
Visually separate tasks in the storyboard. S27 Chad 5 120
Create Login controller for Username and Password O1 Nick 4 60

Implement method to retrieve forgotten login information O5 1

Create a session object to keep track of who is logged on O26 4

 Sprint 5 - Backlog (4/15/08 - 4/28/08)
Est End Date: Actual Time: Start Date: End Date:

4/21/2008 63 4/15/2008 4/20/2008

4/21/2008 112 4/15/2008 4/20/2008

4/21/2008 143 4/15/2008 4/21/2008

4/21/2008 70 4/15/2008 4/21/2008

4/28/2008 331 4/15/2008 4/27/2008

4/21/2008 195 4/15/2008 4/28/2008

4/28/2008 32 4/15/2008 4/16/2008

4/28/2008 32 4/15/2008 4/16/2008

4/28/2008 32 4/15/2008 4/16/2008

4/28/2008 32 4/15/2008 4/16/2008

4/22/2008 4 4/15/2008 4/24/2008

4/28/2008 51 4/15/2008 4/17/2008

4/19/2008 7 4/15/2008 4/17/2008

4/22/2008 124 4/15/2008 4/23/2008

4/22/2008 72 4/17/2008 4/24/2008

4/22/2008 211 4/25/2008 N/A

4/28/2008 61 4/20/2008 4/20/2008

4/24/2008 4 4/25/2008 4/25/2008

 N/A

4/28/2008 20 4/28/2008 4/28/2008

4/28/2008 20 4/28/2008 4/28/2008

4/28/2008 20 4/28/2008 4/28/2008

4/28/2008 20 4/28/2008 4/28/2008

N/A

4/28/2008 87 4/20/2008 4/23/2008

4/20/2008 222 4/19/2008 4/20/2008

4/28/2008 315 4/20/2008 4/27/2008

4/19/2008 55 4/17/2008 4/28/2008
4/28/2008 360 4/24/2008 N/A

4/27/2008 65 4/25/2008 4/26/2008

4/27/2008 15 4/24/2008 N/A
4/29/2008 4/29/2008 N/A

N/A

N/A
 Acceptance Criteria: Status: Milestone ID:
By clicking a button a user is able to add a task to the list. The program will
assign it an order and TaskID, the first item in the list will be assigned order 1
Completed
and if there are already items in the list then it will be assigned the highest
task plus one.
Selecting a view and clicking delete will remove the list item. The list will
update without refreshing. Each task after that item will have there order
Completed
decremented by one or more depending on how many task have been
deleted. Only delete the task if save is selected.
User can click save button to save all the information that has been changed
in the tasks list. The save button will be grayed out if nothing has been Completed
saved.
There should be a checkbox for the user to click to have the task shown up
as done. Done cannot be clicked if lower numbered tasks haven’t already Completed
finished. To Be Verified(TBV)

If the user does not like his changes then the user is able to click revert and it
will undo all the changed before last save. If no tasks have been changed
Completed
that warrant database change then the button will read refresh. Refresh will
query the database and refresh the page if any changes occur.

Dragging then dropping a task in the task list should automatically reorder the
Completed
tasks.
The explorer window appears in the top left portion of the screen when
Completed
landing page is loaded
The user story window appears in the right top portion of the screen
Completed
whenever the window it is displayed.
The story board window appears in the bottom right portion of the screen
Completed
when the window is displayed
The story list window appears in the right portion of the screen when the
Completed
landing page is loaded
The correct user story page is opened when the user selects the story name
Completed
located in the list (S4).
Minimized windows have a specific position on bottom of application based
Completed
on other minimized windows.
Table borders are always visable before, during and after drag and drop. Completed

New task rows have the ability to be drag and drop sorted. Completed
User stories can be double clicked from the user stories view (L5) and their
Completed
user-story page will be displayed.
User story details can be edited from the user stories view (L5) without going
to the user-story page. Only details that can be changed based on user Completed
privilages will be editable.
The list of sprints (S4) is updated and all functionality is retained when the
Completed
viewable sprint is updated.
The correct user story page is opened when the user selects the story name
Completed
located in the list (S4).
Using drag and drop functionality the status of a particular task can be
Completed
changed by moving its location on the interface.
By clicking or otherwise interacting with the element a new interface is
Completed
opened to allow the creation of a new user story.
The interface window contains fields which will retrieve all the information
Completed
which is required to create even the most basic user story.
When the complete operation is performed in the interface from (S14), the
required fields are validated and if no problems are encountered the new user
story is created and the new user story page is linked to. If a problem is Completed
encountered an explanation is displayed to the user to help them correct the
problem.
User can input the name of the story's owner in the new story window before
Completed
the story is created.
Able to access manipuilate a user story from a unique url that specifies the
Completed
user story id in the url tag.
When mouse leaves the droppable area nothing happens and the state
Completed
before the drag is maintained.

Story requestor, owner, developer must be displayed as names in a drop

down menu. Task name is displayed for 50 characters in the task list. The
basic user story details need to be displayed along the top of the page. The Completed
id must be read only, the status and proirity need to be drop downs. Vertical
resize of description and acceptance criteria. Decrease size of font.

When edit button is clicked, popup window with all task details is available to
Completed
edit the task.
Number of tasks completed over total tasks for the given story. Completed
A user story can be moved into the backlog, current sprint +1, and current
Completed
sprint -1 from the column.
The current date is stored so that there is a knowledge of the current sprint
Completed
for each project.
Tasks are visually distinguishable. Completed
The user cannot use the system until they enter a valid user name and
Completed
password.
the user will be able to retrieve their password by having it sent to their email
Cancelled
or another secure means
Session object is created and keeps track of what user is logged in. User
Completed
cannot get into program without being logged in.
 Sprint 4 - B
Task: ID #: Assigned To: Priority: Est Time:

Create a add buttton that will insert a new row into the
U2 Mike 0 120
task list.

Create a delete button that will remove the task from the
U3 Mike 0 80
task list.

Create an edit button that will pop up a dialog box with

U4 Mike 0 120
the editable fields of the task.

Create a save button that will save story and task

U10 Mike 0 240
information to the database

Implement drag and drop sorting of tasks in the task list. U7 Dustin 0 120

Create a checkbox inside the done column of the task list U5 Mike 0 60

Revert - If items have been changed the revert button will

changed everything back to original place.
U11 Mike 0 240
Should read refresh until a change is made, then it
should read revert.

Create a hidden field that will keep the track of the order
U8 Mike 0 120
upon drag and drop.
Add pin button to [Link] O14 Nick 0 60
Explorer Window is located in left portion of the screen
O20 Nick 0 30
when landing page is loaded.
User Story Window is located in the right top portion of
O21 Nick 0 30
the screen when the window is displayed.
Story Board is located in the bottom right portion of the
O22 Nick 0 30
screen when the window is displayed.
Story List is located in the right portion of the screen
O23 Nick 0 30
when the landing page is loaded.

Fix Z-Ordering of Explorer Window, User Story Page,

O24 Nick 0 360
Story Board, and Story List
Populate Fixtures with valid record data. D7 Nick 0 360
Implement links so user story names open the User Story
S5 Dustin 0 120
Page
Alter the storyboard interface to load values from the
S23 Dustin 0 360
database.
Populate storylist with data from the database when
L12 Dustin 0 200
landing page is loaded.
Implement Ajax functionality on explorer view for product
L13 Chad 0 180
creation.
Implement Ajax functionality on explorer view for project
L14 Chad 0 60
creation.
Implement Ajax functionality on explorer view for sprint
L15 Chad 0 60
creation.
Implement Minimize function in [Link] O10 Chad 0 180
Implement Maximize function in [Link] O11 Chad 0 120
Implement position for multiple minimized windows O25 Nick 4 120
Restrict dropping a draggable task to only its droppable
S24 Dustin 4 60
target.
Maintain borders of table when tasks are dragged and
S25 Dustin 4 60
dropped.
Implement a drag and drop link in the leftmost column of
U16 Dustin 4 30
the task list portion of the user story window.
Enable drag and drop on new task rows when they are
U17 Dustin 4 100
created by the user.
 Sprint 4 - Backlog (4/1/08 - 4/14/08)
Est End Date: Actual Time: Start Date: End Date:

4/14/2008 400 4/6/2008 N/A

4/14/2008 73 4/6/2008 N/A

4/14/2008 168 4/6/2008 4/12/2008

4/14/2008 471 4/12/2008 N/A

4/14/2008 97 4/2/2008 4/12/2008

4/14/2008 30 4/12/2008 N/A

4/14/2008 0 N/A N/A

4/14/2008 0 N/A N/A

4/14/2008 60 4/6/2008 4/8/2008

4/14/2008 30 N/A N/A

4/14/2008 0 N/A N/A

4/14/2008 0 N/A N/A

4/14/2008 0 N/A N/A

4/14/2008 288 4/6/2008 4/8/2008

4/14/2008 287 4/12/2008 4/12/2008

4/14/2008 0 N/A N/A

4/7/2008 110 4/2/2008 4/5/2008

4/14/2008 19 4/11/2008 4/11/2008

4/14/2008 90 4/3/2008 N/A

4/14/2008 15 4/9/2008 N/A

4/14/2008 15 4/9/2008 N/A

4/11/2008 154 4/3/2008 4/14/2008
4/11/2008 140 4/3/2008 4/14/2008
4/14/2008 60 4/6/2008 N/A

4/14/2008 34 4/14/2008 4/14/2008

4/14/2008 0 N/A N/A

4/14/2008 25 4/14/2008 4/14/2008

4/14/2008 0 N/A N/A

 Acceptance Criteria: Status: Milestone ID:
By clicking a button a user is able to add a task to the list. The program will
assign it an order and TaskID, the first item in the list will be assigned order 1
Completed
and if there are already items in the list then it will be assigned the highest
task plus one.
Selecting a view and clicking delete will remove the list item. The list will
update without refreshing. Each task after that item will have there order
Completed
decremented by one or more depending on how many task have been
deleted. Only delete the task if save is selected.

A user can click inside the list item to edit any of the editable fields. completed

User can click save button to save all the information that has been changed
in the tasks list. The save button will be grayed out if nothing has been Completed
saved.
User should be able drag a task in the task list. The task that is being
Completed
dragged should be visible.
There should be a checkbox for the user to click to have the task shown up
as done. Done cannot be clicked if lower numbered tasks haven’t already Completed
finished. To Be Verified(TBV)

If the user does not like his changes then the user is able to click revert and it
will undo all the changed before last save. If no tasks have been changed
Completed
that warrant database change then the button will read refresh. Refresh will
query the database and refresh the page if any changes occur.

Dragging then dropping a task in the task list should automatically reorder the
Completed
tasks.
A button exists in the upper right corner of the windows that allows the
Completed
window to be pinned.
The explorer window appears in the top left portion of the screen when
Completed
landing page is loaded
The user story window appears in the right top portion of the screen
Completed
whenever the window it is displayed.
The story board window appears in the bottom right portion of the screen
Completed
when the window is displayed
The story list window appears in the right portion of the screen when the
Completed
landing page is loaded
Windows appear above other windows whenever they are selected, by
clicking anywhere within the window including the titlebar as well as while Completed
dragging the window.
All database tables will contain at least 10-20 valid records. Completed
The correct user story page is opened when the user selects the story name
Completed
located in the list (S4).
When the storyboard window is displayed all of the stories for the currently
Completed
selected sprint are visible in the scrollable table.
The storylist should display the current stories for the selected sprint. Completed
Products will be updated in the hierarchical view (L1) without a refresh of the
Cancelled
page.
Projects will be updated in the hierarchical view (L1) without a refresh of the
Cancelled
page.
Sprints will be updated in the hierarchical view (L1) without a refresh of the
Cancelled
page.
Windows within the application can be minimized. Completed
Windows within the application can be maximized. Completed
Minimized windows have a specific position on bottom of application based
Completed
on other minimized windows.
The task can only be dropped in its droppable target. Completed

Table borders are always visable before, during and after drag and drop. Completed
A row in the task list and be sorted by draging and dropping the row using the
Completed
leftmost column.
New task rows have the ability to be drag and drop sorted. Completed
 Sprint 3 - Ba
Task: ID #: Assigned To: Priority: Est Time:
Connect the database to the explorer view to enable the
L2 Chad 0 60
selection of products from the view
Connect the database to the explorer view to enable the
L3 Chad 0 60
selection of projects from the view
Connect the database to the explorer view to enable the
L4 Chad 0 60
selection of sprints from the view

Create a add buttton that will insert a new row into the
U2 Mike 0 120
task list.

Create a delete button that will remove the task from the
U3 Mike 0 120
task list.

Create an edit button that will pop up a dialog box with

U4 Mike 0 120
the editable fields of the task.

Create a checkbox inside the done column of the task list U5 Mike 0 120

Implement drag and drop sorting of tasks in the task list. U7 Dustin 0 240

Create a save button that will save story and task

U10 Mike 0 360
information to the database

Inline editing of table rows for Userstory partial U14 Mike 0 240
Implement Minimize function in [Link] O10 Chad 0 90
Implement Maximize function in [Link] O11 Chad 0 120
Implement Restore function in [Link] O12 Chad 0 30

Implement Pin function in [Link] O13 Nick 0 300

Add pin button to [Link] O14 Nick 0 90

Add min button to [Link] O17 Chad 0 60

Add max button to [Link] O18 Chad 0 60

Add restore button to [Link] O19 Chad 0 60

Implementing layout for windows O15 Nick 0 300

Create functional prototype for table row drag and drop O16 Dustin 0 300
Implement the interface for dragging and dropping of
S20 Dustin 0 240
tasks between statuses in storyboard partial
 Sprint 3 - Backlog (3/11/08 - 3/31/08)
Est End Date: Actual Time: Start Date: End Date:

3/30/2008 60 3/23/2008 3/30/2008

3/30/2008 30 3/23/2008 3/30/2008

3/30/2008 30 3/23/2008 3/30/2008

3/24/2008 180 3/16/2008 N/A

3/24/2008 180 3/16/2008 N/A

3/24/2008 180 3/16/2008 N/A

3/24/2008 180 3/16/2008 N/A

3/30/2008 230 3/22/2008 N/A

3/30/2008 300 3/22/2008 N/A

3/24/2008 3/16/2008 3/23/2008

338
3/20/2008 87 3/13/2008 3/24/2008
3/20/2008 90 3/13/2008 N/A
3/20/2008 38 3/13/2008 3/24/2008

3/10/2008 184 3/12/2008 3/12/2008

3/30/2008 60 3/13/2008 N/A

3/30/2008 60 3/28/2008 3/29/2008

3/30/2008 30 3/28/2008 3/29/2008

3/30/2008 30 3/28/2008 3/29/2008

3/31/2008 360 3/28/2008 N/A

3/21/2008 412 3/11/2008 3/20/2008

3/30/2008 200 3/21/2008 3/31/2008
 Acceptance Criteria: Status: Milestone ID:
Products can be selected from a hierarchical view (L1). Products exist at the
Completed
highest level in the hierarchy.
Projects can be selected from a hierarchical view (L1). Projects belong to
Completed
products in the hierarchy.
Sprints can be selected from a hierarchical view (L1). Sprints belong to
Completed
projects in the hierarchy. The backlog belongs to the project as well.
By clicking a button a user is able to add a task to the list. The program will
assign it an order and TaskID, the first item in the list will be assigned order 1
Completed
and if there are already items in the list then it will be assigned the highest
task plus one.
Selecting a view and clicking delete will remove the list item. The list will
update without refreshing. Each task after that item will have there order
Completed
decremented by one or more depending on how many task have been
deleted. Only delete the task if save is selected.

A user can click inside the list item to edit any of the editable fields. completed

There should be a checkbox for the user to click to have the task shown up
as done. Done cannot be clicked if lower numbered tasks haven’t already Completed
finished. To Be Verified(TBV)
User should be able drag a task in the task list. The task that is being
Completed
dragged should be visible.
User can click save button to save all the information that has been changed
in the tasks list. The save button will be grayed out if nothing has been Completed
saved.
All fields are editable through one click editing in the task list on the User
Completed
story page.
Windows within the application can be minimized. Completed
Windows within the application can be maximized. Completed
Windows within the application can be restored to their last position. Completed
A buttons appears on the window titlebar that when clicked changes the
dialog so that the user can no longer drag or resize the window. And when Completed
reclicked the window will be draggable and resizeable.
A button exists in the upper right corner of the windows that allows the
Moved
window to be pinned.
A button exists in the upper right corner of the windows that allows the
Moved
window to be minimized.
A button exists in the upper right corner of the windows that allows the
Moved
window to be maximized.
A button exists in the upper right corner of the windows that allows the
Moved
window to be restored.

Each window exists in its own portion of the screen with proper sizes and
Completed
positions. As well as changes size respectively when the browser is resized.

Basic functionality is created and demonstrated to the customer to prove that

Completed
implemenation into the project is possible.
Each status can be dragged to another status cell in its own row. When
dropped on the cell the task is visually moved from the original cell to the new Completed
cell.
 Sprint 2 - Ba
Task: ID #: Assigned To: Priority: Est Time:

Create initial view for the hierarchy of

L1 Chad 0 200
Product/Project/backlog/sprint

Create inital view to display user stories and associated

L5 Dustin 0 120
details

Update L1 view to meet feedback provided by project

L10 Chad 0 100
sponsor.

Update L5 view to meet feedback provided by project

L11 Dustin 0 120
sponsor.

Create Storyboard controller and view O2 Nick 0 5

Create User Story controller and view O3 Nick 0 5

Create Landing controller and view O4 Nick 0 5

Create initial interface element to contain all views within
O8 Nick 0 120
the system.
Update O8 interface to meet feedback provided by the
O9 Nick 0 360
project sponsor.
Create initial interface to display the list of User stories S4 Dustin 0 120
Initial layout provided of each task visually associated
S9 Dustin 0 90
with its User story
Update S4 view to meet feedback provided by project
S18 Dustin 0 120
sponsor.
Update S9 layout to meet feedback provided by project
S19 Dustin 0 60
sponsor.

Create initial view for the user stories that contains a list
U1 Mike 0 360
of tasks based on the story selected, the list is ordered.

Create a add buttton that will insert a new row into the
U2 Mike 0 60
task list.

Create a delete button that will remove the task from the
U3 Mike 0 60
task list.

Create an edit button that will pop up a dialog box with

U4 Mike 0 120
the editable fields of the task.
Create initial text boxes for Acceptance criteria and
U6 Mike 0 30
Description on U1 view.

Access the database to Display the following information

on the page: Story Name, Story ID, Stakeholder, Story U9 Chad 0 60
Owner, Business Value, Priority, Size and Description

Create a save button that will save story and task

U10 Nick 0 240
information to the database

Update U1 view to meet feedback provided by project

U12 Mike 0 120
sponsor.

Update U6 text boxes to meet feedback provided by

U13 Mike 0 30
project sponsor.
 Sprint 2 - Backlog (1/29/08 - 2/18/08)
Est End Date: Actual Time: Start Date: End Date:

2/12/2008 157 2/9/2008 2/11/2008

2/12/2008 130 2/3/2008 2/11/2008

2/18/2008 50 2/17/2008 2/18/2008

2/18/2008 21 2/18/2008 2/18/2008

2/4/2008 5 2/1/2008 2/3/2008

2/4/2008 5 2/1/2008 2/3/2008

2/4/2008 5 2/1/2008 2/3/2008

2/12/2008 105 2/5/2008 2/14/2008

2/18/2008 346 2/16/2008 2/18/2008

2/12/2008 165 2/7/2008 2/11/2008

2/12/2008 95 2/7/2008 2/13/2008

2/18/2008 73 2/14/2008 2/18/2008

2/18/2008 30 2/14/2008 2/18/2008

2/12/2008 240 2/3/2008 2/12/2008

2/18/2008 60 2/10/2008 N/A

2/18/2008 30 2/10/2008 N/A

2/18/2008 N/A N/A N/A

2/12/2008 30 2/3/2008 2/12/2008

2/18/2008 48 2/17/2008 2/18/2008

2/18/2008 N/A N/A N/A

2/18/2008 320 2/15/2008 2/18/2008

2/18/2008 60 2/15/2008 2/18/2008

 Acceptance Criteria: Status: Milestone ID:
Selection of a Product, project, backlog, and sprint are available through a
hierarchy view. Selection of user stories and tasks are available through an
Completed M8
associated view once a sprint is selected. Hierarchy of objects must be
maintained through the views.

User stories can be selected from the view. The view must only display user
Completed M8
stories that belong to the selected sprint in the hierarchical view (L1).

Selection of a Product, project, backlog, and sprint are available through a

hierarchy view. Selection of user stories and tasks are available through an
In Progress M12
associated view once a sprint is selected. Hierarchy of objects must be
maintained through the views.

User stories can be selected from the view. The view must only display user
Completed M12
stories that belong to the selected sprint in the hierarchical view (L1).

a web page with the title Storyboard page will be accessible from a web
Completed M9
browser.
a web page with the title User Story page will be accessible from a web
Completed M9
browser.
a web page with the title Landing Page will be accessible from a web
Completed M9
browser.

All other views exist within the bounds of the element. Completed M8
All other views exist within the bounds of the element. Views can be moved
Completed M12
and closed within the element.
All of the user stories associated with a sprint are viewable within the
Completed M8
storyboard.
Without using any keystrokes or mouse clicks the status of a particular task
Completed M8
associated with a story is obvious to anybody viewing the interface.
All of the user stories associated with a sprint are viewable within the
Completed M12
storyboard.
Without using any keystrokes or mouse clicks the status of a particular task
Completed M12
associated with a story is obvious to anybody viewing the interface.

Inside the Story View there will be a list of tasks that are order by their
Completed M8
database ordering.

By clicking a button a user is able to add a task to the list. The program will
assign it an order and TaskID, the first item in the list will be assigned order 1
Completed M11
and if there are already items in the list then it will be assigned the highest
task plus one.
Selecting a view and clicking delete will remove the list item. The list will
update without refreshing. Each task after that item will have there order
Completed M11
decremented by one or more depending on how many task have been
deleted. Only delete the task if save is selected.

A user can click inside the list item to edit any of the editable fields. completed M11
There should two edit boxes in the Story View; one to include acceptance
criteria tasks and the other one to include description of the task. When a
Completed M8
user clicks a task these should be automatically populated. User can input
text in each box.

The following information will be displayed in the story view: Story Name,
Story ID, Stakeholder, Story Owner, Business Value, Priority, Size and Completed M10
Description

User can click save button to save all the information that has been changed
in the tasks list. The save button will be grayed out if nothing has been Completed M11
saved.
Inside the Story View there will be a list of tasks that are order by their
Completed M12
database ordering.
There should two edit boxes in the Story View; one to include acceptance
criteria tasks and the other one to include description of the user story. When
Completed M12
a user clicks a task these should be automatically populated. User can input
text in each box.
 Sprint 1 - B
Task: ID #: Assigned To: Priority: Est Time:

Identifying User Stories for Landing Page E1 Chad 0 N/A

Identifying User Stories for Storyboard E2 Dustin 0 N/A

Identifying User Stories for User Story Page E3 Mike 0 N/A

Identifying User Stories for Other Programming Tasks E4 Nick 0 N/A

Create Tasks for Landing Page User Stories E5 Chad 0 N/A

Create Tasks for Storyboard User Stories E6 Dustin 0 N/A

Create Tasks for User Story Page User Stories E7 Mike 0 N/A

Create Tasks for Other Programming Tasks User Stories E8 Nick 0 N/A

Design the initial version of the software system E9 All 0 N/A

Develop initial version of class diagrama E10 Chad 0 N/A

Develop initial A3 Architecture Diagram E11 Dustin 0 N/A

Set up physical server D1 Nick 0 N/A

Develop database schema D2 Mike 0 N/A
Set up CVS/Subversion Revision System D3 Nick 0 N/A

Install Web-server on Project Environment W1 Nick 0 N/A

Implement Scripts to Update Web-site Automatically W2 Nick 0 N/A

 Sprint 1 - Backlog (1/8/08 - 1/28/08)
Est End Date: Actual Time: Start Date: End Date:

N/A 60 1/12/2008 1/14/2008

N/A 45 1/11/2008 1/13/2008

N/A 45 1/12/2008 1/13/2008

N/A 30 1/15/2008 1/17/2008

N/A 75 1/12/2008 1/27/2008

N/A 60 1/12/2008 1/27/2008

N/A 30 1/12/2008 1/27/2008

N/A 30 1/15/2008 1/25/2008

N/A 270 1/23/2008 1/28/2008

N/A 60 1/24/2008 1/29/2008

N/A 60 1/27/2008 1/27/2008

N/A 60 1/15/2008 1/21/2008

N/A 180 1/12/2008 1/25/2008
N/A 30 1/15/2008 1/21/2008

N/A 30 1/15/2008 1/21/2008

N/A 120 1/15/2008 1/23/2008

 Acceptance Criteria: Status: Milestone ID:
Basic functionality of the interface is obvious based on user story
descriptions. Uninformed user can tell what the landing page interface should Completed M4
be used for simply by reading the stories.
Basic functionality of the interface is obvious based on user story
descriptions. Uninformed user can tell what the storyboard interface should Completed M4
be used for simply by reading the stories.
Basic functionality of the interface is obvious based on user story
descriptions. Uninformed user can tell what the user story page interface Completed M4
should be used for simply by reading the stories.

Extra functionality is obvious to an uninformed user by reading the stories. Completed M4

All points on the project proposal under the Landing Page section of the
Goals for the project are completely covered by at least one Landing Page Completed M5
task.
All points on the project proposal under the Storyboard section of the Goals
for the project are completely covered by at least one Storyboard task. Visual
Completed M5
task status should be obvious to the user to allow for easy drag and drop
functionality.

All points on the project proposal under the User Story Page section of the
Completed M5
Goals for the project are completely covered by at least one Storyboard task.

All points on the project proposal not covered by the other three sections are
Completed M5
completely covered by at least one Storyboard task.
All intended functionality and non-functional characteristics have been
Completed M6
modeled within the design of the overall system.
All model, view, controller, and supporting objects will be displayed within the
diagram. All relationships between the objects will be represented on the Completed M6
diagram as well.
Entire system functionality along with flow control is summed up in a one
page document on a letter size sheet of paper. Complete coverage of the Completed M6
User Stories can be explained on a basic level by the document.
Web Application should be able to access/query the Database. Completed M1
The database schema has been created as defined by project sponsor. Completed M3
Be able to checkout, update, and commit files for the web application via
Completed M2
CVS/SVN from a remote machine.
Be able to open a web browser and input the URL and view the web
Completed M1
application.
The script should populate a website template whose visual appearance can
be changed without affecting the data displayed. The script should create
HTML links for each relevant document in the public_html directory. It should Completed M7
also change the permissions of all files linked to be readable by any group
(i.e. User, Group, Other)