Advanced Topics in Disciplined Agile

In Disciplined Agile, the correct approach to documentation is to create just enough documentation at the right time to address stakeholder needs. This aligns with agile principles of delivering value efficiently while maintaining necessary documentation.

This approach ensures:
- Documentation remains relevant and useful
- Resources are used efficiently
- Stakeholder needs are met appropriately
- Documentation evolves with the project

The other options are incorrect because:
- Creating comprehensive documentation upfront is wasteful and goes against agile principles of adaptive planning
- Waiting to document only final implementations misses crucial design decisions and context
- Focusing solely on technical specifications while reducing business documentation creates an imbalance and fails to serve all stakeholders effectively

The key is finding the right balance - creating documentation that provides value while avoiding unnecessary overhead.

In Disciplined Agile, collaborative modeling is most effective when done in small groups because:

Small group modeling:
- Promotes active participation and engagement
- Enables real-time feedback and adjustments
- Facilitates shared understanding among team members
- Aligns with agile principles of collaboration and interaction

Why other approaches are less effective:

Individual modeling and later combination creates silos and reduces collaborative benefits, leading to integration challenges and misaligned understanding.

Starting with comprehensive documentation is too waterfall-like and delays valuable feedback loops that could identify issues early.

Focusing on technical specifications before business stakeholder involvement risks building the wrong solution and misses crucial business context that should inform the modeling process from the start.

The small group approach best supports Disciplined Agile's goal of balancing agility with appropriate governance while maintaining effective collaboration.

In Disciplined Agile, models and documentation should be stored in a central repository with version control and team accessibility. This is the best practice because:

Benefits of central repository storage:
- Ensures single source of truth
- Enables version control and change tracking
- Facilitates team collaboration
- Provides easy access for all team members
- Maintains data consistency

Why other approaches are inadequate:

Email sharing is problematic because it:
- Creates version control issues
- Makes tracking changes difficult
- Can lead to outdated information

Multiple storage locations:
- Creates confusion about latest versions
- Increases risk of inconsistencies
- Makes maintenance more complex

Physical documentation library:
- Limits accessibility
- Slows down information flow
- Creates unnecessary bureaucracy
- Does not align with agile principles of quick access and collaboration