This template is a useful way for you to frame your project, to communicate and verify your understanding of its requirements, and track any cross-dependencies with other projects or students. Remember to work with your mentors to verify your assumptions at each stage, and to update this page as your understanding of the project evolves.
Paste the original project description here.
If you have questions about the project description or any part seems unclear, put your questions here.
Write some stories that describe how this feature will be used by users. What type of user(s) (system admins, developers, other) does the feature benefit? How does it benefit them?
What are the ways that users will experience the ideal outcomes of this project? Does your project involve exposing some kind of user interface? This interface might be exposed to the user through the web client, or perhaps it’s a command-line interface. In either case, document interface design decisions here. Wireframes, mock-ups, scanned drawings or links to prototypes are very useful to include here.
What kind of changes will be needed within Review Board’s system of components in order to implement this project? Will new Web API resources be required? Will it require changes to how the extension system works? Will it require changes to the database? Will changes need to be made across components? (Djblets, RBTools, Review Bot, etc).
Are there any other projects that are working in the same area as yours? How are they breaking down their projects? What kind of coordination will be required between you? If you’re dividing any responsibilities between one or more other projects, have each project planning page link to a separate Notion page documenting those decisions in this section.
Is it possible to scope this project down into a “Version 1”, a “Version 2”, etc? Breaking your project down this way might make it easier for you to measure your progress. If scope it down that way is possible, document that scope-down here for each version.