Rich project status

The status a colleague of mine prepared looks impressive with a lot of  information you can get fast. First of all blockers with red asterisks of being not removed and responsible persons in braces right there. And certainly comments to burndown.    

Software quality characteristics

ISO 9126 quality model for external and internal quality (characteristics and sub-characteristics).

Focusing on one external characteristic of software quality can affect other characteristics positively, adversely, or not at all (From "Code Complete 2")

Textual analysis

To identify the objects and classes in Software modeling, a textual analysis is performed: 
"One of the first steps is to create scenarios that in aggregate model the various dimensions of the problem domain. From those scenarios, you can identify potential objects, behaviors, and attributes. For example, select the nouns from the problem domain as possible future objects. The next logical step is to identify the verbs and verb phrases in the problem domain. These are potential behaviors. Finally, from the scenarios, identify the adjectives or other descriptive phrases that are potential attributes."

Performing the analysis on the higher level of abstraction, apparently it produces what Attribute-Component-Capability (ACC) model operates with: components (nouns), capabilities (verbs) and attributes.

Nurture Your Passion

Well-crafted software is a position that should be held. It seems that a passion should be considered as another ground to stand:
Take steps to protect and grow your passion for software craftsmanship.

From "Solid Code"

- Around 50 percent of the software development life cycle should be dedicated to phrases before coding
- Do not allow implementation consideration to affect the requirement analysis or design
- Do not assume that the software model is correct. Use various best
practices