Small releases provide quick feedback about what is needed, what is actually done, and how fast the team can be going. When you lengthen your release cycle, recognize that you are risking larger amounts of time and money without that feedback. Consider how to get the information and confidence that small release provide so readily. Frequent planning , of iterations and releases, communicates what's needed in the light of what has gone before. Decisions are based on knowledge rather than guesses.
Feedback is high, learning is rapid, and communication is maximized.
Learning what can be done and how long it takes is increases confidence. When adjusting your approach to planning, recognize these benefits and find ways to replace them. Metaphor, a compact mental image of the system is a communication mechanism. It gives the programmers a common understanding of how things work, and how things should work. It helps keep the design simple and clear, helps programmers guess what needs to be done and how.