Reuse (ii): Definition of Done

As I said in my previous post, our project has suddenly taken a new path. There are two bits of collateral which I'd recently produced which will now no longer be required. Here are the notes for myself, and anyone else who might be intetested.

Part (ii) - Definition of Done

INTEGRATION READY

• Code Committed (associated with Task and commented meaningfully)
  
• Code Review (if required / requested) Completed
  
• Unit Tested
• Static Analysis Checks (Findbugs, PMD, Checkstyle, Cobertura) passed based on thresholds
  
• Acceptance Tested against Acceptance Criteria
• Story / Defect, Design Decisions, and Test Plan, Conditions and Results documented on Wiki
• Acceptance tests automated and added to Regression Suite
• Story / Defect added to Release Note (including installation and admin instructions)
• Story and all Tasks updated and set to "Ready for Review"

INTEGRATED AND RELEASED

• System Integration Testing completed
• Test Plan, Conditions and Results documented on Wiki
• Release tagged in SCM
• Maven version numbers updated
• Artifacts published to Artifactory
  

Reuse (i): Way of Working

Our project has suddenly taken a new path. There are two bits of collateral which I'd recently produced which will now no longer be required. Here are the notes for myself, and anyone else who might be intetested.

Part (i) - Way of Working for an Agile Distributed Team

• 3 week iterations (all teams starting and ending on the same days)
  
• Sprint Planning with the teams (Planning Poker for Stories, hours for tasks)
• Daily Scrums (3 questions plus "What have your learned?")
• Prioritised Backlog (Stories for the next-up phases, Use Cases for further out, Epics beyond that)
• Product Owners own Product Backlog
  
• Release Plan (always visible with named internal releases each iteration)
  
• Defects, Technical Stories (NFR's) and Technical Risks on the Product Backlog too
• Cross Functional Teams (UI Designers, Product Owners, Designer / Developers, Testers)
• Core Services Team (Environments, CM, CI, DBA)
  
• Crozz Timezone Teams (no primary location - Scrum Masters could be anywhere)
• Scrum of Scrums (meeting 2-3 times a week)
• Demos each iteration with client Acceptance / Signoff
• Empowered Onsite Clients (but not full time)
• Retrospectives every Iteration
  
• Definition of Done (see part (ii))
  
• Automated Integration Tests (captured with Selenium from Wireframes before development)
• Automated Acceptance Tests / Regression Tests (ensuring "Accepted Functionality never gets lost)
• IBM RTC for Stories, Tasks, Defects
• IBM RTC for SCM
• Hudson for CI
  
• Virtual Taskboards (IBM RTC)
  
• Each teams Velocity tracked and displayed
• Product Burnup displayed as Lean Cumulative Flow Diagrams
• Sprint Burndowns tracked and displayed
• Teams (Re)Plan and (Re)Estimate every Iteration
• System Testing within an Iteration
• Hudson and RTC Radiators (builds and graphs displayed on Screens plus audible feedback from HudsonTracker)
• Collaborative workspaces (whiteboards, pens, post-its, breakout areas)
• Regular High Bandwidth COmmunications (Eyecatcher VC Units, MSCommunicator VoIP, desktop sharing)
• No changes during an Iteration

Hudson and RTC - Cowley 1.0.1 Released

I've had some time recently and managed to get back to looking at my Hudson RTC plugin. I found a lot of things making the 1.0.0 version really unstable and have made some updates and come up with 1.0.1.

To get it and start getting the Hudson build love in your RTC projects visit the project site.

Please let me know too how it works for you - the site has an issue tracker so please log all bugs and RFE's there.

There are some extra features I'm working on for 2.0.0 which hopefully will be along soon including change set parsing (let Hudson know just who's changes sparked a build), personal builds, and automated releases. Watch this space...