2. Team Organisation

Question 1

Common Team Models

Answer 1

1. Chief programmer team model
2. Multi-user dungeon model
3. Role-based mode

Question 2

Agile team benefits

Answer 2

1. less social loafing
2. constructive interactions
3. minimal coordinating efforts
4. everyone in the foreground
5. visible and meaningful contribution
6. willing to work beyond job roles

Question 3

Agile Manifesto

Answer 3

1. individuals and interaction over processes and tools
2. working software over comprehensive documentation
3. customers collaboration over contract negotiation
4. responding to change over following plan

Question 4

Agile Practices

Answer 4

1. small teams (3-12)
2. frequent:
   - structured meetings
   - small deliveries
   - customer engagement
3. maintain design and code quality
4. automation whenever possible
5. frequent change of objectives and priorities
6. frequent review of software process and make adjustments

Question 5

Agile Risks

Answer 5

1. lack of customer engagements
2. stakeholder conflict
3. complex contract
4. poor code quality
5. poor team coordination
6. loss of organizational memory

Question 6

Scrum process

Answer 6

PO : product backlog
scrum master: sprint backlog
review team: working increment

Question 7

Scrum roles

Answer 7

1. scrum master
2. product owner
3. team manager
4. quality assurance manager
5. toolsmith
6. chief architect
7. UX designer
8. developer

Question 8

Scrum roles considerations

Answer 8

1. attributes
2. skills
3. personality
4. circumstances
5. professional development aim

Question 9

Scrum communications

Answer 9

what
when/how often
by when
to whom
by what

Question 10

Scrum sprint planning

Answer 10

1. decide on the main goal

2. select task from the backlog

Question 11

Project launch meeting

Answer 11

1. determine major features to deliver
2. understand long term objectives and identify the minimum viable product
3. decide on goals
4. develop user stories
5. convert stories to tasks