DePaul University



XPSCRUMSimilaritiesCustomer Collaboration is emphasized because requirements cannot be collected at the beginning Respond to changes quickly rather than following a planWorking software more useful than presenting docs to clients Expect changes in customer requirementsFrequent communication with customersDaily meetings DifferencesProgramming in pairs or conducting extensive code reviewAvoid programming features until they are needed Flat mgt structureSimplicity Clarity in programming codeSteps:Planning used to create user stories or requirements which are converted into iterations that covers a small part of the sys functionalityDesigning is the process that starts an iteration. Several iterations leads to the final product. Coding is the most important step. Programmers work in pairs developing and debugging code.Testing is done via customer feedback of user acceptance testing A sprint is a list of tasks to be accomplished Sprints last 2-4 weeks and starts with a brief planning meeting and ends with a reviewFinal product is developed from several sprints or iterations. A scrum is a daily meeting of 15 min duration to explain what was worked on yesterday and what will be worked on today along with any problems that need attentionScrum master is like the team coach and does not provide day to day direction or assign tasksScrum project management is the scrum team itselfProduct Owner PO provides the vision and prioritize the backlog Scrum team is like a car, PO the driver making sure it travels in the right direction, Scrum Master the chief mechanic keeping the car well-tuned and performing at its best ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download