scrum psm Flashcards
agile manifesto
individuals and inteaction over process and tools
working software over comprehensive documents
customer collaboration over contract negotiation
responding to change over follow plan
agile elements
agile = software development methodology based on interactivy and incremental development where requirements and solutions evovle through colaboration between self organising cross-functional team - iterative adaptable rapid cooperative quality diriven
what are agile benefites
iterative and adaptive
customers see quickly where we are
every sprint potentially shippable product
often routine feedback
reduction of wasted development
clear prioritisation helps make features mandatory
agile principles
- highest priority to satisfy customer through early and continuous delivery of valubale software
- the change is welcomed, even late in development
- deliver working software frequently
- business and dev need to work together through the poject
- build project around motivated individuals - give them tools, envionment and trust
- face to face communication
- agile process promotes sustainable development. should be able to maintain constant pace indefinitely
- simplicity - remove unnecessary early on
- reflection about team efecivenes on regular bases
what is scrum
framework within which people can address complex adaptive problems while productively and creatively delivering products of the highest value.
-lightweight
-simple to understand
-difficult to master
scrum employs interative, incremental approach to optimise predictability and control risks
basic principles of scrum
- define success
- define failure
- optimise the process for success
benefits from scrum process
- customers find dev team more responsive to their needs
- high value features are delivered faster with short cycles
empirical process of scrum
- -inspection - frequent enough inspection allows detection of unnacceptable variance
- tranparency-aspect of the process that affects the outcome is visible
- adaptation - if inspectoin reveals elements outside of acceptable limit, adapt as quck as possible to minimise further deviation
scum roles
product owner
- owns product backlog
- defines backlog itesm
- responsible for profitability
- prioritise backlog items
- provides vision and boundaries
- singte authority for product
- accepts work as completed
- negotiates priorities with dev team
- available for clrification
- gets stakeholders to define roadmap and help prioritise the backlog
- manages relationship with stakeholders
scrum master
- help team understand and use seft-management and cross functionality
- ensure that the process isfollowed and understood
- remove impediments, allow the team to be fully functional
- stops dev from being interrupted by external factors
- no authority
- works with product owner to maximise return on investment
- improve enjineering practices so that each increment of functionalit is potentialy shippable
- feedbak
- servant leader - manages team by leading and serving the needs of his team and customers
- assist with product backlog refinement, facilitate taem meetings, manage interruptions
- ensure definition of done is agreed
dev team
- cross functional 3-9 people (dev, qa, designer, ba ) whoever is needed to address requirement and turn it into usable product
- empowered
- self managing
- dedicated
qa as part of cross functional team
- interface with dev and po - to make sure acceptance tests track desired functionality
- write acceptance test code while code is written
- test the code against the acceptance test
- check tst cases every day
- develop ongoing test automation to integrate acceptance and feature tests into the continuous testing environment.
- use testrail for tracking updating test cases
product backlog
an ordered list of everything that might be needed in the product single source of requirements owned by PO refined by scrum team developed by dev team
less then 180 itesm! top 20-40 will go in upcoming sprints use velocity after 1-2 sprints. release burndown from product backlog refine 10% of dev time split into releases
product backlog detail
detailed appropriately: -high priority described in more details
estimated - rough estimated by story point (complexity) or size or days
emergant - evolves through project. changes with user feedback
prioritised - value, knowledge, uncertainty, risk, releasablity, dependancy
sprint backlog
- list of tasks committed to complete in the current sprint or iteration
- items taking from backlog based on priorities set by Product Owner
- team decideds on the items and time required to complete them
- stories broken down to tasks -1 day work
- anyone can pick it up
how to create good sprint backlog
sprint planning: involve everyone on the team discuss how every items should be imiplemented have definition of done identify all kinds of tasks don't estimate or assign tasks review sprint commitment 1-2 hours per 2 week sprint evolve sprint backlog during sprint
what is product increment
the sum of all the items in the product backlog that are completed during a sprint and the value of the increments of all previous sprints.
must meet scrum’s team definition of done.
