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 ...
- 49.2k
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 ...
- 8,348
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.....
- 14.8k
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 ...
- 4,532
4
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.
- 37k
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 ...
- 19k
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 ...
- 817
2
votes
Is it correct to refer to a 'post mortem' session even for successful projects?
Try "Project Review", or, "Debriefing"
From Wikipedia, the free encyclopedia
Debriefing is a process of
receiving an explanation,
receiving information and situation-based reminders of ...
- 21
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 ...
- 167
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 ...
- 8,539
1
vote
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 ...
- 205
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 ...
- 14.5k
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 ...
- 18.7k
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 ...
- 601
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 ...
- 4,045
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 ...
- 11
1
vote
Is it correct to refer to a 'post mortem' session even for successful projects?
Yes. Post mortem applies.
The SUCCESS was an artifact of the life of PM process, but after the work's complete, that process is over ... you killed it to bring home a success ... in the same fashion ...
- 1,332
1
vote
Is it correct to refer to a 'post mortem' session even for successful projects?
would be good or not to keep such expression only for failed projects?
Like others my perspective is that the phrase you use is fairly unimportant as long as everyone understands what it means within ...
- 2,071
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 ...
- 111
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 ...
Only top scored, non community-wiki answers of a minimum length are eligible