2.2.1 – Definition of DONE
Defines what the Product Owner (P.O.) will consider when evaluating the Item presented by the team as Done, during the Sprint Review Meeting. Informational only.
Ex.: Modeled, coded, tested and working.
2.2.2 – Definition of READY
Defines what is a Ready User Item, i.e., a User Item that can be considered for inclusion in a Sprint, in this specific project. An Item at a Ready state should be good enough to be included in a Sprint, in order to be worked on by the team. Informational only.
Ex.: Detailed use case with all alternatives contemplated and sketches of screens to be used.
2.2.3 – Website
A link to your project’s site. Only informational.
2.2.4 – Twitter
Your project’s Twitter account. Project’s notifications will be tweeted using this account. We suggest you create a private account on Twitter and add only project members to it.
2.2.5 – Timebox
The timebox to be used on your Sprints, in weeks.
2.2.6 – Initial Velocity
The velocity you consider for the first sprint of your project. It will be used as the base velocity for the average calculation.
2.2.7 – Planning Velocity
It is used to help with the planning process. The velocity defined here appears on a horizontal dynamic bar on the Product Backlog. It helps the user visualize which stories will be included in the next sprint.
2.2.8 – Non-Estimated Stories
The amount of points you want the system to consider for a story that has not been estimated. It helps on planning. We recommend the use of the average story points.
2.2.9 – Language
The language to be used on BeePlus’s notifications.
The interface language is defined on User-Settings.