path to agility
DESCRIPTION
Mathew Sigman, M.S.E., Telerik MVP, PMI-ACP, and ScrumMaster certified.TRANSCRIPT
Solutions v.Nextand Team Foundation ServerKaleidaCare Development Team
Why?
• Give Dev team ability to provide working software releases quickly
• Increase accuracy and stability of schedule
• Increase communication between Dev and rest of company• Less time spent creating and updating documentation
Team Roles• Kelly – Product Owner• Matt – Scrum Master• Woo – Team Member• Jeremy – Team Member• BJ – Team Member• Mary Ellen – Team Member• Lisa – Team Member
Overall Idea
Definition of Done
What does it mean for something to be “complete”?
1. Code written per company standards and integrated2. User story is accurately told3. QA has written automated tests and the tests pass
User Story
A requirement written from a users’ perspective
User Story
As a <user> I want to <do something>
so that <I get value>
Examples for the Client File
• As an auditor I want to see all records created for a particular client so I can see their care history.• As a caseworker I want to see all records but
be able to go straight to a particular record so I can make changes.
User Story
• Wireframes• Acceptance tests• Other details including – Notes – Even entire documents– Priority
Epics
Epic
User story User story
User story
User stories can be further broken into tasks
Epic
User story
Task Task
Task Task
User story
Task Task
Example Tasks
• Create table MY_SEARCH_TABLE• Create search page
KaleidaCare.Web.UI/NewFeature/Search.aspx and add fields
• Create class and write Search() method
Product Backlog
TFS: Product Backlog
Sprint Planning Meeting
Sprints
• Fixed 2 week time period, no matter what• Starts with a sprint planning meeting
Sprint Planning Meeting
Sprint Begins
Daily standup meeting• What tasks/stories since yesterday?• What tasks/stories are you working on today?• Is anything holding up your work?– IT/Office issues– Code issues– Technical questions– Anything else blocking progress
Daily Standup
• Short questions pertinent to team can be asked in Daily Standup
• Longer questions should be held for after• Work with Kelly to ask questions
TFS: Task Board
Burndown Chart
Sprint Demo
• Company wide meeting • One Hour• Optional, but team members
should go
Retrospective
• Immediately follows demo• Team members only• Identify areas for improvement for next sprint
Meeting SummaryM T W Th F
Daily StandupSprint PlanningSprint Begins
Daily Standup Daily Standup Daily Standup Daily Standup
Daily Standup Daily Standup Daily Standup(code freeze @ midnight)
Daily Standup(stability changes only)
Daily StandupRetrospective
Daily StandupSprint PlanningSprint Begins
Daily Standup Daily Standup Daily Standup Daily Standup
Daily Standup Daily Standup Daily Standup(code freeze @ midnight)
Daily Standup(stability changes only)
Daily StandupSprint demoRetrospective
Key Concepts
• Requirements broken into smaller pieces called user stories
• Definition of Done – testing happens in tandem with development
• Anything not “Done” at end of sprint is worth 0 points and returned to product backlog
Build Schedule Changes
dev7.kaleidacare.com qa7.kaleidacare.com solutions7.kaleidacare.com
• Build every night• Runs coded UI tests• Developer check-ins
no longer pushed to dev7 website
• Instead, gated check-ins perform code analysis and other sanity checks
• Build weekly for maximum consistency
• Used as an integration and staging area, not for QA testing
• Build manually triggered
Questions?