We're working to describe our planned work, following a general Agile methodology -specifically Scrum. In part, this description is based upon a template from AgileSoftwareDevelopment.com. The tasks in any individual sprint are drawn and inspired from something called a Product Backlog. The Product Backlog is a document containing high-level, broad stroke tasks that the team needs to accomplish.
The sprint backlog is a greatly detailed document containing information about how the team is going to implement the requirements for the upcoming sprint. Tasks are broken down into hours, with no task being more than 16 hours. If a task is greater than 16 hours, it should be broken down further. Tasks on the sprint backlog are never assigned; rather, tasks are signed up for by the team members as they like.
We're currently attempting to setup a Jira instance to help us assign, track, and maintain the status of the Sprint tasks.
Sprint 1 - Develop SOA Documentation Templates
|
Task Description |
Prio. |
Work Est. |
Risk |
Assigned To |
Status |
|---|---|---|---|---|---|---|
1.1 |
Finish basic template for new services |
H |
4 |
L |
|
|
1.1.1 |
Finish template for new Service Contract description page |
H |
12 |
L |
|
|
1.1.2 |
Get wiki->Java tool working on new Service Contract description pages |
H |
12 |
L |
|
|
1.2 |
Port existing notes to the new service description home pages |
|
36 |
|
|
|
1.2.1 |
Service Descriptions for Exhibition, Loan, Movement, Contact, Organization, Person, ID, Scheduler, Messaging, Date And Time, Notification |
H |
12 |
L |
Complete |
|
1.2.2 |
Service Descriptions for Resource, Archival and Preservation, Location, Media, Data Warehouse, Reporting, Vocabulary, Generic group |
H |
12 |
L |
Complete |
|
1.2.3 |
Service Descriptions for Collection, Annotation, Authentication, Authorization, Context, Generic eventing (utility), CollectionObject, Workflow, Query, Generic relationship |
H |
12 |
L |
Complete |
Sprint 2 - Fill out broad, shallow SOA analysis
|
Task Description |
Prio. |
Work Est. |
Risk |
Assigned To |
Status |
|---|---|---|---|---|---|---|
2.1 |
Link existing workshop docs, Spectrum note, etc. |
|
15 |
|
|
|
2.1.1 |
Service Descriptions for Exhibition, Loan, Movement, Contact, Organization, Person, ID, Scheduler, Messaging, Calendar, Notification |
H |
6 |
L |
|
|
2.1.2 |
Service Descriptions for Resource, Archival and Preservation, Location, Media, Data Warehouse, Reporting, Vocabulary, Generic group |
H |
4 |
L |
|
|
2.1.3 |
Service Descriptions for Collection, Annotation, Authentication, Authorization, Context, Generic eventing (utility), CollectionObject, Workflow, Query, Generic relationship |
H |
5 |
L |
|
|
2.2 |
Identify dependent, related services, and needed utilities. Assess risk and other issues, and document. |
H |
30 |
M |
|
|
2.2.1 |
Service Descriptions for Exhibition, Loan, Movement, Contact, Organization, Person, ID, Scheduler, Messaging, Calendar, Notification |
H |
12 |
L |
|
|
2.2.2 |
Service Descriptions for Resource, Archival and Preservation, Location, Media, Data Warehouse, Reporting, Vocabulary, Generic group |
H |
8 |
L |
|
|
2.2.3 |
Service Descriptions for Collection, Annotation, Authentication, Authorization, Context, Generic eventing (utility), CollectionObject, Workflow, Query, Generic relationship |
H |
10 |
L |
|
Sprint 3 - Fill out narrow, deep SOA analysis for Object Entry
This is currently pretty rough, but should provide some sense of the work.
|
Task Description |
Prio. |
Work Est. (Hrs) |
Risk |
Assigned To |
Status |
|---|---|---|---|---|---|---|
3.1 |
Identify services needed to support Object Entry |
H |
|
L |
|
|
3.1.1 |
Analyze needed services, review with team |
H |
6 |
M |
|
|
3.1.2 |
Document needed services, divide tasks |
H |
2 |
L |
|
|
3.2 |
Identify key questions and issues, pose for review |
M |
2/service |
M |
Team, by service |
|
3.2.1 |
Conduct review, incorporate feedback |
H |
2/service |
H |
Team, by service |
|
3.3 |
Prepare Entity diagrams |
M |
4/service |
M |
Team, by service |
|
3.4 |
Define basic CRUD operations (w/o schema details) |
H |
4/service |
L |
Team, by service |
|
3.5 |
Develop core schema for CRUD operations |
H |
16/service |
M |
Team, by service |
|
3.6 |
Define Read/Validate operations |
M |
8/service |
M |
Team, by service |
|
3.7 |
Define key setup capabilities |
M |
12/service |
M |
Team, by service |
|
3.8 |
Define Search operations |
M |
8/service |
M |
Team, by service |
|
Sprint 4 - Build simple utility services for Object Entry?
Some of this may be stubbed to get us to a prototype ASAP
Sprint 5 - Build entity services for Object Entry?
This will be the main deliverable we're working towards in the first phase. This will include integration with our tools, with the configuration layers.