Tag: Agile (40 posts) Page 2 of 4

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...

Jeremy Jarrell
Productivity

Finding the Right Amount of Backlog Refinement

blog/2017/pos-neg1.jpg

Many product managers struggle with getting the right level of detail in their backlog. If the backlog is too vaguely defined, then your team picks up stories that aren’t immediately actionable, which can slow them down. On the other hand, if the backlog is too well defined, then it becomes rigid and fails to evolve as your product takes shape. Read more...

Jeremy Jarrell
Productivity

Choosing the Best Slice of Your Story

blog/2017/vertical-slicing.jpg

Learning to split large user stories into smaller user stories is one of the best things a team can do to improve their workflow. Not only are smaller stories easier to understand—and therefore easier to estimate—but their smaller size makes them inherently less risky for a team to take on. Read more...

Jeremy Jarrell
Productivity

Three Ways Product Managers Can Help with a Great Iteration Planning Meeting

blog/2017/IPM.jpg

A great iteration planning meeting (IPM) sets the tone for the entire iteration. Your team leaves the session energized, excited, and with a clear picture of how to hit the ground running in the new iteration. But, what if things don’t go as well as you’d hoped? Then your team will leave the session tired and frustrated. They will leave without a clear idea of how to get started on their new set of work. They may even leave without any idea of what their goal for the next iteration even is. Read more...

Steve Lichtenstein
Productivity

Guidelines for Agile Development Using Tracker

blog/2015/08/rps1.jpg

When you’re bogged down working on your day-to-day chores and features, it can be tough to stay focused on the broader goal of smooth agile development. And while we don’t pretend that we have all the solutions, Tracker is, after all, designed to facilitate precisely that goal. Luckily, the time we’ve spent getting deep down and dirty with Tracker has allowed us to suss out the better agile practices from the. . .less better ones. Read more...

Emanuel Petre
Productivity

A Commitment is Not a Guarantee

blog/2015/07/blame_game_small.jpg

If your team uses Scrum as a development process, the team decides which of the next most important items it can complete by the end of the iteration. However, this “commitment” is often used to hold the team accountable for the amount of work that will be shipped by the end of the sprint. Holding your team accountable for failing to deliver on their engagements is counterproductive and will act as a regime of terror. This is no small issue, and Scrum now suggests using the word forecast instead of commitment. Read more...

Ronan Dunlop
Productivity

Crunch Time—A Pivotal POV

blog/2014/04/Screen-Shot-2014-04-22-at-1.40.32-PM-300x274.png

To truly understand Tracker you need to appreciate how Labs does what is does. Onsi Fakhouri does a great job explaining just that. Here’s an excerpt from his blog post. Read more...