14
votes
Sprint is 2 week and 40-stories
If you are following Scrum as defined in the Scrum Guide, the Product Owner cannot simply add stories to the Sprint Backlog. The Sprint Backlog, which is created as Sprint Planning as a negotiation ...
9
votes
Accepted
Delegating Work and Dealing with Poor Results?
A few suggestions:
Don't delegate & disappear until the deadline. Check in with them once or twice, just informally to ask how it's going, do they need any clarification from you, are they having ...
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? ...
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 ...
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 ...
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 ...
6
votes
How can I improve the efficiency of QA?
Let's divide QA(Quality Assurance) from QC(Quality control), check the difference.
Short term solution for manual QC would be to create test plans, acceptance criteria's, force your QC to add test ...
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 ...
6
votes
What is a healthy [bug cards]/[total cards] ratio for game development?
That seems a very formal and ultimately futile way of viewing things.
Right now, your rate is X. Whatever ratio others tell you is good, that will not change your current reality.
And if you say Y is ...
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 ...
5
votes
QAs get all the Work at the End of Sprint
You should not consider development and testing as sequential activities within the sprint, or the thing you describe happens. Development and testing should happen together as a collaboration between ...
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 ...
4
votes
How to set properly aligned KPIs for engineers and QA staff
So right now, as an Engineer, I take a single task, mull over it for 4 weeks, make sure it contains no bugs at all and I am the best worker you ever had. Despite the fact that it took me 4 weeks to ...
4
votes
What UAT checklists should I give the testing team?
I agree with @CodeGnome but not just with Agile. No matter the method, the product, or even the domain, UAT needs to belong to the users, in scope, conduct, and outcome. The client side needs to ...
4
votes
How should a Software Tester deal with missed Defects/bugs in Production?
You're describing an immature organization, seemingly political, low performing team, hostile work culture.
There is no such thing as a 100% defect free product or service of any type. And a mature ...
4
votes
QAs get all the Work at the End of Sprint
Yes. A common rule of thumb for a two-week sprint is that most backlog items should take 2 - 3 days to complete including QA, deployment, etc. This is just wisdom for experienced teams though, not a ...
4
votes
Best way to keep development and testing in synch
One approach you could try is to have the QA working ahead of the developers.
It would work something like this:
Back end devs write stubbed API calls that mimic the behaviour of the finished ...
3
votes
How to manage long-term software quality requirements?
I could say something about each of your points, but will address one. If you address this one, then you will figure it all out (eventually).
“Software developers started leaving project”
Ask why? Ask ...
3
votes
Reward for recognizing mistakes but disincentivize low standards
Don't use money to reward quality.
Studies show that money is an excellent motivator for routine tasks that involve no thinking, and a terrible motivator for tasks that require creativity.
Experts ...
3
votes
What UAT checklists should I give the testing team?
UAT Checklists Should Come From Users or Their Proxies
What checklists should I give the team?
From an agile perspective, you should not be giving the team a user acceptance testing (UAT) ...
3
votes
Do QA testers have to follow their sprints strictly?
This is largely going to depend on your work environment.
In my experience, QA can support a team of 3-5 developers, so your QA is definitely under-utilized. This can be addressed by adding more ...
3
votes
As a Scrum Master should I decide or the team decide whether they need a tester?
A lot of comments are made about the size of the team and the roles within it, so I'll skip that.
My advice (with most questions, issues or whatever): Take it to the team
The team is doing the ...
3
votes
How can a small team of devs maintain many products at the same time?
If you have teams that work on one project only, then you could keep them on Scrum iterations. If they can plan things out and do the work without depending too much on external resources (I'm ...
3
votes
QAs get all the Work at the End of Sprint
There are a few different ways to approach this problem.
From a Scrum perspective, your Development Team does not have sub-teams. You may have specialists, such as people who specialize in testing, ...
3
votes
Best way to keep development and testing in synch
TLDR: Optimize for throughput and your people will become T-shaped.
First of all, I should address
Is this the right approach?
To which my answer is "Don't ask strangers on the internet. Try ...
3
votes
What is the good response to convince project manager about testing process?
I'm not sure that there is a good answer to the manager's question. In some contexts, having formal gate reviews may be beneficial. However, reviews tend to be after-the-fact inspections, which aren't ...
3
votes
How to deal with other's tester mistakes after pass ownership of testing?
For me, it wouldn't make any difference if you did all the testing, B did all the testing or if you shared the effort. Nor does it make a (big) difference if what you notice in production is a new ...
3
votes
Accepted
What is a healthy [bug cards]/[total cards] ratio for game development?
TL;DR
You have one or more process problems that have been abstracted away into a proxy metric that is being used to "hold people accountable." This is almost always counterproductive, but ...
2
votes
What should be in ISO 9001 quality manual?
Every Quality Manual will be specific to the company that has implemented the ISO 9001 standard, and no two will be completely identical even when looking at companies in the same industry. If you are ...
2
votes
Do QA testers have to follow their sprints strictly?
In Scrum there is no such a role as tester. In Scrum Guide it is written:
Scrum recognizes no titles for Development Team members other than
Developer, regardless of the work being performed by ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
quality-management × 55quality × 19
software-development × 10
testing × 10
scrum × 9
agile × 8
team-management × 7
planning × 4
project-team × 4
time-management × 4
bugs × 3
process-improvement × 3
kpi × 3
kanban × 2
scrum-master × 2
communication × 2
methodology × 2
human-resources × 2
prioritization × 2
agile-coach × 2
reviews × 2
estimation × 1
project-management-style × 1
sprint × 1
requirements × 1