Stepsize Documentation
Home
  • 🏠 Welcome to the Stepsize Docs
  • 🧠Getting Started
    • Getting started with Stepsize
    • Creating your first issue
  • 🏷️Issues
    • How to create an issue
    • Adding more code and context to your issues
    • How to view inline annotations
    • Converting TODOs into issues
    • How to resolve issues
  • 👥Team & Collaborators
    • How to invite collaborators
    • Setting up Stepsize for your team
    • Using Stepsize as a Team
    • Talking to your Team Lead about Stepsize
    • Talking to your Head of Engineering about Stepsize
    • Talking to your Product Manager about Stepsize
  • 🏁Workflows
    • Using Stepsize in your planning process
    • Using Stepsize in your code review process
  • 😎Talk to us
    • Contact Us
Powered by GitBook
On this page
  • Allocating resource to fixing issues
  • Planning to fix tech debt
  • Identifying issues to fix using the visualisation tool
  • What next?
  1. Workflows

Using Stepsize in your planning process

PreviousTalking to your Product Manager about StepsizeNextUsing Stepsize in your code review process

Last updated 2 years ago

Stepsize brings a new level of visibility to tech debt.

The best way to ensure reported issues get fixed is to make good practices a habit during your sprint cycles. Stepsize is the ideal tool for this.

Haven't invited your team to Stepsize yet? Open the and head to Settings > Members. Head over to our guide on inviting collaborators for more information.

Allocating resource to fixing issues

Teams that have a strategy for managing tech debt . When teams use Stepsize to do this, they ship .

To manage tech debt effectively, pay it back quickly and regularly.

Here are two methods your team could use:

  1. Allocate 15-20% of resources to refactoring code and fixing bugs in every sprint cycle

  2. Allocate entire sprints to deal with tech debt on a regular basis, such as every quarter

Planning to fix tech debt

Use a portion of your team's sprint planning to agree which issues to prioritise.

For example, you could

  • Prioritise issues which impact the current work

  • Prioritise issues which are lowering morale

Identifying issues to fix using the visualisation tool

At the top of the Stepsize sidebar, navigate to Visualisation.

The visualisation shows you a visual representation of your codebase, which acts as a heamap for issues in your codebase.

You can filter your visualisation based on tags your team uses.

What next?

Stepsize has a range of powerful tools which help you surface tech debt during your code review process. Learn more about this in the next guide.

Using the Visualisation tool in Stepsize
🏁
Stepsize web app
ship 50% faster
3 times faster