Scrum certification + Requirements

Question 2

Scrum Certification

Answer 2

• certified scrum master
• 2 day course plus online test
• commercialisation of agile methodologies or useful qualification

Question 3

ScrumButt test

aka nokiatest

Answer 3

• originates from Nokia (Bas Vodde)
• 9 questions to determine status of a scrum team rated 0-10
• iterations
• testing
• enabling specifications
• product owner
• product backlog
• estimates
• burndown
• disruption
• team
• average per team member of avg per question

Question 4

Kanban

Answer 4

• visual indication of progress of team
• show of cards to see how project is going
• translated as “visual card” or “signal card”
• visualise the workflow -> ie, whiteboard with stickies
• limit work in progress -> max number of tasks in a column specified by WIP limit
• measure & optimise flow -> burndown charts
• kanban boards -> move sticky notes between columns on whiteboards

Question 5

Requirements

Answer 5

• are condition/feature of what a program is gonna be doing
• tool has to be useful for them - have to decide what it will do
• a lot/too many features may not necessarily help
• a condition/capability needed by a user to solve a problem or achieve an objective
• a condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification or other formally imposed documents
• a documented representation of a condition or capability as in (1) or (2)

Question 6

Why are they important?

Requirements

Answer 6

need to decide to what to build

Question 7

functional requirements

Answer 7

an action that product must take to be useful

Question 8

nonfunctional requirements

Answer 8

• a property or quality the product must have
• could be about accessibility/interface
• features might make program unpleasant to use

Question 9

constraints

Answer 9

• global requirements - on the project or the product
• could be release date
• must be obeyed rather implemented

Question 10

FURPS

Answer 10

• functionality - what the application should do
• usability - what the program should look like
• reliability - a system should be reliable, accessible at any time, how reliable it should be
• performance - how efficient system should be
• supportability - how easy it is to support application

Question 11

The iron triangle

Answer 11

• each point is scope, resources and schedule
• scope -> features, functionality
• resources -> cost, budget
• schedule -> time

Question 12

R

Question 12

Requirements analysis

Answer 12

• the process of studying user needs to arrive at a definition of system, hardware or software requirements
• the process of studying and refining system, hardware or software requirements