The toughest part in building features is staying through its course.

Plenty of things change, pesky little bugs creep in, and you’ll have to entertain the possibility that things won’t go as per plan.

This unpredictability makes building the right features and shipping them on time hard.

That’s why when we opened up Zepel last year, we had Sprints baked into the product so you can launch your feature in phases and ensure you never drop the ball. We focussed on ensuring every feature you worked on, got the attention it deserved by building a free-form interface that doesn’t get in your way.

All you had to do was type, right-click and add it to a Sprint. No messy forms or clutter.

And today, we’re excited to launch Sprints across features, so you can add your user stories from different features into a Sprint.

Run Sprints across Features and launch in phases

As your team grows and starts building multiple features, you’d want to build your features in phases or run a Sprint just for a series of enhancements.

Starting today, you can add work items from different features into your Sprint.

Plan a Sprint and add work items from multiple Features

Once you’ve planned your Feature with work items, all you have to do is select them, right-click, and choose the Sprint you want to add them to.

Right-click on items to add them to a Sprint

Feature building is multidisciplinary

Of course, you need members from development, design, QA, and many others to build a quality feature. That’s why we launched Boards earlier this year, so you can accommodate each of their workflows while you build your feature.

And when we started revamping Sprints, we knew you wouldn’t want just the big picture overview. But would also want to see where each work item stands across disciplines.

Which is why, when you run a Sprint in Zepel today, you can see exactly where all your work items stand in different Boards, so you can drill into the finer details and get the full context of your Sprint’s progress.

Click on a Board to see where each user story stands across disciplines

And when you want a take a step back and get a bird’s eye view of your entire Sprint, the burn-up and burn down reports has your back. You can quickly see how your entire Sprint is progressing either by the number of items or by estimation points.

There’s a List for everything else

Not everything you are working on needs to be a feature. Product-wide tech debts, bugs, and miscellaneous tasks come up.

Which is why every project you create, comes with a List of its own, so you can capture even the smallest unit of work item and ensure you never drop the ball.

A List for every project to capture all miscellaneous items
Because the difference between products that are good and products that make your customers want to come back every single day is the attention to details.

And when you’re ready to work on them, simply add them to a Sprint or assign it to a teammate and push it to one of your Boards.

With Sprints across Features and List introduced today, planning your feature, watching it come to life, and hit production should be a breeze. Check it out on Zepel and let us know what you think.

sprints-relaunch