Mjukvaruprojektmetoder

Individuals and interaction over process and tools

individuals and interaction over process and tools

working software over comprehensive documents

customer collaboration over contract negotiation

respond to change over following plan

scrum expert & advisor Scrum master, Team member, Product owner

coach Scrum master, Team member, Product owner

impediment bulldozer Scrum master, Team member, Product owner

Facilitator Scrum master, Team member, Product owner

Responsible for delivering user stories Team member, Scrum master, Product owner

Does all of the developer work Team member, Scrum master, Product owner

Self-organizes to deliver user stories Team member, Scrum master, Product owner

owns the estimation process Team member, Scrum master, Product owner

owns "how to do the work" decisions Team member, Scrum master, Product owner

avoids "not my job" Team member, Scrum master, Product owner

Holds the vision for the project Product owner, Scrum master, Team member

Represents the business Product owner, Team member, Scrum master

Represents the customers Product owner, Team member, Scrum master

owns the product backlog Product owner, Team member, Scrum master

prioritizes stories Product owner, Team member, Scrum master

creates acceptance tests Product owner, Team member, Scrum master

is available to anser teams questions Product owner, Team member, Scrum master

identify and plan improved ways of working retrospective, sprint demo, sprint planning, stand up, backlog grooming session

show stakeholders and the working system sprint demo, retrospective, sprint planning, stand up, backlog grooming session

product owner decides priorities sprint planning, retrospective, sprint demo, stand up, backlog grooming session

also known as daily scrum stand up, sprint planning, retrospective, sprint demo, backlog grooming session

team reviews upcoming backlog items backlog grooming session, sprint planning, retrospective, sprint demo, stand up

priority set by product owner product backlog, sprint backlog

define functionality to be delivered within the next increment product backlog, sprint backlog

reviewed during a backlog grooming session sprint backlog, product backlog

every user story scoped in detail and estimates determined sprint backlog, product backlog

low priority stories not estimated or only given tentative estimates product backlog, sprint backlog

frequent feedback agile, not so agile

informal agile, not so agile

feedback is rapid agile, not so agile

not many process steps agile, not so agile

many short interactions agile, not so agile

TDD (test-driven development) agile, not so agile

onsite customer agile, not so agile

releases are frequent agile, not so agile

documentation is minimal and relevant agile, not so agile

continous integration agile, not so agile

automated testing agile, not so agile

Big Bang not so agile, agile

a lot of process steps not so agile, agile

slow feedback not so agile, agile

ad hoc testing not so agile, agile

strict "waterfall" not so agile, agile

customer is remote or rarely aviaibale not so agile, agile

much process-oriented documentation not so agile, agile

testing phase not so agile, agile

considerable formality not so agile, agile

refactoring is primary technique that developers use to evolve the design of a system, incrementally repeating factors within a project, taking a factor from the user stories and divide it into smaller factors

refactoring is restructuring existing code without changing external behavior, incrementally repeating factors within a project, taking a factor from the user stories and divide it into smaller factors

Click

Type

Listen

Games

Print