path to agility
DESCRIPTION
Mathew Sigman, M.S.E., Telerik MVP, PMI-ACP, and ScrumMaster certified.TRANSCRIPT
![Page 1: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/1.jpg)
Solutions v.Nextand Team Foundation ServerKaleidaCare Development Team
![Page 2: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/2.jpg)
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
![Page 3: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/3.jpg)
Team Roles• Kelly – Product Owner• Matt – Scrum Master• Woo – Team Member• Jeremy – Team Member• BJ – Team Member• Mary Ellen – Team Member• Lisa – Team Member
![Page 4: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/4.jpg)
Overall Idea
![Page 5: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/5.jpg)
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
![Page 6: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/6.jpg)
User Story
A requirement written from a users’ perspective
![Page 7: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/7.jpg)
User Story
As a <user> I want to <do something>
so that <I get value>
![Page 8: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/8.jpg)
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.
![Page 9: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/9.jpg)
User Story
• Wireframes• Acceptance tests• Other details including – Notes – Even entire documents– Priority
![Page 10: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/10.jpg)
Epics
Epic
User story User story
User story
![Page 11: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/11.jpg)
User stories can be further broken into tasks
Epic
User story
Task Task
Task Task
User story
Task Task
![Page 12: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/12.jpg)
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
![Page 13: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/13.jpg)
Product Backlog
![Page 14: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/14.jpg)
TFS: Product Backlog
![Page 15: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/15.jpg)
Sprint Planning Meeting
![Page 16: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/16.jpg)
Sprints
• Fixed 2 week time period, no matter what• Starts with a sprint planning meeting
![Page 17: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/17.jpg)
Sprint Planning Meeting
![Page 18: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/18.jpg)
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
![Page 19: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/19.jpg)
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
![Page 20: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/20.jpg)
TFS: Task Board
![Page 21: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/21.jpg)
Burndown Chart
![Page 22: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/22.jpg)
Sprint Demo
• Company wide meeting • One Hour• Optional, but team members
should go
![Page 23: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/23.jpg)
Retrospective
• Immediately follows demo• Team members only• Identify areas for improvement for next sprint
![Page 24: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/24.jpg)
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
![Page 25: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/25.jpg)
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
![Page 26: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/26.jpg)
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
![Page 27: Path to agility](https://reader036.vdocuments.us/reader036/viewer/2022062312/5551a14db4c905013a8b5051/html5/thumbnails/27.jpg)
Questions?