3. scrum an iterative, incremental approach to optimize predictability and control risk.
4. must read and these
5. must readmust studied
6. requirmentswaterfall design development testing user acceptance release sprint 1scrum sprint 2 sprint 3 sprint 4 sprint 5 release
7. scrum supportin visualstudio
8. This template allows you to organize and track theprogress and health of a small- to medium-sizedScrum project.
9. team 1 product owner 1 scrummaster 5± 2 the team
10. the team the Team, which does the work. The Team consists of developers with all the skills to turn the Product Owner’s requirements into a potentially releasable piece of the product by the end of the Sprint.
11. product owner the Product Owner, who is responsible for maximizing the value of the work that the Scrum Team does.
12. scrum master the ScrumMaster, who is responsible for ensuring the process is understood and followed.
13. pig & chicken “A chicken and a pig are together when the chicken says, "Lets start a restaurant!" The pig thinks it over and says, "What would we call this restaurant?" The chicken says, "Ham n Eggs!" The pig says, "No thanks, Id be committed, but youd only be involved!"
14. # Planning the project
15. # Release planning meeting Estimating and prioritizing the Product Backlog # Product Backlog Evolving User Needs Owned by Product Owner Prio by Business Value
16. product backlog The Product Backlog represents everything necessary to develop and launch a successful product. It is a list of all features, functions, technologies, enhancements, and bug fixes that constitute the changes that will be made to the product for future releases.
17. # Product Backlog in visual studio
18. # Product Backlog
19. # Product Backlog
20. work item type product backlog item bug # Product Backlog
21. product backlog item
23. tip: product backlog items are usually stated asuser stories. use cases are appropriate as well,but they are better for use in developing life-or mission critical software.www.scrumalliance.org
24. bugs on the backlog scenario: bugs are related to functionality being coded during the sprint solution: bugs are solved during in the sprint - speak or create task - scenario: bugs are not related to functionality being coded during the sprint solution: bugs on the backlog. solution: bugs on a separate bug backlog.
25. Iteration path # Product Backlog
26. Iteration path
27. Iteration path
28. done The increment must be a complete slice of the product. It must be “done.” Done defines what the Team means when it commits to “doing” a Product Backlog item in a Sprint.
29. grooming the backlog
30. release burndown graphThe Release Burndown graph records the sum ofremaining Product Backlog estimated effort acrosstime.
31. velocity graphvelocity is how much product backlog effort a teamcan handle in one sprint
32. Looking ahead to the next version of VS Application Lifecycle Management
33. # Planning the sprint
34. # Sprint planning meeting Add PBI to sprint Decomposition Commitment # Sprint Backlog Tasks Related to PBI’s Hours remaining
35. sprint backlog The Sprint Backlog consists of the tasks the Team performs to turn Product Backlog items into a “done” increment.
36. # Sprint Backlog in visual studio
37. task It is all of the work that the Team identifies as necessary to meet the Sprint goal.
41. sprint burndown graphSprint Backlog Burndown is a graph of the amountof Sprint Backlog work remaining in a Sprint acrosstime in the Sprint.
42. team capacity planning (from MSF)
43. sprint burndown graph in Excel from MSF
44. sprint planning in Excel from MSF
45. Looking ahead to the next version of VS Application Lifecycle Management
46. # Daily scrum Track # Running the sprint
47. daily scrum The Daily Scrum is at the same time and same place throughout the Sprints. During the meeting, each Team member explains: 1. What he or she has accomplished since the last meeting; 2. What he or she is going to do before the next meeting; and 3. What obstacles are in his or her way.
49. Looking ahead to the next version of VS Application Lifecycle Management
50. Looking ahead to the next version of VS Application Lifecycle Management
51. practices Test early and often Build and deploy continuously Acceptance Test Driven Development Emergent Architectures Refactor Test Driven Development Agile Database Development Pair Programming
52. # Ship the sprint
53. # Sprint Review Demo the value # Sprint Retrospective Agile Practices – Improvement # Product Tasks Related to PBI’s Hours remaining
54. sprint review During the Sprint Review, the Scrum Team and stakeholders collaborate about what was just done. Based on that and changes to the Product Backlog during the Sprint, they collaborate about what are the next things that could be done.
55. sprint retrospective This meeting, the ScrumMaster encourages the Scrum Team to revise, within the Scrum process framework and practices, its development process to make it more effective and enjoyable for the next Sprint.
56. sprints # Sprint Retrospective
58. practicesTest early and oftenTest Driven DevelopmentAcceptance Test Driven DevelopmentBuild and deploy continuouslyEmergent ArchitecturesRefactorAgile Database DevelopmentPair Programming… and more
59. Test early and often Test Tasks, get test early involved
60. Test Driven Development Write unit test before code
61. Acceptance Test Driven Development Write acceptance tests before code
62. Build and deploy continuously Deliver continuous work software
63. Emergent Architectures Design vertical slices of functionality No Big Design up Front
64. Refactor RED GREEN REFACTOR
65. Agile Database Development Database unit tests Database refactoring
66. Pair Programming The person typing is called the driver. The person reviewing the code is called the observer