CSSE3002 Lecture Notes - Lecture 8: Dynamic Systems Development Method, User Story, Emergence
28 Jun 2018
School
Department
Course
Professor
Student presentations
Scrum
Scrum seems to be a process but is actually a framework. A framework that takes a
multitude method processes and techniques, a team combines those to produce a
product or accomplish a goal
Scrum cam be used anywhere but it is mainly used in software engineering
development
Scrum framework- to understand these components, needs to understand the scrum
team and its members, each member has diff responsibilities at different stages
within this framework
Product owner- usually one person, to maximize the value of the product being
delivered by the development team. Creates and consistently manages the product
backlog. Act as a leader, defines goal for the whole team
Development team - they complete the tasks required. They define what ‘done’
means throughout this process
Scrum master – to be a mediator inside and outside of the scrum team. Ensure the
scrum process is being used effectively by all team members
Sprint planning – sprints works by segmenting work into discrete timeframes, a
sprint is no longer than one month
Daily scrum and daily work - do the sprit and complete the work, complete the
backlog. Mediated through daily scrum, meeting 15 minutes every day, repeated till
everything in the backlog is finished
Sprint review – what has happened during the sprint? Anything done anything not
completed? If not completed, either put it back to the product backlog or discard it.
How they are the work done? What the team did, how they did them and the
relationship between them.
An agile and effective development process
XSCALE/Agile TNG
XSCALE and Agile TNG are both the same thing
A new version of next generation of agile
XSCALE: a method in which you can evolve agile for a new generation
Agile: project delivery that does not assume the initial criteria specified are going to
be similar throughout, changes are welcomed in the later stages of development to
meet the customer needs
What agile lacks – targets small medium sized teams only
find more resources at oneclass.com
find more resources at oneclass.com
XSCALE: adds four specific pattern of languages to allow them to be more open
discussion for the team.
Most projects, design thinking style is used
Continuous throughput: team has to continue working on the project on a pace
Autonomous Teams: each member working on a specific part of the project instead
of having a hierarchical structure
Crystal Process
Developed in the 90s, one of the earlier agile methods
Traits: ultra light, human powered, designed to be convenient for the people working
Start very small, as minimalistic as possible, then add features through crystal to
cover the scope
More about communication, easy access to expert users as fundamental process
All co-located, everyone working on it work together nearby, could voice opinions
immediately/ ask questions, but impossible for big project
Prioritises safety, usability
Project cycle:
Divided into many portions
Charter: decide where the business models are, go through requirements
Build a team (6 members)
Determine the methodology (team members should be familiar with the
methodology)
Define roles (sponsor, lead designer, expert user, etc could add more roles)
Delivery cycle
Completion ritual (provides comfort and closure to the workers)
Reflection workshop (recalibrate)
Flow in product development
Flow – implies flexibility
Product development is a cycle that you cant go back to a stage you just passed
Flow? About the movement between processes in development cycle – moving from
integration to maintenance etc
Why use this method? - old method has problems – they were hostile to changes
during implementation – it costs a lot to change requirements
find more resources at oneclass.com
find more resources at oneclass.com
Why is it avoided? - seems costly to change deliverable – everything is written in
contract, nothing should be changed
Behaviour-Driven Development
Agile software development process which involves example-based communication
between the stakeholders
Focuses on testing the behaviour of the system – an improvement of test-driven
development
Purpose: to increase the communication between the software project stakeholders,
to decrease communication gap
Use a common language – Ubiquitous Language
To ensure all of the stakeholders are on the same page and correctly understood by
everyone before the development starts
Three core principles
Enough is enough: every activity should be given a specific amount of time,
not to waste time on one activity
Deliver stakeholder value: every activity should deliver a value to the
stakeholder
Its all behaviour: priority is behaviour
Red-green-refactor cycle
Ubiquitous language: represents the scenarios or the examples – scenarios
determine how a feature behave differently in different situations
The aim of UL: decrease the cost of translation – every team members(tester, coder
etc) might represent features differently – to reduce this communication gap
Example of BDD: Given-And-When structure
Given Student is at the UQ home page
And Navigate to my.UQ dashboard
When Student enters credentials
Name | password etc
And Student logs into system
Then Student in on the my.UQ dashboard page
Advantages
Brings stakeholders at the same page
System behaviour explained in natural language
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
Scrum seems to be a process but is actually a framework. A framework that takes a multitude method processes and techniques, a team combines those to produce a product or accomplish a goal. Scrum cam be used anywhere but it is mainly used in software engineering development. Scrum framework- to understand these components, needs to understand the scrum team and its members, each member has diff responsibilities at different stages within this framework. Product owner- usually one person, to maximize the value of the product being delivered by the development team. Act as a leader, defines goal for the whole team. Development team - they complete the tasks required. They define what done" means throughout this process. Scrum master to be a mediator inside and outside of the scrum team. Ensure the scrum process is being used effectively by all team members. Sprint planning sprints works by segmenting work into discrete timeframes, a sprint is no longer than one month.
