(3 votes, average: 3.33 out of 5)
Loading ...
Traditional requirements happen after a multi-system architecture has been defined.
But what about the requirements that feed into that architecture? The requirements that drive the enterprise architecture decisions in the first place? We haven’t talked about those before.
(3 votes, average: 3.67 out of 5) Loading ...
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.
(2 votes, average: 5 out of 5) Loading ...
Product managers are often described as the hub or center of a software development organization. Saeed Khan takes umbrage with this under-appreciative image in an awesome article about information flow, product managers, and the SDLC.
Subscribe by RSS
(more...)
Subscribe to comments RSS
Add Tyner Blain to Google Toolbar
(help)
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Jul | ||||||
| 1 | 2 | 3 | ||||
| 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| 18 | 19 | 20 | 21 | 22 | 23 | 24 |
| 25 | 26 | 27 | 28 | 29 | 30 | 31 |
 |
These articles are written primarily for business analysts and product managers. Hopefully they help with thinking, doing, and training. Welcome aboard and let us know what you think!
