Product Setup

Present the scope from your project plan to set a common goal with your team. This can be done in RTD Manager in the project setup section. There is even a place for the charge number that your team will need to use for billing purposes.

Step 2: Identify Team and Set Roles

Identify team members and their roles (lead developer, testers, quality, subject matter experts/end users, technical writers, etc). In RTD Manager, this can be done on the project setup page.

A very high-level plan for multiple Sprints (e.g. three or more iterations) is created to capture the time to develop the main features.
It is a guideline that reflects expectations about which features will be implemented and when they are completed. It also serves as a base to monitor progress within the project.
Compare this plan to the schedule. If the release plan is longer than the stakeholder's schedule, work with the stakeholders to identify additional items that may be optional [objective requirements].

No project is risk-free. Identify early-on the following...
- Purchases required for new tooling, development tools, licensing, etc.
- Any new technology/tools or computer hardware issues the team may encounter.
- Unforeseen circumstances that may create hiccups such as 3rd party dependencies.
- Extended absences of any team members.
Present a risk management strategy to make sure you're prepared.
- Tip: Tackle high-risk items early in your project timeline, if possible. Or create a small "time buffer" around the task to help keep your project on track in the event of a delay.

Share with your team ahead of the meeting.
Ensure your team members understand the task before presenting to the stakeholders.
- Tip: Keep your kickoff meeting as short as possible. Now is the time to establish yourself as an effective leader and earn your customer and team's confidence.