Throughout your PM career at Clarity you will make hundreds upon hundreds of tasks. The Azure task is the direct reflection of the work that will be in a Developer's sprint.
An Azure task in this case will be a blanket term for any 'yellow' level item: Task, QA Failure, etc.
Azure tasks will be updated daily by the developers, adjusted by the project managers, and organized by the scrum master. They are the micro-cogs that make our organization work.
A bulleted section of
- Technology: Azure
- Sphere: Development
- SDLC: Development
- Cadence: Daily
¶ Creating a Task
In the Sprint:
- Next to any Blue level work item in the sprint, you will see the green "+" icon.
- You will be given three options for what to create:
- Task: A standard task, generally assigned to a User Story
- QA Failure: A task related to either a blue level that failed QA
- Impediment: A placeholder to let explain a block
¶ From the Blue Level:
- On the right-hand side of the blue level, under 'Related Work', you will see an option to "Add link-"
- Select "New Item"
- Ensure that the Link Type is "Child"
- The work item type is either Task, QA Failure, or Impediment based on what is necessary.
¶ Information that should be on the Task:
- The task title will have the project acronym within square brackets at the start of the task
- The title of the task will be a brief summary of what the task is
- You will assign the task to the person intended to do the work.
- You will add a Tag to the Task with the project acronym
- You may also add additional tags to this task based on need:
- Examples could include: Out of Scope, Meeting, or any other qualifier you would need
- You may also add additional tags to this task based on need:
- State: A new task will have the State set to "New"
- Reason: will be set automatically
- Area: must be set to the project's relative Area Path
- Iteration: Dependent on what sprint it will be in. Standard will set it for the backlog.
- Description: A short description of what the task will
- Discussion: Is for ongoing conversation on the task itself. If the discussion is more specific to the Blue Level itself, take the discussion there.
- Project Manager: The Project Manager on the project
- Full Priority: As a standard, set it to 4-Normal
- Blocked: Either "Yes" if the task is blocked, or Blank. Do not set it to "No"
- CEF Version: Not necessary
- Confidence Level: Will be set by the developer doing the task itself
- Original Estimate: The original estimate for the whole of the work on the task
- Remaining: At the onset of the task, this should match the Original Estimate.