Add "intro graphics"

[gernotstarke]

to give an overview.

An (enhanced) version of this "info graphic" might serve as an overall navigation

[gernotstarke]

[aheusingfeld]

I like the overall idea of that circle made of 3 arrows which circulate around the crosscutting concerns. Regarding the content let's do a hard one:

1. let's come up with suggestions for the 3 most important Words (or 2-word-terms) in each section
2. Vote which ones are most important
3. Take the top 5 ;) of each section and put them on the graphic

[aheusingfeld]

BTW: I think I love the idea of having icons in there! If we manage to have them in and still not too much content to overwhelm readers, it'd be awesome!

[gernotstarke]

I'm lacking ideas what (else) to include in "evaluate". One idea: add "check the success of improvements" (our fundamental principle: validate improvement, turned into a practice)

The other "keywords" in the circle are ok, imho, at least until we come up with better proposals.

[aheusingfeld]

Ok, here is my first take

analyze

• find issues
• collect improvements
• separate both
• make them measurable

evaluate

• calculate issue cost
• estimate improvement effort
• ingest interval estimation

improve

• improve value
• prioritize by impact

crosscutting

• issue-improvement-relations
• common constraints
• perpetual principles

[gernotstarke]

thanx Alex - I propose: slight modifications in wording, move some entries...

analyze

• understand system
• find issues
• collect improvement options

evaluate

• estimate issue cost
• estimate improvement effort
• estimate in intervals

improve

• improve value
• improve quality

crosscutting

• manage issue-improvement relations
• plan improvements
• handle constraints

[MichaelMahlberg]

Without looking at the diagram or the previous answer (but looking at the guide itself):

Analyze

• Inspect System
• Collect Issues
• Inspect Environment

Evaluate

• Financial model
• Implications (Kano-model, liquidity etc.)
• Trade-Offs

Improve

• Modify system
• Modify Environment
• Iterate

Crosscutting

• Plan
• Negotiate
• Verify

Ceterum Censeo (now also in #216 ):
As I said before: There are more things to consider for "evaluate" than we currently consider...
(see #216)

[MichaelMahlberg]

I actually like @gernotstarke's current list best, I just would not go with "estimate in intervals" because to me that is on a different level of abstraction. (And it is not about what to do, but how to do it)

I would suggest "build financial model" but that is more than two words...

[gernotstarke]

Slightly simplified the version from my first comment, re-colored according to brighter color schema:

[gernotstarke]

included this image here: http://aim42.org/apply/getting-started/