We will journal our Ruck innovations dog-fooding (see Proposed innovations … a byte for your thoughts? and Proposed innovations to the v1.2 guidance. Thoughts? for details) as part of the vsarSecurity prototyping project.
This ensures that we have a transparent record when we eventually update our guidance based on dog-fooding feedback, that our Ruck masters have a point of reference and that we can get your candid feedback.
… candid feedback is always welcome
where are we in the process?
As shown by the yellow area we just completed the kick-off and are in the process of establishing a vibrant team.
create a new team ecosystem
- Create a new project team, called vsarSecurity, and add project lead and ruck master as team administrators.
- Create a TFVC folder and appropriate subdirectories, using the TFS Branch Tool or doing it manually.
- Assign the iterations to the project.
- Add the features as presented at the kick-off to the backlog and link them to the flight (epic). At this stage we do not have the epic type on VSO and are using a feature work item, that has children features, as our flight (epic).
- Add a program manager (PM) pbi, add the draft objectives and acceptance criteria and link it to its parent flight (epic).
- Add the default stories to the pbi and assign the innovations stories to the project lead (PL) and the planning stories to the ruck master (RM). We believe that the demo video can be done in a full-time day, the planning and innovations in less than a day, and are therefor assigning 1, 0.5 and 0.5 story points respectively … the team can (should) revise these defaults.
- Customise our backlog board to contain a current sprint and a ready for review column. The idea is that stories relevant to the current sprint are moved to the “current sprint column”, stories under development will sit in the committed column and stories ready for final testing and signoff in “ready for review” column.
Remember a story is only done when both the developer and the tester of the story pair give the sign.
- Refine our team home page, using tiles and light-weight graphs.
- Create a team mail distribution list (DL).
what’s supposed to happen next?
- Commit the team, which will include the program manager (PM), project lead (PL), ruck master (RM), product owner (PO) and <10 team members made up from developers/contributors and/or testers/reviewers.
- Update the mail DL accordingly.
- Schedule the training, research and planning (TRP) sessions well in advance to allow team members to plan the TRP sprint.
- Schedule the weekly 15+15min stand-up meetings, which typically start during the TRP sprint or the first Development (DEV) sprint.
- Go, go, go with the TRP sprint. In out case we start on 17th March for a 2-week TRP adventure.