Hot answers tagged

16 votes

When does the team discuss requirements when using Kanban?

You're right that Kanban doesn't have the concept of Sprints or Sprint Planning like Scrum does. That's because it's a leaner methodology. More things are done just-in-time. It's up to you to decide ...
user avatar
  • 75.9k
8 votes

How should I translate a requirements document into user stories?

But my team is working using agile methods (a combination of scrum and kanban), so what we need is user stories. This is a misconception. Neither Scrum nor Kanban require that requirements be ...
user avatar
  • 75.9k
8 votes

Teams do relative estimations, business wants absolute estimations. How to make everyone satisfied?

I'm curious why you bother to do estimations at all if you don't have a way to eventually boil it down to approximate actual time. The only reason I can think of is to be able to say "that's too big" ...
user avatar
7 votes
Accepted

When agile versions span multiple sprints

At the end of an iteration, it's not required to release a software product. Scrum calls this an Increment, and other methodologies may have different names. The purpose is the same - at the end of ...
user avatar
  • 75.9k
7 votes

Definition of "Current Task Estimate"

Where did you get this definition from? I'm reading this definition from the chapter "Estimate your work", which doesn't include done work.
user avatar
  • 1,014
7 votes
Accepted

Agile Waterfall integration and delayed deployment

One solution is to adopt the "LTS" (Long Term Support) model used by Linux and browser vendors. At the end of a sprint, if you have a version fit for release, you create a release. Give it a version ...
user avatar
  • 38.2k
7 votes

Kanban board - How to handle defects found in testing phase?

The ticket should be in the column it belongs in, which sounds pretty stupid to say and is exactly why I'm mentioning it. The ticket was being developed, then handed off to QA who found some defects. ...
user avatar
  • 512
7 votes

Teams do relative estimations, business wants absolute estimations. How to make everyone satisfied?

The ultimate goal with any estimation approach is to be able to translate the estimates into 'real' terms. Otherwise, what would be the point? What use do t-shirt size estimates have if you can't ...
user avatar
  • 22.1k
6 votes
Accepted

Is it time for our development organization to let go of Scrum?

No. Scrum is designed to fight exactly the issues you are experiencing. You could switch to a reactive approach fixing bugs as they are reported as quickly as possible, but this comes at the cost of ...
user avatar
  • 64.6k
5 votes

Agile Waterfall integration and delayed deployment

Rather than feature branches, I'd recommend using feature flags. Essentially, these are just conditionals in your code that determine whether a particular portion of the code gets run or not. You ...
user avatar
  • 6,224
5 votes

When does the team discuss requirements when using Kanban?

You are slightly misrepresenting/misunderstanding what the Sprint Planning meeting does in Scrum which I think is the cause of your confusion. A Sprint Planning meeting is usually the wrong place to ...
user avatar
5 votes
Accepted

Scrum in combination with ad hoc bug fixes

"[...] reported many critical bugs that needed immediate attention" sounds nasty. If your team can solve 5 bugs per day and dozens of users reported dozens of bugs which all need immediate attention, ...
user avatar
5 votes

As a developer, how should I work differently in kanban vs scrum?

The two approaches are very compatible. In fact, it is completely possible to use both. That said, as you adopt Scrum, there will probably be two significant differences. 1) Scrum is very team ...
user avatar
  • 2,001
4 votes

If my value stream has dev followed by test, how do I model a developer who writes tests first?

Don't have a separate column. I know it's an example used everywhere but it's more geared at highlighting waste between steps, the TDD cycle is pretty tight. I'd recoummend Development column with ...
user avatar
  • 141
4 votes

Is it time for our development organization to let go of Scrum?

I am not sure you have quite precisely put your finger on exactly what the problem is, especially due to having taken on the new large customer. Are you starting to miss sprint goals/ deadlines? Are ...
user avatar
4 votes

Using Kanban or Scrum across 2 companies

Scrum and Kanban aside, the fundamental problem you are facing isn't unique to your situation. It's quite common when there's a hand-off between the development organization and another organization. ...
user avatar
  • 75.9k
3 votes
Accepted

How to organize work for a team delivering 3 connected but distinct products and stay agile

Adding additional Scrum teams is a function of the number of development team positions you have, not the products you're working on. A development team should be no more than nine people, so if you ...
user avatar
  • 6,224
3 votes

How to organize work for a team delivering 3 connected but distinct products and stay agile

Option 2 with a dedicated product owner for each of the projects. Each product owner must agree during Sprint Planning that the sprint will capture enough deliverables for their project. Leverage in ...
user avatar
3 votes

Are there any challenges with self-selecting/volunteering/signing up for agile tickets/tasks?

The retrospective system is relatively efficient at sorting any challenges out. People tend to specialize a little on topics you are better at or more interested in, and sometimes you still end up ...
user avatar
3 votes

Are there any challenges with self-selecting/volunteering/signing up for agile tickets/tasks?

Since you are asking for experiences, mine is that it has never been an issue. I've worked on half a dozen different scrum teams over the past decade and in the each case there were simply never any ...
user avatar
  • 24.9k
3 votes

When does the team discuss requirements when using Kanban?

I am editing my answer based on the feedback I received to further help understand how and when should you be work on the Requirements and Sprint Planning stage of your Sprint; as also on applying the ...
user avatar
3 votes
Accepted

How to treat partially done partially cancelled cards

I recommend scissors. If you insist on grouping multiple tasks on one card it's going to have multiple states. The rest of the world solves this problem with check boxes but if your process needs ...
user avatar
3 votes
Accepted

Agile tools, can't find any that suits my case or I'm wrong somewhere?

It sounds like you're thinking about what a project is differently to how most of this kind of software does. As a result, you're also breaking down other pieces differently. In a tool like Jira: A ...
user avatar
  • 5,956
3 votes
Accepted

How should I translate a requirements document into user stories?

There's no shortcut. What you have is great if formally verifying that system requirements is a requirement of the project. If formally verifying system requirements is not a requirement then you can ...
user avatar
  • 4,977
3 votes

How to deal with roundtrips in Kanban

Two things stand out to me. In the long-term, the Lean-Agile methods are centered around building quality into the process from the beginning (and at every stage) and Kanban is centered around ...
user avatar
  • 75.9k
3 votes

As a developer, how should I work differently in kanban vs scrum?

I pick up the highest priority piece of work for which I'm suited and I complete it to a good standard, as soon as I can without overworking myself. This sounds like a very lonesome job. Where's ...
user avatar
  • 67.8k
3 votes

How to deal with story-cards on a simple issue-board in Jira

Don't have a separate card for the story. Mark all the cards in the same story with a sticker/colour or swim-lane
user avatar
  • 64.6k
2 votes

How to include estimating and its effect on prioritization with Kanban?

One of the things Agile tries to achieve is the concept of 'doing it trumps talking about doing it', estimating is one of these things where you spend too much time worrying about how long it'd take ...
user avatar
  • 48k
2 votes
Accepted

Best practices for releasing patches that affect multiple development stories

You can release to a QA 'trunk' before going to the release trunk. This lets you get more testing in, and lets you promote good integrated builds to a release. The difficulty comes if you find a bug, ...
user avatar
  • 48k

Only top scored, non community-wiki answers of a minimum length are eligible