Tag: Agile (37 posts) Page 1 of 4

Jeremy Jarrell
Productivity

Keeping Your Team on Track

blog/2017/sunset.png

One of the most striking things that nearly all highly effective teams have in common is a small—but reasonable—set of clearly defined goals for each iteration. Rather than obsessing over secondary metrics, such as the number of stories closed or the total number of points completed, successful teams measure their success by their ability to deliver on the goals they set for themselves at the beginning of the iteration. Read more...

Jeremy Jarrell
Productivity

Understanding the Need for Agile

blog/2017/sprout.png

This post is the first in a series that we’re introducing to get back to the basics of agile and help you understand where these methodologies that have been so successful actually originate from. Read more...

Jeremy Jarrell
Productivity

Embracing Evil with Evil User Stories

blog/2017/spooky_hacker.png

If you’re like most product managers, you probably have a backlog full of user stories representing just what you’d like to see your best users do with your product. But what about your not so great users? Read more...

Jeremy Jarrell
Productivity

Velocity Is Not the Goal

blog/2017/roller.png

How is my team doing? How much have they done? Inevitably, after your team starts to make progress using an agile methodology, you’ll find yourself wanting to measure that progress. And as soon as you start to look at how to measure agile teams, you’ll encounter velocity. Read more...

Jeremy Jarrell
Productivity

Choosing the Right Iteration Length

blog/2017/beaker.jpg

One of the most common questions facing teams that are new to agile is, “What’s the right iteration length for our team?” Although this question can seem daunting at first, there’s actually a simple way to find the answer. Read more...

Jeremy Jarrell
Productivity

Splitting Stories Across Teams

blog/2017/splitting-stories-1.png

If you are releasing a feature across both platforms, you may originally start with that feature described as a single user story but then split the story in two as each team tackles their respective implementations. Read more...