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 ...
user avatar
9 votes

How to motivate my team members to start documenting their work

You've identified a risk, and a possible solution. I'd refrain from considering your solution (more documentation) as "the" solution and ask them to apply it straight away. You're working with a team ...
user avatar
  • 1,001
9 votes

Failed to finish project in time, now threatened with UK court

Your first course of action should be to secure some legal counsel and get their opinion. Asking a message board for legal advice is only marginally better than doing the same for medical advice... at ...
user avatar
  • 8,879
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 ...
user avatar
  • 16.7k
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 ...
user avatar
  • 17.7k
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 ...
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 ...
user avatar
7 votes

How to motivate my team members to start documenting their work

@Mamoo is right. A new and junior project manager does not have the authority or influence to jump to a solution and ask the team to implement it. Even as a two decade project manager I wouldn't try ...
user avatar
7 votes

What does MOS and RA stand for in IT project?

Context Matters Acronyms and initalisms are useful shorthand when discussing a problem domain with others who share the same lexicon. However, such shorthand is highly contextual. For example, an "R....
user avatar
  • 47.9k
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 ...
user avatar
  • 16.7k
6 votes
Accepted

How much code documentation should an effective Scrum Team produce?

There can be no general answer to this. Multinational or public companies do vary greatly. Software developed by such companies varies even more in size, type, purpose, usage, life expectancy etc. In ...
user avatar
6 votes

How much code documentation should an effective Scrum Team produce?

Well the answer is really "It depends" mixed with "Why do they need it?" and "What's the least you can get away with?" This is really about interviewing your stakeholders and doing a 5 Why's type ...
user avatar
6 votes
Accepted

How to motivate my team members to start documenting their work

Documentation is always the stepchild of development. Although you could simply order them to do it, there are a few points to take care of when you want to motivate them: Demonstrate the problem Have ...
user avatar
  • 7,650
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 ...
user avatar
  • 47.9k
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 ...
user avatar
  • 17.7k
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 ...
user avatar
  • 8,381
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 ...
user avatar
  • 47.9k
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 ...
user avatar
4 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?

One of the four values of agile is "Customer Collaboration over Contract Negotiation." The first thing to ask is "what is best for the customer?". Once you've done that, then you ask "is it covered ...
user avatar
4 votes
Accepted

When does one develop a RASCI?

The RASCI being developed is intended to highlight the support model going forward. From my perspective a RASCI encompasses all aspects of the project including handover. It can do both, or neither. ...
user avatar
  • 856
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 ...
user avatar
  • 14.7k
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 ...
user avatar
  • 41
3 votes

Documenting business & technical decisions, changes, updates and so on

Many of the design or project management decisions are the result of "trade-off analyses", and trade-offs are a method for validating requirements and/or designs. A sound Systems Engineering approach ...
user avatar
3 votes

Documenting business & technical decisions, changes, updates and so on

Tracking Specifications and Strategic/Architectural Decisions I want to know why we made the decision to implement a module in a way and why we changed it afterwards. This can be driven at several ...
user avatar
  • 47.9k
3 votes

How does one bridge the gap in producing deliverables between operations and projects?

Welcome to StackExchange- Project Management. This is not an uncommon issue in large enterprises. Clear ownership of deliverables can be a challenge. Given you're new, you probably are in a good ...
user avatar
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 ...
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 ...
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 ...
user avatar
  • 16.7k
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 ...
user avatar
  • 2,323
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 ...
user avatar

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