From UG
(Difference between revisions)
|
|
| Line 1: |
Line 1: |
| - | [[Category: PM (public)]] | + | [[Category: XArc]] |
| - | | + | |
| - | == About 9002 years ==
| + | |
| - | | + | |
| - | This is folder with various reflections by PM and Sys Architect.
| + | |
| - | | + | |
| - | == Chronologically ==
| + | |
| - | | + | |
| - | === June 2010 ===
| + | |
| - | | + | |
| - | '''[[Dividing project into subprojects]]''' ''[work in progress]'' - about one of the most important tools of Solution Architec, reason why, how to do it, examples.
| + | |
| - | | + | |
| - | === Future articles ===
| + | |
| - | | + | |
| - | * '''M2M vs E2E''' - one design is when 2 mutually remote teams connected by Managers. Another when Engineers connected directly after manager forms a team.
| + | |
| - | | + | |
| - | * '''What is the strategy for documentation?''' - who is to write and manage spec? Engineer/Developer or Sys An/Proj Manager?
| + | |
| - | | + | |
| - | * '''How to organize?'''
| + | |
| - | | + | |
| - | Many ways to ogranize. But as long as a way covers a list of core activities it does not matter who is doing what and in what sequence:
| + | |
| - | | + | |
| - | * Client requests solution
| + | |
| - | * A fully captured biz reqs
| + | |
| - | * B well documented biz reqs
| + | |
| - | * C created design/solution
| + | |
| - | * D documented design/solution
| + | |
| - | * E codes sol
| + | |
| - | * F tests sol
| + | |
| - | * G supports sol:
| + | |
| - | ** bugs
| + | |
| - | ** tweaks
| + | |
| - | ** questions
| + | |
| - | | + | |
| - | * number of reviews defined
| + | |
| - | * communication links between X and Y are well defined
| + | |
Current revision as of 23:16, 8 December 2011
Pages in category "9002 years"
This category contains only the following page.
D
