Targets. Overview
- Tatiana Petrovskaia
- Ekaterina Chueva
This section describes target types and types of relations between targets in the Planner application.
1. Types of Targets
There are several types of targets in the Planner application, which allow you to plan and manage projects with greater flexibility and detail.
Type of target | Description | Example |
|---|---|---|
Objective | Ambitious, qualitative descriptions of what you want to achieve. Answers the question: Where do we need to go to achieve the desired goal? Should be:
| Increase the company revenue by 10% in the next two quarters |
Key Result | Set of metrics that measure your progress towards the objective. Answers the question: How do I know that I am getting to Objective? The key result can be measured by the per cent or quantity of something. Progress of a Key Result directly affects progress |
.
|
Initiative | Small goal or a specific action you need to do to achieve a small goal (other Initiative), Key Result or bigger goal (Objective). Please, pay attention, that at the moment | Perform regression testing to identify critical errors. |
Milestone | Scheduled end date, when the planned goals and results are to be achieved. Please, pay attention, that at the moment | Release on Prod |
Capability | Activity or ability that enables an organization to achieve specific goals or objectives | Financial Management |
Epic | Large amount of work that encompasses multiple smaller work items, known as Features, Stories, or Tasks, which collectively contribute to a significant aspect of a project. Epics often represent high-level objectives or significant deliverables and are broken down into manageable parts that can be completed over several iterations or sprints | User Account Management |
Feature | High-level functionality or service that delivers significant value to the end user. It represents a set of capabilities that fulfill specific user needs and is often a part of a larger product or system | User Authentication |
Story | Simple and concise description of a functionality from the perspective of the end user. It captures who the user is, what they want to achieve, and why it is important. The structure of User Story is: As a <User> I want to <description of an action or a possibility> so that <purpose/desired outcome> | As a user, I want to reset my password so that I can regain access to my account if I forget my password. |
Task | Specific piece of work that needs to be completed to accomplish a Story, Feature, or Bug. Tasks are usually assigned to team members and have more detailed steps or instructions | Design password reset UI: Create wireframes and design the user interface for the password reset functionality, ensuring it is user-friendly and accessible |
Bug | Error, flaw, or unintended behavior in the software that needs to be fixed. Bugs can affect usability, performance, security, or other aspects of the application | Password reset link not working: When users click the password reset link in the email, they are redirected to a 404 error page instead of the password reset form |
Here’s how you can use them:
Strategy: Continue to set and track your objectives, key results, and initiatives.
Roadmap: Plan long-term capabilities and break them down into epics, features, and milestones to get a clear overview of your project’s progress and dependencies.
Delivery: Manage day-to-day tasks, user stories, and bug fixes to ensure smooth project execution.
2. Types of Relationships
In the Planner application, there are types of relationships:
Type of Link | Description | How to Use |
|---|---|---|
Parent-Child |
|
|
Dependencies (Start/Finish) |
|
|
2.1 Parent-Child
Constraints of the parent-child relationship:
An Objective target cannot have a parent target. Only Key Results can be children to an Objective.
A Key Result target cannot have child targets.
Initiatives can have as many nested levels of targets as you need. Each parent target inherits the progress of child targets.
2.1.1 Dependencies (Start/Finish)
There are four-time dependencies:
Dependency | Description |
|---|---|
Finish to start | The linked target must be started on the same day when the main target is finished |
Start to finish | The linked target must be finished on the same day when the main target is started |
Finish to finish | Both linked targets must be finished on the same day |
Start to start | Both linked targets must be started on the same day |