Remove Definition Remove Document Remove Documentation
article thumbnail

The art of writing good documentation

Analysts Corner

Documentation is dead. All are good excuses for writing little to no documentation for your software projects. Because if good documentation “is a love letter you write to your future self” ( Damian Conway ), then no documentation is a trap you set for your future self. Documentation is hard.

article thumbnail

Documenting Acceptance Criteria: some ways to do that using text

Analysts Corner

Different formats of documenting detailed requirements using text such as Given When Then, Event-Response, and so on. Instead, I will focus more on the mechanics of documenting what the story writer was able to think of when writing a story and discussing it with the team.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Documenting Acceptance Criteria using process diagrams

Analysts Corner

In the previous post , I spoke about documenting user story acceptance criteria using text. Initially, I prepared requirements in the textual format (using “given when then” technique) and sent the document for the engineer’s review. Overall, we are talking about a full day of work spent on documenting requirements.

article thumbnail

Great books for business analysts that work in products

Analysts Corner

Here are some book recommendations covering everything from the product process and discovery interviews to problem framing and documentation. Problem/opportunity framing In product discovery, the definition of the problem is almost never clearly in front of you to collect and write requirements. This is crucial!)

article thumbnail

Aws Lambda Documentation

Whizlabs

AWS Lambda Documentation over the official website of AWS is highlighting the detailed explanations on the definitions, developer guide, API reference, and operations of Lambda. Follow onto this Lambda documentation article and elaborated sections below to get the fundamentals, basics, and in-depth knowledge of Lambda.

article thumbnail

Starting a New Project as a Business Analyst

Analysts Corner

Create a glossary of terms with the definitions and acronyms specific to the domain you’ll be operating in. Perform a document analysis of any publicly available document on the domain. Read any existing documentation , meeting notes, or important emails about the project. Access their website and their social media.

article thumbnail

Replacing Legacy. Part 1: Definition, Reasons, Characteristics

Analysts Corner

As usual, let’s start with a definition of “Legacy”: A legacy system is an old method, technology, computer system, or application program, “of, relating to, or being a previous or outdated computer system,” yet still in use. The “let’s-document-it-later” (never) approach in the long term becomes a significant concern.