Skip to main content
New
Stack Overflow Jobs powered by Indeed: A job site that puts thousands of tech jobs at your fingertips (U.S. only). Search jobs
19 votes
Accepted

How to document non-functional requirements in User Stories?

Non-functional requirements come in many forms, but they have one thing in common: The don't describe functional behavior of the system but rather put constraints on the design choices that you can ...
Bart van Ingen Schenau's user avatar
11 votes

Cloning Jira tickets at the end of a sprint - carrying over effort and points

If at the end of your sprints often you have many big tickets that are 90% - 95% done then there is something wrong: Red flag #1: Lots of things get packed into a sprint but are not finished Red flag ...
CharonX's user avatar
  • 1,643
8 votes
Accepted

Is it generally helpful to include JIRA issues in code comments?

I would try to avoid such comments. Although I think there is a place for them where you have a particularly annoying requirement. Which without, anyone might want to refactor the code. eg. //must ...
Ewan's user avatar
  • 76.3k
8 votes
Accepted

The meaning of "Fix Version" field in Jira, while working in agile, microservices and CI/CD processes

Are the above assumptions correct? It sounds like you have a hidden assumption that is wrong: namely that the field has a fixed meaning and usage. The thing is: the basic concept of what a "...
Michael Borgwardt's user avatar
7 votes

How to document non-functional requirements in User Stories?

"Non-functional requirements" is a bit vague and open to interpretation. Going on your specific example, I would say that those requirements should be used as acceptance criteria for other stories. ...
Bryan Oakley's user avatar
  • 25.3k
7 votes
Accepted

How to resolve tasks completed from the backlog with no work done?

You say "I didn't do any work for those features to work properly" but that's not strictly true. While you didn't write any code, you did spend some time testing, and testing is valid work just as ...
Pete's user avatar
  • 3,221
7 votes

How do I track tiny/small UI change requests in Agile?

Problems like these are what your retrospectives are for, because there is no "one true agile way" that will work best for everyone in the world, or even every team in a company. Brainstorm some ...
Karl Bielefeldt's user avatar
6 votes

Advice regarding tools and insights from sprints on developer performance

Do not use Jira to pick winners and losers. Coders created Jira and coders can make Jira say whatever they want. Use Jira to help the team improve its estimating and planning skills. Not for ...
candied_orange's user avatar
5 votes

When should I update 'due date' in JIRA?

Updating the due date to reflect a time estimate frankly makes no sense. The issue is already due before work started on it, whether that's tomorrow or in six months. Due dates are parameters to the ...
Dan1701's user avatar
  • 3,108
5 votes

How do you include "global requirements"?

In my opition global requirements belong to the definition-of-done because you do not want to update every matching userstory when a global requirement changes
k3b's user avatar
  • 7,526
5 votes

Is it generally helpful to include JIRA issues in code comments?

For Code Comments, there is very little usefulness. For version control comments, they are very useful for reasons outlined below. Code comments really should be used to help understand the intent ...
Berin Loritsch's user avatar
5 votes

The meaning of "Fix Version" field in Jira, while working in agile, microservices and CI/CD processes

The Fix Version field in Jira and related fields in similar tools are not only applicable to monolithic applications in a sequential or waterfall process. Having CI/CD does not make this field useless....
Thomas Owens's user avatar
  • 82.8k
4 votes

How to document non-functional requirements in User Stories?

You can incorporate them into your DOD "Definition Of Done". Non-functionals are problematic in agile though, if they change you have no way of tracking which stories have been done against what ...
Ewan's user avatar
  • 76.3k
4 votes

How to resolve tasks completed from the backlog with no work done?

Now, since I didn't do any work for those features to work properly, in order to reflect correctly what was done for those tasks should I close them unassigned in the backlog directly or put them in ...
Emerson Cardoso's user avatar
4 votes

How do I track tiny/small UI change requests in Agile?

Its probably a change to an existing user story. ie. as a user given I have some memberships when click on the resign button the status should read 'cancelled' and an email should be sent blah.. ...
Ewan's user avatar
  • 76.3k
4 votes

Cloning Jira tickets at the end of a sprint - carrying over effort and points

The idea behind putting a story that has not been completed in its entirety on the next iteration (or the backlog) is that the team should not get credit for unfinished work. This should give the team ...
Bart van Ingen Schenau's user avatar
4 votes

Cloning Jira tickets at the end of a sprint - carrying over effort and points

Say you have ticket that is pointed at 8 points, and it is all but done barring some minor changes. We could say that the ticket is 90- 95% done. Then why not clone the ticket, and carry it over as a ...
Flater's user avatar
  • 51.7k
4 votes
Accepted

Benefit of using JIRA issue key in fork based workflow

You have the name your branch something. Some benefits of adding the Jira number: If someone is sick (or hit by a bus) other developers can find the open branch easily, on the ticket number If you ...
Niels van Reijmersdal's user avatar
4 votes
Accepted

"Dev to QA handover" process improvement

There are a couple of different problems happening here that may be intertwined. Having a hand-off between a development team and a QA team is generally anti-agile. In order to achieve agility, teams ...
Thomas Owens's user avatar
  • 82.8k
4 votes
Accepted

Should the Jira assignee change for testing?

This depends on your workflow. Some teams that I've worked with do change the assignee from the developer to the tester when the work enters test. The fact that it doesn't look like a person has or ...
Thomas Owens's user avatar
  • 82.8k
3 votes

How do you include "global requirements"?

When talking about requirements, you have multiple types of requirements. User stories often capture a combination of functional requirements (inputs, outputs, behaviors) and user characteristics (...
Thomas Owens's user avatar
  • 82.8k
3 votes

How do you include "global requirements"?

Well, you're not going to address UI standards in your User Story if the User is another machine. You're going to have to decide if splitting out the "global requirements" is worth the risk of them ...
Robert Harvey's user avatar
3 votes

Scrum and backlogged issues

The Sprint is a team commitment. The Sprint belongs to the team. Only the team gets to decide how it will collectively fulfill the team commitment. If someone from another team is "assigning" things ...
catfood's user avatar
  • 1,615
3 votes

Advice regarding tools and insights from sprints on developer performance

Developers are professional problem solvers. Pick any metric you like and the developers will identify which ones you are using and game them, making the metric effectively useless. Or they will have ...
Kain0_0's user avatar
  • 16.2k
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
Ewan's user avatar
  • 76.3k
2 votes

GitHub with TFS ALM

You can. You can keep your code in GitHub and use both Build and Release tools in TFS or VSTS. What you loose is the ability to link work items to code. Everything else works just fine, ...
MrHinsh - Martin Hinshelwood's user avatar
2 votes
Accepted

Should I consider microservice as an epic or a project in TFS?

If you have resources that depend on each other, with resources being [people | work items | code], then they would all be in the same Team Project. You can easily have separate Teams (Backlogs, Work,...
MrHinsh - Martin Hinshelwood's user avatar
2 votes

How to model story preparation for issues which are tackled across several projects

If you want to track this in JIRA I would follow it through as if it were a new task. So for example: Let's say you have the story CORE-75: Foo the Bar. Once it is decided which team will take the ...
Erdrik Ironrose's user avatar
2 votes

A Git workflow where QA tests are integrated into JIRA issues

I would just add the tests to the same branch that the code being tested is in, either the feature branch or develop. You should want to frequently run your entire test suite and treat any failure as ...
bdsl's user avatar
  • 2,734

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