Skip to main content
13 votes
Accepted

Where does documentation like business and software requirement spec docs fit in an agile project?

In the manifesto for Agile software development one can read: Working software over comprehensive documentation This doesn't mean documentation is a bad thing. Instead, working code is better so ...
Tiago Peres's user avatar
  • 2,084
9 votes

Where does documentation like business and software requirement spec docs fit in an agile project?

I encourage people not to think of user stories (or backlog items of any kind) as another form of requirements. There is a critical difference in thinking between the use of requirements documents and ...
Daniel's user avatar
  • 16.9k
8 votes

How can we speed up code reviews without sacrificing thoroughness of the code reviews?

A couple of suggestions: Code Quality Tools It is worth thinking about using automated code quality tools like Findbugs, PMD and Checkstyle. Ideally get the team to agree on a set of coding ...
Barnaby Golden's user avatar
8 votes

Does it make sense to require developers to write a "business value add" section in each issue?

Here's my TL:DR answer: No! The engineer shouldn't be working on something if the business value isn't already defined. It's the voice of the customer (product manager, product owner, business ...
Joel Bancroft-Connors's user avatar
7 votes

How to refer to functional requirement specifications (FRS) from user stories?

You've basically hit on the purpose of user stories. You see, user stories arose when we had large requirements documents that had all of the details the dev team could possibly need to develop the ...
Daniel's user avatar
  • 16.9k
6 votes
Accepted

What documentation is required for behavior-driven development?

Input Artifacts for Behavior-Driven Development (BDD) For successful behavior-driven development, you need (mostly) the same documents you'd need for any other agile project, with the addition of ...
Todd A. Jacobs's user avatar
  • 50.5k
5 votes

Does it make sense to require developers to write a "business value add" section in each issue?

Leadership 101: Do not force the team to do something for the sake of doing something. On the surface, it seems to be a very nice idea, being poorly implemented. The straight answer for the ...
Tiago Cardoso's user avatar
  • 8,653
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 ...
Thomas Owens's user avatar
  • 19.5k
5 votes

How to refer to functional requirement specifications (FRS) from user stories?

TL;DR The short answer is that you don't. Big, upfront planning is orthogonal to agile development. Instead, you should focus on iterative and incremental development with tight feedback loops to ...
Todd A. Jacobs's user avatar
  • 50.5k
5 votes
Accepted

How to approach this: A team member with Good technical skills but weak in other areas

This is a situation most of us as project manager face in real life. The good part of this situation is that the issue and the reason are pretty transparent, and there is no lack of openness within ...
Vinith K. Venugopal's user avatar
4 votes

Does it make sense to require developers to write a "business value add" section in each issue?

this is the job of the engineer working on the issue as they're the one most familiar with it. Technically, no. The engineer working on the issue is the one most familiar with the technical details ...
Sarov's user avatar
  • 14.8k
4 votes

Where does documentation like business and software requirement spec docs fit in an agile project?

Customer-side BA here, currently in the middle of a large-scale enterprise data warehousing and infrastructure modernization initiative. The project teams use Jira instead of TFS, and though the ...
JJ Ward's user avatar
  • 41
4 votes

What should be cover in Functional and Non-Functional requirements for a network project?

Functional Requirements Describes what the system should do or be capable of doing Typically if functional requirements are not met, then the system will not work (at least not in its entirety) The ...
Spectrem's user avatar
  • 151
3 votes

How can we speed up code reviews without sacrificing thoroughness of the code reviews?

Are the goals that the review can be audited? or to prove the auditor is doing his/her job? We document them as new tasks/discoveries on our Scrum-board and some just picks them up. I think the main ...
Niels van Reijmersdal's user avatar
3 votes

Where to start in agile-based documentations and what are the best practices to start with?

Code is your most useful documentation because it's the only document that's always up to date. Ensure your code is easy to read: well structured, well named and commented where necessary. Beyond ...
Kempeth's user avatar
  • 1,623
3 votes

User documentation and technical writer in Scrum

In Scrum, the ideal would be to have all skills needed to deliver the product on the team. If part of your product includes user documentation, then that skill should be on the team as well. Note that ...
Daniel's user avatar
  • 16.9k
3 votes

User documentation and technical writer in Scrum

the dev team create user documentation still The reason for this is, that the team should be wholly responsible for the delivery of the sprint commitment. If part of this work includes technical ...
user32613's user avatar
  • 2,436
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 ...
Frank Blome's user avatar
3 votes

Where does documentation like business and software requirement spec docs fit in an agile project?

Documentation as code is the key phrase here. Modern testing frameworks combine english readable content with the instructions to perform the actual testing, system calls, UI interactions, etc. ...
Michael Durrant's user avatar
3 votes

How to refer to functional requirement specifications (FRS) from user stories?

I think part of the problem is that this: login with my username and password is not a requirement. It's a design choice masquerading as a requirement. The real requirement is something like: "...
pgs's user avatar
  • 131
3 votes

How to approach this: A team member with Good technical skills but weak in other areas

As a project manager, you want to take the most from people and at the same time offering an environment where motivation of knowledge workers is taken into account. One of the key aspects of ...
Tiago Cardoso's user avatar
  • 8,653
3 votes

How to approach this: A team member with Good technical skills but weak in other areas

If you include a proper definition of documentation in the definition of done, it will start affecting this developer's performance. Then the developer will have two choices; Work properly on ...
Nezih TINAS's user avatar
2 votes

How to document existing products and their development?

For the sake of being straight forward, here goes. Start now, start small. Goal, KPIs, and user flow should be enough to get you started. Document those things appropriately before going any further. ...
Amir Syafrudin's user avatar
2 votes

How should a project manager handle a request for contracted software to produce twice as many reports as specified in the project's requirements?

TL;DR At this stage, the project manager's job is to provide a framework for the companies to address scope, and to estimate the budget and resources needed to deliver that scope. That's it! In ...
Todd A. Jacobs's user avatar
  • 50.5k
2 votes

Documenting requirements on an Agile project

The Agile thinking suggest the best practise is to document just enough. If you need to document something for a good reason, document it! In software development each project has its own needs, ...
Niels van Reijmersdal's user avatar
2 votes

Does it make sense to require developers to write a "business value add" section in each issue?

Does it make sense to ask engineers to put a Business Value Add section in each issue they work on? No, not really, but you may want to do it anyway. Ideally, the person who asked for the feature ...
RubberDuck's user avatar
  • 1,370
2 votes

What is a project book?

In this case, the project book needs to be what your teacher thinks it should be. I've never created a "project book" in all my time working on projects. It is likely a specific term some people use ...
Joel Bancroft-Connors's user avatar
2 votes
Accepted

Where to start in agile-based documentations and what are the best practices to start with?

There is an anti-pattern in many agile shops where they devalue useful documentation, likely due to a belief that "just read the code" is a reasonable answer. The cognitive load for reading a few ...
Zee Spencer's user avatar
2 votes

User documentation and technical writer in Scrum

The development team is responsible for producing the product. All of the product. Period. So either the development team needs to do what's described in the definition of done, or the whole Scrum ...
nvoigt's user avatar
  • 8,515

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