Documenting processes is something most business analysts have to do. The goal of documenting the process is to communicate requirements. By establishing a shared understanding of the process, you can establish the context for the requirements. Easy processes are easy to draw and understand. When documenting a more complex process, you need to provide the same clarity and consistency. In this article we show how to document asynchronous process steps to maximize the clarity of the documentation.
Subscribe to Tyner Blain
Search
Pages
Archives
Categories
- Administrivia (32)
- Contest (1)
- Austin TX (11)
- Business Analysis (171)
- Business Rules (13)
- Consulting (103)
- Communication (90)
- Presentation (15)
- Writing (39)
- Outsourcing (8)
- Communication (90)
- Data management (3)
- Definitions (6)
- eCommerce (6)
- Expert systems (3)
- Flashback (75)
- Foundation series (22)
- Interface Design (11)
- Interviews (2)
- Lists (26)
- Marketing (27)
- Organizations (12)
- IEEE (1)
- IIBA (4)
- ProdMgmtTalk (2)
- ProductCamp (4)
- People management (4)
- Polls (10)
- Process Flow (5)
- Process Improvement (73)
- CMMI (10)
- Product Management (278)
- Product Strategy (10)
- Project Management (60)
- Quick Post (1)
- Requirements (369)
- Prioritization (50)
- Requirements gathering (108)
- Requirements management software (14)
- Requirements Models (168)
- Ishikawa Diagram (19)
- Kano Analysis (11)
- Software requirements specification (57)
- UML Modeling (12)
- Use Cases (68)
- User Stories (11)
- Reviews (11)
- Book Reviews (8)
- Software Reviews (3)
- ROI (41)
- Slightly off-topic (36)
- Software development (269)
- Agile (127)
- Design (16)
- Testing (47)
- Test Automation (25)
- UX (67)
- Interaction design (31)
- Usability (21)
- Success Stories (1)
- Uncategorized (18)



