7 votes

Why did our process cause us to miss our release date?

Both Developers and Executives Broke the Agile Contract It was due for a release tomorrow but, as a result of a review by management, needs reworking. This will undoubtedly add a lot of time onto ...
Todd A. Jacobs's user avatar
  • 50.4k
6 votes
Accepted

Why did our process cause us to miss our release date?

I think the crux of your question may actually lie in questions you posed in a comment, rather than in the question itself: Do you find it acceptable that release dates are not met? The answer is.....
Sarov's user avatar
  • 14.8k
6 votes

"Dead horse" topics banned at sprint retrospectives, is this good practice - why or why not?

Is this a standard or good practice in facilitating a retro to 'censor' known issues like this? Yes and no. I feel it's wrong to censor anything, especially talking about impediments at a ...
nvoigt's user avatar
  • 8,505
5 votes

Our first post mortem - what's the right structure

Six to no more than maybe 9 people is your sweet spot for facilitating working groups. I would predict having a single sessions with 40 people will yield nothing valuable.
David Espina's user avatar
  • 37.1k
4 votes

How to run our first post mortem?

I used to work at a company where post-mortems were fun, and we looked forward to them. A clear list of issues is prepared. This can be collected during the project or polled for (verbally or by ...
Danny Schoemann's user avatar
3 votes

Our first post mortem - what's the right structure

If the meeting will be just about sharing the results of the questionnaire and the next steps of the product (In other words no interaction with the attendees other than the regular Q&As in any ...
Yassmeen's user avatar
  • 817
3 votes
Accepted

What is a clear, but more friendly term than "post mortem?"

A more friendly and less formal alternative term for "post-mortem" is "lessons learned" or "retrospective." This term focuses on the positive aspect of learning from ...
Marcin Sanecki's user avatar
3 votes

"Dead horse" topics banned at sprint retrospectives, is this good practice - why or why not?

The Scrum team alone cannot solve every impediment. It is a good idea to have some kind of escalation path for issues that are outside of the control of the team, but are recurring and damaging. As a ...
Barnaby Golden's user avatar
2 votes

Why did our process cause us to miss our release date?

I would encourage you to sit with your team (perhaps in the retrospective) and take a look at the values in the Agile manifesto: http://agilemanifesto.org/ Customer collaboration over contract ...
Casey Sprague's user avatar
2 votes

"Dead horse" topics banned at sprint retrospectives, is this good practice - why or why not?

A retrospective should not ban topics. And a retrospective must not waste people's time, either. With that said, what you could do is categorise the retrospective items according to different ...
Tiago Cardoso's user avatar
  • 8,643
1 vote

What is a clear, but more friendly term than "post mortem?"

In my view, I have always separated the types of rear-facing analysis due to the intent of the review. In other words, I do not think that a lessons learned or retrospectives or whatever you want to ...
David Espina's user avatar
  • 37.1k
1 vote

What is a clear, but more friendly term than "post mortem?"

Lessons learned That's the purpose of a post mortem. That's the purpose of a project/phase retrospective also. What went well, what not so well, what we learned, and what are some action items for ...
Bogdan's user avatar
  • 15.2k
1 vote

"Dead horse" topics banned at sprint retrospectives, is this good practice - why or why not?

If the same impediment is being raised Sprint after Sprint, that brings up a few questions. Is someone actively working on resolving the impediment? Maybe it can't be resolved within the Scrum Team ...
Thomas Owens's user avatar
  • 19.4k
1 vote

"Dead horse" topics banned at sprint retrospectives, is this good practice - why or why not?

Censoring an impediment from the retrospective doesn't solve it. As it looks to be a major impediment that's blocking the team, maybe it's worthwhile to arrange a separate meeting to analyze the ...
BenLinders's user avatar
1 vote

What are the most common problems that you find in your lessons learned sessions?

Wrong purpose The most common problem is planning it as a blaming session and not as a meeting to come up with a plan to never repeat a mistake. Or, in the rare case it's about a success: Plan it as ...
1 vote

Why did our process cause us to miss our release date?

Your thinking assumes several fallacies which have been evidenced time and time again. The idea that software engineering is accurately estimable (it's not, estimates merely become more accurate as ...
Venture2099's user avatar
  • 4,075
1 vote

Is it correct to refer to a 'post mortem' session even for successful projects?

I also think David got the answer right. But to add a little. Post-mortem is a common term for this activity that is now understood by many. The word's actual latin meaning is less important than the ...
Matt's user avatar
  • 11
1 vote

Do you track the cause of bugs?

The cause of bug is a very important metric. I generally name is as "Resolved As" with values: Code Fix, Environment Issue, External Entity, Bad Data, Design Gap etc. There is no blame game ...
Abs's user avatar
  • 111

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