Information for Developers
No development work is done without a work item.
Sprints are Q1, Q2, and Q4. Releases are deployed to production within those windows, as needed.
Types of Work Items
A Product Backlog Item (or PBI) is used for all development work that we might do.
Title should be as follows: "<Subject>: <Change>" (i.e. "Booking Report: Add Shipment Number")
Description needs to include enough specific information to complete the work without a lot of back & forth interaction
A Bug is used for any defect that is unexpected behavior. A bug must have detailed data and steps to reproduce the issue
Work Item States
New: Needs to be reviewed and assigned for analysis or development
Approved: Ready to be assigned to a release/iteration
Committed: Part of a release/iteration
Done: Completely tested and ready to deploy.
New Work Item
Do not assign to an individual
Set Area to appropriate area
Leave Iteration as "Hurkin" (default)
Use the Product Backlog to drag and drop items
Review the Product Backlog
Assign work items to an Iteration until the iteration is full
For each work item, developers may add Tasks as appropriate to define the work
Completing Work Items
Check in code and associate it with the work item
Assign the PBI or Bug to an individual for testing
Verifying Work Items
Set the Status to Done.
If there is a problem, leave the item in current state and re-assign.
Re-Opening Work Items
Only do this if the item is part of the current iteration being developed
Set the status back to "New" (or "Active" if New is not available)
Assign it back to the user who completed the work
Recording Work / Time sheets: Admin and Support
All work is recorded using work orders in the HURKIN database. Created as follows:
Work Item Type = ADMIN or SUPPORT
Your name for Worker
Quantity = Hours
Reference 1 (for SUPPORT only) = Database Code for the customer to be billed for the activity.
Memo = Notes about what you did
A report is run automatically every week, and sent to email@example.com so that these can be paid.