21
votes
Accepted
should developers have a say in functional requirements
I fail to see how you can carry out requirements engineering activities effectively without the involvement of developers.
A business analyst or product manager may be very good at working with ...
- 19.9k
20
votes
What techniques can identify missing requirements?
I'm not entirely sure if that is still "project management", but what has helped me in my developer role is to actually take a day and do the work that my program is supposed to improve.
...
- 8,790
12
votes
should developers have a say in functional requirements
Everyone in a development team should take responsibility for and be involved in requirements gathering to some extent, otherwise you have barriers to effective teamwork.
"The best architectures, ...
- 6,345
12
votes
Lately discovered requirements in Scrum
If a requirement is discovered in the middle of a project or even later, then the cost of implementation of this requirement can be very high.
In this statement you are saying that the cost of change ...
- 19.6k
10
votes
Is it possible to be agile with a highly technical project?
Everything in your question suggests that you are exploring a new problem, not simply creating something you already know exactly how to build. Because waterfall asks you to create your design ...
- 16.9k
10
votes
Accepted
What techniques can identify missing requirements?
Software is never finished, merely abandoned.
Don't remember who said this first, but it's true. After you spend some time in the industry, you inevitably reach the same conclusion. And based on this, ...
- 15.5k
8
votes
Accepted
SAFe, are developers required to gather their own requirements?
TL;DR
Your company has not implemented SAFe; they have implemented Buzzword Management™. In this case, the interplay between roles has been applied incorrectly. Core responsibility for requirements ...
- 50.7k
8
votes
Accepted
Making backlog items independent - how that can be achieved?
You cannot totally eliminate dependencies. Some story will depend on another, some feature will need another feature to be built first, some new feature will be desired only after you see and interact ...
- 15.5k
8
votes
should developers have a say in functional requirements
Developer here. I have seen projects fail because a functional requirement was impossible to implement. I'll tell you a tale where I was involved.
We were working with a piece of hardware that allowed ...
- 180
6
votes
Could the Product Owner be a user of a user story in Scrum?
Two things come to mind.
First, if you can't trace the need to a stakeholder impacted by the system, is it actually a requirement? Unnecessary features and gold-plating is a waste, in the Lean sense. ...
- 19.9k
6
votes
Accepted
Could the Product Owner be a user of a user story in Scrum?
The only time the Product Owner would be named in a user story is if you are building a product that is designed for Product Owners.
I need to write some requirements affecting directly to the ...
- 19.6k
6
votes
Lately discovered requirements in Scrum
Prioritisation, continuous delivery and review is the way to control delivery risk for any software development, not just when using Scrum. I can't agree with the first sentence of your question ...
- 6,345
6
votes
Lately discovered requirements in Scrum
You say:
If a requirement is discovered in the middle of a project or even later, then the cost of implementation of this requirement can be very high.
This can be true or can be false. It depends ...
- 15.5k
5
votes
Accepted
Are Delighters equivalent to Gold Plating?
These are two judgement labels applied to the exact same behavior, based on the outcome. If you get it right, the customer is delighted. If you get it wrong, you gold plated and the customer is ...
- 37.2k
5
votes
Accepted
Documenting requirements on an Agile project
There are three agile principles that are at play:
"Working software over comprehensive documentation" from the Agile Manifesto.
"Simplicity--the art of maximizing the amount of work not done--is ...
- 19.9k
5
votes
Accepted
Doubt defining functional requirements
TL;DR
Every organization has its own way of defining requirements. There is no "one true way" to specify them. If you want to know how requirements should be written in your organization, you'll need ...
- 50.7k
5
votes
Is it possible to be agile with a highly technical project?
Validated Learning
Agile approaches involve validated learning. Wikipedia defines the steps of validated learning as:
Specify a goal
Specify a metric that represents the goal
Act to achieve the goal
...
- 50.7k
5
votes
Accepted
When requirement changes comes during the sprint, who takes the final decision to include or not
The final decision is up to the product owner. If it's really, really, really important, the product owner could just cancel the current sprint and start a new one with just this single story in it.
...
- 8,790
5
votes
should developers have a say in functional requirements
Anyone can have a say in the product requirements. Even the analyst's mistress may offer some input. That said, it is analysts' job to analyze, combine, synthesize, and prioritize both requirements ...
- 151
5
votes
Accepted
Is onboarding a non-functional requirement?
TL;DR: No. Onboarding is a waste.
Time and effort invested "Onboarding" is neither a functional or a non-functional requirement. In our project, we had failed to find how to address such ...
- 8,673
4
votes
Accepted
Should developers be talking to users during Story planning / refinement?
Yes, ofcourse, why should the development team settle for second hand information. Self-organizing teams should get the information from the source!
I really like this item from the Cargo Cult Agile ...
- 5,553
4
votes
Should developers be talking to users during Story planning / refinement?
In certain situations I think they should, but there are a lot of caveats and gotchas to it. Let me list out reasons I have done it, and also times when I would not do it and maybe that will help as ...
- 415
4
votes
How to deal with constantly (~daily) changing requirements?
I think the simple statement of your problem is that to plan you need to at least be able to count the number of things you need to do. However you have no base number right now besides the 800K & ...
- 261
4
votes
How to deal with constantly (~daily) changing requirements?
My first step would be to ask how you are doing Kanban?
Kanban is the go-to tool for rapidly changing requirements. The basic principle of "Have a board, have a WIP, prioritize daily", is incredibly ...
- 12.6k
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 ...
- 12.6k
4
votes
Accepted
Splitting up user stories that are enhancements that may destroy other functionality?
Very interesting problem. All three of those are potentially options, but the third seems the most likely. I could see the first if for some reason there was business benefit to stopping people using ...
- 16.9k
4
votes
Accepted
Diagram for mapping project dependencies or relationships
What you are looking for is a Visual Portfolio Map
Here is a good article that describes what a Visual Portfolio Map is and why you need one: How to Manage Interdependencies in a Project Portfolio.
...
- 11.1k
4
votes
Could the Product Owner be a user of a user story in Scrum?
Sure, the Product Owner can be a legitimate role in a user story. So can a Developer, or a Sys Admin, or so forth. The key thing is to identify the role who will benefit from the business value ...
- 3,659
4
votes
Accepted
Requirements vs User stories
While user stories can absolutely be considered a type of requirement, there are distinct differences between user stories and other requirements that I don't see here or in the accepted answer on the ...
- 16.9k
4
votes
How to make the correct requirement document with regards to agile & scrum?
In Scrum, we typically don't worry very much about writing requirements, let alone documents.
Scrum calls for a couple requirements "artifacts": the Product Backlog and the Sprint Backlog. The ...
- 489
Only top scored, non community-wiki answers of a minimum length are eligible