Moving a project forward
Choose a useful next step, use the material already available, and keep decisions and permissions clear.
Choose a useful next step
Start with a question to answer, a method to review, or a change whose effects need to be understood. Keep the wider goal in view, but give the next piece of work a clear boundary. A long-term project need not become one unrestricted instruction.
Use the material already in the project
E2C is intended to compare your goal with the work already done, recover the relevant requirements, and ask about what remains unclear. Existing reports and project files should provide a starting point. You should not have to rewrite them or map the entire project before an initial review.
Explain changes in ordinary language
Describe the new goal or change, and identify decisions that require you or another responsible person. Use what the existing material already explains, then clarify genuine uncertainties. Asking for an explanation of a change does not, by itself, authorize carrying it out.
Use guidance that fits the version
These are working principles, not step-by-step instructions for a released E2C version. Specific operating guidance and experience reports need a clear product version, context, and supporting evidence. The fictional stories explain an approach; they are not verified user results.