Hot answers tagged

80 votes

Is it sound project management practice to make software engineers fix bugs "off the clock"?

And not only are they suppose to correct them, they are suppose to correct them on their own time without impacting plans. This is your problem. Why don't your plans include the time for fixing ...
user avatar
54 votes

Is it sound project management practice to make software engineers fix bugs "off the clock"?

Just as a side note to the other good answers - developers tend to have minds that look at process and (un)consciously find ways to game it. What you are training your developers to do here is to not ...
user avatar
  • 641
47 votes

Is it sound project management practice to make software engineers fix bugs "off the clock"?

Over the last year we've become pretty hardcore in adopting the principal that an engineers must fix their own defects (those found internally and those that escape to the end users). Not only are ...
user avatar
  • 7,530
29 votes

Is it sound project management practice to make software engineers fix bugs "off the clock"?

This is a troubling post. Your company is penalizing its workers for what is a normal and expected occurrence--performance variability. The whole reason to "punish" someone is for a behavior change, ...
user avatar
  • 36.6k
18 votes

Is it sound project management practice to make software engineers fix bugs "off the clock"?

Aside from the main issue you are asking about, there's also something a little concerning about this part: "defects (those found internally and those that escape to the end users)" I don't see ...
user avatar
15 votes
Accepted

How picky should I get with a team member's quality of work?

When Engineering Problems Become Project Management Problems One of the team members turns in code that is almost always bloated and inefficient, even though it technically works (although, from ...
user avatar
  • 47.4k
15 votes

Is it sound project management practice to make software engineers fix bugs "off the clock"?

The short answer: No, it isn't! The not-as-short answer: Your company has come up with the idea that the existence of bugs is a professional failure on the part of the developer. This is not true. ...
user avatar
13 votes
Accepted

How do you convince a client that testing is a must?

If you are building a product for a client, your internal testing / QC work is not subject to negotiations. It is part of the work, part of the price, and there is no reduction in that area. If the ...
user avatar
  • 36.6k
13 votes

What could be my risk mitigation strategies if my client wants to contract UAT?

“It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts. Sherlock Holmes A logical corollary is that it is a ...
user avatar
  • 8,689
10 votes

Is it sound project management practice to make software engineers fix bugs "off the clock"?

"Hardcore" indeed. I don't have much to add to the other good answers, but I'll relate an experience of my own as a developer. I worked for a company in which the culture was similar to what you are ...
user avatar
9 votes

How do you ensure code quality when having a weaker programmer on your project?

It's great to hear that Code Reviews went smoothly and you are seeing results soon, you have seen it's effective and that means the junior programmer is keen to learn (All good stuff) Few things I ...
user avatar
  • 434
8 votes
Accepted

Influence code quality as Scrum Product Owner

The Product Owner has responsibility for the backlog and the development team has responsibility for delivery. However, in Scrum we work as a team and there is nothing to stop the Product Owner ...
user avatar
8 votes
Accepted

QA Code freeze and setting the expected delivery timeline

Having worked in two regulated environments (aerospace and pharmaceutical/healthcare), I've seen the problem of needing independent quality assurance in a deliverable. A few things to consider: ...
user avatar
  • 17.2k
8 votes

What is the good response to convince project manager about testing process?

Modern testing is all about how you assist to "Accelerate the Achievement of Shippable Quality". Do your reviews help with accelerating? What metrics do you use to create proof of that? ...
user avatar
7 votes

Is it sound project management practice to make software engineers fix bugs "off the clock"?

This practice is good way to drive out your best and brightest, leaving you with a skeleton crew of your bottom performers. I have developed software for generation 4&5 fighter jets and managed ...
user avatar
  • 201
7 votes

QA-Challenged Team - How to Improve?

We've struggled with the same issue on my team, while there's no replacement for a quality QA on the team, we've managed to get along by wearing multiple hats. This is our workflow: TDD the story ...
user avatar
  • 1,390
7 votes

How to manage long-term software quality requirements?

TL;DR While quality can be measured objectively, defining the domain-specific elements of quality for your organization isn’t something where you can rely on a standard dictionary definition. In ...
user avatar
  • 47.4k
7 votes

How to handle stakeholders' different understanding of project requirements?

This is a great question. Several years back I analysed the bugs reported in a team and found that over half of them came about as a result of misunderstanding of requirements. Some things that can ...
user avatar
7 votes

What is the good response to convince project manager about testing process?

What do you mean by "reviews" in this context? Many development teams do peer-reviews of code and analysis because they find that reviews improve productivity and quality. Many teams also ...
user avatar
  • 5,662
6 votes

Is it sound project management practice to make software engineers fix bugs "off the clock"?

In addition to others, I also find this post disturbing. I've seen Project Managers want to place all sort of metrics on developers, but never on themselves, Product Managers, QA, management, etc. It ...
user avatar
  • 61
6 votes

Moving from 2-week dev sprint / 1 week QA sprint model to a "true" 2-week sprint model - tips?

Having gone through something similar myself, here are some considerations. I'll try not to get too wordy but there are some aspects of Scrum that need to be brought up. Making this sort of change ...
user avatar
  • 405
6 votes
Accepted

How to deal with overhead of QA logging bugs that POs aren't interested in fixing?

This sounds like a good topic to bring up at the team's retrospective. There are lots of possible approaches, but the team should decide for themselves. Some things you might consider: The QA shows ...
user avatar
6 votes

What is the good response to convince project manager about testing process?

I think it is a very fair question for the PM to ask. Evaluating the proposed effort against its benefits, costs, and risks is proper leadership and management. If you have a proposal for testing, you ...
user avatar
  • 36.6k
5 votes
Accepted

Is there any place for the Prince 2 Mandate Document 'Quality Expectations' in an agile development?

Define Quality Through an Agile "Definition of Done" What level of quality are you expecting from this solution? While tempting, asking the question in this way is not useful because it doesn't ...
user avatar
  • 47.4k
5 votes
Accepted

How other than financial constraints affect quality?

If I don't have the time to produce a Swiss precision watch, ... If I don't have the tools to produce a Swiss precision watch, ... If I cannot attract the people that can produce a Swiss precision ...
user avatar
  • 7,530
5 votes
Accepted

Should a Statement of Work (SOW) include "coding style" under the Client Obligations section?

TL;DR Should I add something to "Client Obligations" about code style? You can do this, but you may be measuring the wrong thing. This smells like an X/Y problem: you have a problem to solve with ...
user avatar
  • 47.4k
5 votes

Is it sound project management practice to make software engineers fix bugs "off the clock"?

Defects are part of software development cycle. It certainly cannot be blamed on just a single person. The whole chain is responsible. Any found defect should be categorized and prioritized. Then it ...
user avatar
5 votes

Stories in test at end of sprint

Discuss in the Retrospective. There's a limit to how much advice can be obtained from strangers on the internet. Your Team is presumably aware of the problem, and Scrum prescribes a self-organizing ...
user avatar
  • 14.7k
5 votes

How to handle stakeholders' different understanding of project requirements?

If there are two stakeholders who have different understandings of the requirement, then there may be more. What about how you interpret the requirement, from the perspective of a tester? Or how about ...
user avatar
  • 17.2k
4 votes
Accepted

How do I improve the development process at our small startup?

Focus on quality and estimates You identified four problems. Of those, I would view the following two as your main issues (long hours and missed deadlines are likely resulting from these): Quality ...
user avatar

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