Caimito One Team supports and fosters a number of important Agile Development techniques. The major screens Dashboard, Backlog, Release, and Iteration are used almost daily by all team members including stakeholders and product owner.

Dashboard

• Vision - Every time the dashboard is visited to check for project progress, who has left comments on issues or which items are new the vision document is displayed
• Transparency - There is no hiding. All project activity shows up on the dashboard and anybody who his part of the team can participate
• Trust - As progress is shown by graphs and live daily project updates, trust builds through transparency and objective information
• Real Customer Involvement - Customers (stakeholders) are encouraged to participate and respond to comments on user stories and bug reports as team members write them
• Daily Project Status- Daily Project Status shows iteration and project progress. Live project updates show new comments, new items, and workflow actions taken on items.
• Reporting - Live reports on all changes to important items and big visible charts showing project progress provide good reporting
• Collaboration - Team members, product owner and stakeholders collaborate by providing guidance and information through comments on issues. New comments are easily spotted in the project updates section of the dashboard.
  

Backlog

• User Stories - Requirements are captured as user stories in the backlog and ordered by importance
• Bug Reports - Reports about defects are captured in the backlog and ordered by importance
• Estimating - Team members estimate user stories based on complexity in points. Together with the importance of the issue this helps in planning the next iteration and provides an estimated release plan.
• Transparency - All currently known requirements and defects including importance and estimates are visible to everybody on the project
• Real Customer Involvement - Customers (stakeholders) are encouraged to enter themselves new requirements as user stories with the help of the product owner to give direction to the development team
• Incremental Requirements - The use of user stories and estimating in complexity encourages specifying requirements incrementally and closed the feedback loop with development.
• Documentation - All features of the software product under development can be documented easily

Release

• Velocity - Based on actual team velocity and currently known requirements a forecast of the project is shown
• Transparency - The estimated release plan shows the truth based on the current situation
• Risk Management - As the estimated release plan tells how many iterations are needed, issues may be assigned a higher or lower importance to meet deadlines with the most valuable product possible
• Trust - The team delivers what it promises. The estimated release plan avoids over promising by the team and disappointment for stakeholders
• Project Status - Based on known facts the current status of the project as a whole is always visible

Iteration

• Velocity - Iteration planning takes into account the true capacity of the programmers
• Transparency - Everybody on the project can see what the programmers and testers are currently working on
• Trust - Stakeholders (customers) can see which stories have been developed, which bugs have been fixed, as the work is being done
• Real Customer Involvement - Stakeholders (customers) can interact with the team, provide answers to team member's comments on issues and guide them
• Work task oriented - Team members know exactly each day what work needs to be done. They can use team tasks to coordinate work amongst themselves even if they are not physically in the same room.
• Daily Project Status - On more granular level the daily status of the iteration is shown by different colors (done, in progress, impediment)
• Done Done- Sub tasks may be used to coordinate between programmers and testers so that the whole team knows when the state of "Done Done" is achieved on a per issue basis
• Collaboration - Team members use comments on issues and team tasks to coordinate work amongst themselves.