18.02
Work - Avengers
Definition of Done
Brainstorm
Levels of Done:
Task
Story / Feature
Sprint Goals
Release
Ideas
Project
As a Product Owner
I want to know done stories are ready to release
So that I can plan release of features
As a Development team
I want to know that we've thought of everything
So that we can call a feature done
As a customer
I want to know when things are done
So that I can have them
User Experience
Guidelines must be followed
Code Produce
all 'to do' items in code completed
Code commented, checked in, merged
Peer reviewed
or peer programmed
Doesn't break the build
Meets code standards
Unit tests written and passing
Deployed to system test environment
and passed system tests suite
Integrations tested
Passed UAT
and signed off as meeting requirements
Any build/deployment/config changes
implemented/documented/communicated
Technical documentation updated
Component docs, Author docs, Models, Code docs
Acceptance criteria met
Automated regression tests pass
Non-Functional requirements assessed
Meets compliance conditions
Functionality documented
Product Owner accepted user story
NAB Environments
DEV
SIT
UAT
Blue
Prod
Principles:
Guideline, not a rulebook
'Done' takes practise
Evolving definition of done
Local
Testing done across multiple browsers
Responsive Testing Done
bigColumns
Backlog
Kickoff
In Dev
Walkthrough
Ready for Test
In Test
Done
shortColumns
Backlog
Dev
Walkthrough
Test
Done
Swimlanes
Dev
QA
PO
BA
a11y
Project Phases
Development
Integration
UAT / BVT
Pentesting
Release
Big ole questions
What happens at kickoff
Why?
What do we do for Code Quality?
When does a11y do what?
Detail how each meeting should run
- Who attends
- Why are they there
When is BVT?
When is code pushed/merged to which environment?
- Maybe as a swim lane
Test cases written
Defect Documentation for Release
Integration tests written
Mocks/Stubs created
Functional Testing written