422
Study finds 268% higher failure rates for Agile software projects (www.theregister.com)
submitted 2 years ago by to c/programming@programming.dev
135 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 2 years ago (1 child)

The difference is in exact wording Agile: the software shall properly authticate a user within our active directory.

Documention : user authentication will be provided by functions ”valisate username” as described in section 14,7 subsection 4, ”validate password” as described in section 16.2 and validate the correct pasword as described in section 23.4.Proper authication to the correct use group shall comply with the requirements in document 654689 section 64.7 subsection 17

Yes there is a difference and one is better....

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 2 years ago (2 children)

    So you started with the need to authenticate, which should be documented in the requirements. You know, the things that are required to happen.

    The details on HOW to authenticate are ALSO documentation. Not all documentation describes functionality.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    So you started with the need to authenticate, which should be documented in the requirements. You know, the things that are required to happen.

    I think you're confusing documentation with specification.

    Requirements are specified. They are the goals and the conditions in which they are met. Documentation just means paper trails on how things were designed and are expected to work.

    Requirements drive the project. Documentation always lag behind the project.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 2 years ago (1 child)

    If you write it down it is documentation. When requirements are written down, they are documented! Requirements are not the same thing as specifications either, but both are documentation!

    You are saying that only technical documentation counts as documentation.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 2 years ago

    If you write it down it is documentation.

    I think you're not getting the point.

    It matters nothing if you write down something. For a project, only the requirements specification matters. The system requirements specification document lists exactly what you need to deliver and under which conditions. It matters nothing if you write a README.md or post something in a random wiki.

    Requirements are not the same thing as specifications either, but both are documentation!

    https://en.wikipedia.org/wiki/System_requirements_specification

  • permalink
  • fedilink
  • source
  • parent