Skip to main content

Task sizing

Lesson 3 of 10 · 4 min 24 s. Three sizes of work side by side in one project. A sketch that hands back a clickable mockup with nothing changed in the code, the same task built once you like it, and an epic that is analysed, designed and planned before it is split into tasks and checked against what was asked.

Before you start​

  • You have done Writing a request that comes back right and are signed in to the console.
  • You have a project you can start tasks in. The lesson uses TimeSaver, a time-tracking app for small teams.

Steps​

  1. Open the new-task form in your project and start with an idea you'd like to see before anyone builds it. The lesson's description is: A Today page that shows the day's entries on a timeline, hour by hour.
  2. Under the description, choose the first size, Sketch. How big the piece of work is decides what comes back: a sketch is a quick mockup to look at, and nothing in the code changes. Choose Unattended as well, and press Go. The sketch appears on Tasks, and an agent takes it on as soon as the machine is free.
  3. When the sketch is finished, open its page, then Artifacts. The mockup is drawn in the app's own style and it's a working page, so click around it the way a user would and decide whether it's what you had in mind. Nothing in the project's code has changed.
  4. When you like it, build it from the same task. Open the Task tab, where your request is still there, change its size from Sketch to Task, and press Go. The same description now goes to an agent that changes the code, and the sketch stays on Artifacts so you can hold the result against it.
  5. Now something too big for one task. Click New task again. The lesson's description is: Let people set a budget in hours for each project, see how much is left on the timesheet, get a warning when a project is close to its budget, and compare budget with actual hours on the Reports page. That's four things, each in a different part of the app.
  6. Choose the third size, Epic. An epic is worked out first and only then split into tasks, each small enough to build and check on its own. Choose Unattended again, and press Go.
  7. On Tasks, both are now listed. The build of the sketch is under way, and the epic has an arrow beside its title; click it to open the stages that work it out before anything is built: an analysis of what's asked, then a design, then a plan.
  8. While the epic is being worked out, the regular task finishes. In the lesson, TimeSaver's site has a new Today page, with the hour-by-hour timeline from the sketch and the day's entries on it, checked with the team's tests like any other change.
  9. Open the analysis stage's page on its Artifacts tab. Each stage of the epic hands back a document, and the analysis comes first: it turns the request into requirements, with the decisions it took, what must be true for each part to count as done, and how each will be checked. The design and the plan start from it, so a wrong turn shows up here, not after the build.
  10. Once the plan is finished, open the epic's Subtasks. Below the stages that worked it out are the tasks the plan split it into, each a change of its own, built and checked like the one you made before. They run one after another on the project's machine, and the list shows where each has got to.
  11. When the last task is done, the epic finishes with one more stage. Open Details: that last stage checks everything delivered against the original request, and its notes say what it found. Then open Metrics for what the whole feature took, in time and in cost, all its tasks added up.
  12. Try the feature in the app. In the lesson, two TimeSaver projects have budgets; each shows how much is left, and the one that's nearly used up carries a warning.

What you learned​

  • There are three sizes: a Sketch to look at, a Task to build, and an Epic for the big ones.
  • A sketch hands back a clickable mockup on Artifacts and changes nothing in the code. Build it from the same task by switching its size to Task.
  • An epic is analysed, designed and planned first, and each stage leaves a document on its Artifacts.
  • The plan's tasks are listed under the epic's Subtasks, and a last stage checks everything against the original request; Metrics shows what the whole feature took.

Next​

Next lesson: Staying in the loop. Previous: Writing a request that comes back right.

Related: