Orcas

We are busy building the next generation of Orcas. We are looking at this project not only as a potential significant boost to the way we build software but also as a test of Rails and its ability to deliver on its many promises.

The functionality that we are committed to delivering is listed below. It's meant to be a binding public declaration that will handcuff us and make us wish that we never posted it.

This will be a highly iterative process where we get your feedback early and use it throughout the 2 weeks. There will be a release at least daily and will be based on the schedule below. The first release is tomorrow and new functionality will be deployed every day. We are counting on you to provide feedback.

Keep an open mind. The polish will not be on until late next week. Success in this project will be a major boost to this team.



PROJECTS/SPRINTS
Ability to extensively tag and search projects
Ability to track a log of the history on a project
Specs tied to a project and the ability to include attachments
All the data that is tracked on a project in Walrus has to be tracked. This includes test and test attachments.
Projects tab. (Replaces the Walrus spreadsheet)
Project tab defaults to current user but can use “*” or “JPC MP DMD” to filter the projects.
Sprint building that leaves out no current functionality.
Moving or automoving projects into the next sprint
The ablility to stage projects in some kind of “next sprint” area
The ability to rapidly add projects
SPRINT METRICS AND HISTORY
Calculate sprint metrics so they don’t have to be manually calculated
Provide history of sprint metrics (the ability to run metrics over previous sprints)
Metrics are velocity, allocated, incidents, hours, defects, rework%
Include burndowns
TODAY
Ability to track “Today” must and nice to have “Tasks”
Ability to create “Today” tasks associated with projects or to drag in the project.
Clear and easy to use flow for entering “current est”, “actual hours”, and “status” of my projects
Allow for edit of all and one click submit. (Or better yet it would work like Google spreadsheets)
Developers’ daily updates of project status should be done in the “Today” tab
Display “Today”s turtle scales
Avitars
WIKI
Build new pages
Edit existing pages
TESTING VIEW
Provide the spreadsheet that Conrad works from to build scripts
BALLS
The ER board that shows the drama at a glance (id, description, customer, date due, last contact)
Track the log of all contacts
Ability to extensively tag and search balls
Log style tracking on balls
REQUESTS
Backlog management (the customer request list)
DEFECTS
Ability to view defect and bugs and display a metric that shows the state of the software
DASHBOARD
the most recent events
usage stats off the login screen
current defect state
defect metric
CONTEXT CAPTURE / WEEKLY REVIEW
Easy to generate “current week” review and “current month” review
Context capture and the ability to generate summaries/reviews over a specified period of time
Track both general ideas and context tied to a project
EMAIL NOTIFICATIONS
Ability to “subscribe” to a project or ball and get emails when it changes
MOMENTUM VIEW
Ability to view the momentum of the team at a glance
ROCKS
View of your top 5 priorities for the quarter
View of all everyone’s top 5 priorities for the quarter
The “ladder” up though the strategic plan
DATA IMPORT
Test Walrus import early in order to test with meaningful data
Import Walrus data to cut over