Here are a few things everyone should know when you’re new to our platform:
Tara’s workflow is super simple:
- Create a requirement to capture what we want to build and include details such as product requirements, specs, and designs
- Evaluate and create the engineering tasks to complete the requirement, and estimate the effort needed to complete each task,
- Plan and sequence the work by creating upcoming sprints and assigning tasks to them
- Start the next sprint, and track daily progress until completion. Rinse and repeat until you finish your product
- Requirement: A requirement typically contains the information - spec, designs, links, etc - about a feature, an enhancement, or a product. It groups together a set of tasks required to achieve the desired outcome, analogous to an epic in other agile task management systems
- Task: A task is the fundamental unit of work - typically development work - that is worked on by a single individual. A task should be bite-sized enough to be completed within a sprint.
- Sprint: A sprint is typically a one-week or two-week period when the engineering team focuses on completing the tasks planned for this period. A big feature or a large project is typically broken down into tasks that can be completed iteratively sprint by sprint.
- Backlog: The backlog contains any tasks that have not been planned or completed yet - i.e. any incomplete tasks that have not been assigned to the current or an upcoming sprint
- Homepage: The homepage is the page where you visit every day. It shows what you need to focus on - tasks assigned to you and ones you collaborate on, as well as pull requests on which you are a reviewer - during the current active sprint, minimizing ambiguity and noise.