bug trackingworkflow

Download Bug trackingworkflow

Post on 05-Dec-2014




0 download

Embed Size (px)




  • 1. TFS Work Items Workflow Petro Porchuk 03/29/2011
  • 2. ?
  • 3. The Goal is to clarify
  • 4. Agenda Roles Email Notifications Work Item Types User Story Workflow Prioritizing Bugs Bug Workflow Task Workflow Q&A
  • 5. Roles Manager/Admin unlimited permissions DEV Developer Create Tasks (Create Bugs, Create User Stories) Resolve Bugs, User Stories Close Tasks QC Quality Control Engineer Create Bugs, Tasks (Create User Stories) Close Bugs, User Stories, Tasks Reopen Bugs, User Stories Tasks USER End User Representative Create Problem Reports Close Problem Reports Reopen Problem Reports
  • 6. Email NotificationsWe need email notifications each time a work item is being moved through the workflow to quickly know what to do and dont bother one another with stupid questions like: Are you done with the story, so I can test?, Have you done with testing, how it went?.We need to use the tool we have for that TFS. DEV QC Active US/Bug has been assigned Active US/Bug has been moved to to. (New, Reopened, Edited). Resolved and Assigned to. Worked on US/Bug has been Worked on US/Bug has been closed. closed.
  • 7. Work Item Types User Story - one or more sentences in the everyday or business language of the end user that captures what the user wants to achieve. Before a user story is to be implemented, an appropriate acceptance procedure must be written by the customer to ensure by testing or otherwise determine whether the goals of the user story have been fulfilled. Bug - a program defect, which is usually found and described as a failure (deviation between actual and expected behavior). Usually filed by QA. Task - an activity that needs to be accomplished within a defined period of time. Is usually a sub-item of a Bug, User Story Problem Report an unverified report, usually filed by PM or user. After positive verification a bug report is created. Bug report changes are automatically reflected in the problem report
  • 8. User Story Workflow Active (New) Assign Unassign Email to (Admin) (Admin) DEV Rejected/Out of Scope/ Abandoned Active (assigned) (QC, Admin, DEV) Code complete and unit tests pass Build is available for QC (DEV) Acceptance tests fail* (QC) Resolved Assign Unassign Email to QC (DEV) (DEV) Resolved (assigned) Acceptance Closed in tests pass Error Reintroduced in (QC) (QC) Scope/Closed in Error (QC) Closed Email to DEV & QC involved
  • 9. Acceptance tests fail At least: 1 * Critical Issue OR 1 * High Issue OR N * Medium Issues, where N is too many
  • 10. Prioritizing Bugs Priority (When it should be fixed?) Severity (What it affects?) The level of (business) importance assigned The degree of impact that a defect has on to an item, e.g. defect. the development or operation of a component or system.Priority Description Defined By Severity Description Example Defined By 1 The bug is Critical Bug Reporter 1 (Critical) An Absolute Blocker. Unable to Start or Bug for business Use Application. Reporter needs. Must be Crash. fixed ASAP 2 (High) Serious Failure. Direct Unable to Create Bug 2 Very important Bug Reporter argument against the new row. Unable to Reporter issue to be fixed Acceptance Criteria edit existing rows. Data loss. 3 Highly appreciated Bug Reporter 3 (Medium) Regular bug. Affects very few Keyboard shortcuts Bug to have of potential users. Not do not work. Reporter blocking anything Validation missing 4 Nice to have Bug Reporter 4 (Low) Minor issue, not affecting Cosmetic UI issues, Bug anyone at all, just annoying grammar errors Reporter
  • 11. Prioritizing Items Stack Rank (What you shall work on first) -is the traditional method Product Owners use to rank/prioritize their product backlog items. The lower the stack rank the higher the priority the work item is
  • 12. Bug Workflow Active (New) Assign Unassign Email to (QC) (QC) DEV As Designed/Cannot Reproduce/ Active (assigned) Deferred/Duplicate/Obsolete (DEV) Fixed (DEV) Not fixed/Test Failed (QC) Resolved Assign Unassign Email to QC (DEV) (DEV) Resolved (assigned) Email to Verified DEV & QC (QC) involved Regression/Reactivated (QC) Closed
  • 13. Task Workflow Active (New) Assign Unassign (QC, Admin, DEV) (QC, Admin, DEV) Active (assigned) Deferred, Cut, Obs olete (QC, DEV, Admin) Completed (QC, DEV, Admin)