8 votes

How do we prevent debates over whether changes to user stories are new work or bugs?

How do we capture enough details so that in a month or so, when someone in those discussions comes back and their memory of it was different from ours, we don't get into a debate/discussion over ...
  • 48.6k
8 votes

SRS for an Agile project

Many agile projects don't produce a software requirements specification in the sense of a document that lists a bunch of "shall" statements along with some assumptions and dependencies, like what is ...
  • 18.6k
7 votes

How should a non-technical person define tasks for technicians?

Stories should always be defined in business terms. Why does there need to be web integration? Who is it for? What exactly does it need to accomplish? If it is not directly-related to a business ...
  • 14.7k
6 votes
Accepted

How should a non-technical person define tasks for technicians?

TL;DR You should not be defining tasks for technical people. Instead, you should describe a value proposition and some testable acceptance criteria, and then turn your technical experts loose to find ...
  • 48.6k
5 votes
Accepted

Can a requirement be linked to another requirement?

Can a requirement be linked to another requirement? Yes, it can. Requirements can depend on other requirements. Or some requirement can be derived from another requirement. Requirements can also be ...
  • 14.3k
4 votes
Accepted

How to avoid recurring questions and contradictions about same or related problems?

You don't need a project manager to run this project. In fact, unless heavily empowered all a project manager is going to do is give the headache to someone else. What you need is to have a "product ...
4 votes

Technical Spec: Is more detail help or hindrance?

Document the minimum required for a proper, unambiguous implementation. It requires a lot of efforts from both analysts and implementors, so will depend a lot on your project environment maturity. ...
  • 8,540
3 votes

How do you keep documentation on long-term project?

We differentiate between documentation for: Developers: This goes right in the source code and will be stored in Git. Whenever a function is added or updated, some "text in green" (our wording for ...
3 votes
Accepted

Technical Spec: Is more detail help or hindrance?

This really depends on how you and your collaborators like/are expected to work, how much time you want to invest in getting things right, and how painful it is for you to not have some of the detail ...
  • 341
2 votes

Can planning documents be retroactively produced to fit the product that's been built?

Spikes and Prototypes are Okay; Retconning Project Plans Is Not I was planning to go onto the implementation phase and then to reverse engineer my work. From a project management point of view, ...
  • 48.6k
2 votes

How to manage business and technical requirements?

In Business Requirements Document: A High-level Review the author defines business requirements as making reasonable estimates of how big a project is and how much it is going to cost. He then ...
2 votes

How do we prevent debates over whether changes to user stories are new work or bugs?

Agile Manifesto says: Working software over comprehensive documentation but also! That is, while there is value in the items on the right, we value the items on the left more. So the answer ...
  • 394
2 votes

SRS for an Agile project

If you have a prototype, a vision document, Personas and some PBI depending on your project I dont think you need SRS. for more complex or enterprise applications you may want to add a UML doc but I ...
  • 197
2 votes
Accepted

How to maintain a spec for a large complex project with repetitive patterns?

I would make a Template Spec for the similarities. Then each product starts by referencing the relevant Template Specs and then noting the diferences. This way, when you change something system-wide,...
2 votes

How to describe the business entities in Scrum?

A user story is an invitation to a discussion. It is not intended to be a detailed specification. All the user story needs to communicate is the basics of a requirement and it is worded in such a way ...
2 votes

How to describe the business entities in Scrum?

There is nothing in Scrum that's keeping you from defining your business entities somewhere and then referencing them in the stories. The agile approach only means you should be able to change those ...
  • 8,053
2 votes

Is the client or vendor responsible for writing the BRD?

The team as a whole (developers and client) should take responsibility for creating any documentation. It's a collaborative effort and to maximise productivity the team should try to avoid having ...
  • 5,961
2 votes
Accepted

Should I write the performance or the architectural specification first?

As you noticed, the architectural and a performance specifications are interdependant. However, in most cases you are going to want the product to be as fast as possible - and therefore you want to ...
2 votes

Should I write the performance or the architectural specification first?

TL;DR Your question is about an academic exercise where the only "correct" answer is the one your instructor has previously provided, or whatever answer the instructor expects. Instead, I ...
  • 48.6k
2 votes
Accepted

Who speaks to the client when there are some errors in the documentation that the client delivered?

TL;DR Whatever your team is doing, it isn't Scrum. None of the roles, events, or theory defined by the framework are being followed properly, and even basic agile values like customer collaboration ...
  • 48.6k
1 vote

Technical Spec: Is more detail help or hindrance?

Is more detail help or hindrance? More detail helps until it becomes a hindrance :). In other words, the law of diminishing returns starts to apply at some point. Your developers will find some ...
  • 14.3k
1 vote

Technical Spec: Is more detail help or hindrance?

There are different approaches to the lifecycle of a project which are often described as ranging from "predictive" (define everything early and as fully as you reasonably can) to "...
  • 5,961
1 vote

How to write recommendation documentation?

This depends on what the target audience is for your propositions. More details to more technically-oriented people, less details for the people who controls budgeting. Architecture is always a high-...
  • 315
1 vote

How to manage misalignments between Design Specs and After Design Adjustments?

Sounds like your organisation uses Jira tickets as their central source of information, (i.e your SM looks at Jira tickets), so the Jira tickets should contain short comments on how the implementation ...
  • 11
1 vote

What questions to ask and how to create spec based on provided information

As noted in the comments you are really looking for the approach and thought processes of your candidate. Essentially you are looking for quality analysis (you are hiring a business analyst) and ...
1 vote

How to describe the business entities in Scrum?

TL;DR You're conflating a lot of things, and trying to convert the user story format into a new type of specification. It isn't one. Instead, you should modify your process so that everyone shares a ...
  • 48.6k
1 vote

How to describe the business entities in Scrum?

As others have said, the Scrum guide doesn't define business entities, but it does speak to them in principle. The Product Owner is responsible for maximizing the value of the product and the work ...
1 vote

How to avoid recurring questions and contradictions about same or related problems?

Communicate + collaborate with the person writing the tickets There's really nothing more to say than that. Having a process that looks like this, someone writes the tickets perfectly -> developers ...
1 vote

How should a non-technical person define tasks for technicians?

Imagine you are going to the hospital and meeting with a doctor to help you because you have chest pain. Do you tell the dr straight away "I have a heart problem, i just read webmd, I need a heart ...
1 vote

How do we prevent debates over whether changes to user stories are new work or bugs?

Document as much detail as you need to get the work done, which should normally include sufficient documentation for future support but not necessarily to complete further stories or defect fixes. I ...
  • 5,961

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