Having a quick and easy reference means the entire team has a clear direction on how they will deliver the next release. Pin them on a wall, or lay them out on a table to represent the work flow for this iteration. Give them to each developer, customer, analyst, project manager, etc so they know what to expect, what to do or how to do it.
Iterative Development - how to divide a project up, what to start on first and how to keep control of an evolving system...
Scrum (Agile methodology) - Scrum agile practices geared for software product development...
XP - eXtreme Programming (Agile methodology) - XP agile practices geared for enterprise software development...
FDD - Feature Driven Development (Agile methodology) - FDD agile practices geared for custom one-off application development...
Estimation - team-based estimation against a work breakdown structure (WBS) using sensitivity analysis...
Reflection - team brainstorming session to assess the development practices and outputs to look at areas to improve...
JAD Session - brainstorming session bringing together domain experts and end users to scope and prioritise the next release...
Use Case Analysis - modelling and capturing testable requirements through Use Cases...
Domain Object Model - key communication tool to convey the business/domain entities, their relationships, rules and constraints...
User Story - structured capture of features from the users' perspective, also incorporating the Test Scenarios (from the BDD perspective)...
User Interface Prototyping - Clarify requirements & ensure a user friendly solution; Communication tool between users and developers...
Architectural Requirements - defining the testable scope of your system architecture and reusable framework...
Architectural Modelling - key focus and representation to model the physical and logical architecture of the system...
Architectural Principles - key design rules that clearly state a durable idea about the structure of the system; key decisions in relation to the Architectural Model(s)...
OO Principles - the fundamental rules for guiding all OO designs...
Abstract Factory (design pattern) - OO design solution to create families of related or dependent objects without specifying their concrete classes...
Observer (design pattern) - OO design solution to automatically update dependent objects when another object changes state...
Decorator (design pattern) - OO design solution to add/withdraw responsibilities to/from objects dynamically and transparently...
Mediator (design pattern) - OO design solution to avoid objects referring to each other explicitly...
Class Diagram - the primary UML notation for modelling the domain objects and classes...
Sequence Diagram - the primary UML notation for modelling the run-time behaviour of the system...
Activity Diagram - for modelling business process workflows as well as complex algorithms/logic at the code level...
Automated Testing
- what to expect in a test framework, and how to go about building up a comprehensive automated testing environment...
Code Inspection
- powerful peer review technique that's highly effective in finding software defects, with many other benefits as well...
C++ Implementation
- the "do's and don'ts" of programming in C++ and how to avoid the various &gotchas& to ensure safer programming...
C++ STL
- summary of the key elements of the C++ Standard Template Library (STL) - strings, containers, algorithms...