CSSE3002 Lecture Notes - Lecture 4: Planning Poker, Fungibility, Peer Pressure
28 Jun 2018
School
Department
Course
Professor
Lecture Week 4A notes
Continuing about User stories from last week’s lecture
Prioritisation and Estimation
1st project due end of march
-Requirements model about commonwealth games website using user stories.
-Template: use to describe user stories (the slides)
o1st page: overall system goals- information out of business model canvas
o2nd page: List of roles (system roles)
o3rd page(s):
(slides) individual slides represents user stories
As a (someone) I want (to do something) so that (I get benefits).
Notes: do not have to write down notes for every slide (only if there is
something meaningful)
-Story ID: Story 1, Story 2, Story 3... (track the stories)
-Story Title: Short descriptor
-Priority and points (today’s lecture)
oWhat’s the priority and what’s the estimated size of the story
-Complete the slides and submit it.
-If install solar power: how much money I make, how much power I save
-User stories: the details of the project to implement the user stories
-Story ID does not have to be in numerical sequence (can group them up)
Release and Sprint Plan Template
Release plan:
-Given all these stories, when will we deliver it
-What’s the plan to do it for the first iteration or sprint?
-Each release has a list of stories that is related to each other (one topic)
Sprint plan:
-What will be done in the first two weeks
-Estimation of how long each task take
-Delivery Schedule: (two sprints and deliver)
find more resources at oneclass.com
find more resources at oneclass.com
-Sprint 1: estimate the hours, how many tasks for each story
Marking criteria:
-50% based on story itself (well-written, quality, INVEST principle, represent complete
and impressive system), points for how well you’re doing in tutorial sessions
-20% release plan, 15% sprint plan
Research Presentation (week 7 & 8)
6 mins MAX, 2 mins for questions, one min to change speakers
-Don’t talk too fast/rush (bad presentation style)
Choose your topics
-Week 7 (pick an elicitation technique, explain & give example if possible)
-Week 8 (pick an SE process, some process has lots of info some does not)
Present based on the information you could find. (sources do not have to be peer reviewed)
2 groups (tutorial group, user stories project team) in Blackboard
Sign up for presentation: insert topic chosen & when you’re presenting
Create a page in Wiki: one paragraph summary of topic & list of references found
Presentation marking criteria:
-60% based on content
-20% how well-organised (information)
-20% quality of your presentation
Presentation: only a bit of a research, get information from other presentations and do more
research for report at the end of semester.
Prioritisation
-Determine what’s important to client. Normally build a system in stages, what should
happen early and later. Rank the importance of the stages
-Help the team understand the general business objective we’re trying to achieve. The
priorities will start with indicating the things the businesses interested in or just the
technical features to be delivered.
-With a large project which might take a long time.
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
Continuing about user stories from last week"s lecture. Requirements model about commonwealth games website using user stories. Template: use to describe user stories (the slides: 1st page: overall system goals- information out of business model canvas, 2nd page: list of roles (system roles, 3rd page(s): (slides) individual slides represents user stories. As a (someone) i want (to do something) so that (i get benefits). Notes: do not have to write down notes for every slide (only if there is something meaningful) Story id: story 1, story 2, story 3 (track the stories) Priority and points (today"s lecture: what"s the priority and what"s the estimated size of the story. If install solar power: how much money i make, how much power i save. User stories: the details of the project to implement the user stories. Story id does not have to be in numerical sequence (can group them up) Given all these stories, when will we deliver it.
