BISM1201 Lecture Notes - Lecture 7: User Story, Extreme Programming, Continuous Integration
30 Sep 2018
School
Department
Course
Professor
Document Summary
Progra(cid:373)(cid:373)i(cid:374)g & project develop(cid:373)e(cid:374)t: self-organizing teams, product progresses in a series of month-lo(cid:374)g (cid:862)sprints(cid:863, e(cid:395)ui(cid:396)e(cid:373)e(cid:374)ts a(cid:396)e (cid:272)aptu(cid:396)ed as ite(cid:373)s i(cid:374) a list of (cid:862)product backlog(cid:863, no specific engineering practices prescribed, o(cid:374)e of the (cid:862)agile p(cid:396)o(cid:272)esses(cid:863). Team selects items from the product backlog they can commit to completing. Sprint backlog is created: tasks are identified and each is estimated, collaboratively, not done alone by the scrum master, high-level design is considered work estimated. Create user stories: a user story describes functionality that will be valuable to either a user or purchaser of a system or software. User stories are written from the e(cid:374)d use(cid:396)(cid:859)s poi(cid:374)t of (cid:448)ie(cid:449). Fo(cid:396) e(cid:454)a(cid:373)ple: "as a returning customer, i want to find a meal that i have ordered before. " Prioritize the user stories: product owner prioritizes the user stories in the product backlog by working with your customers to understand what they value and by working with your team to understand risks and dependencies.
