Class 4 - Intro to Agile, Working with Stakeholders

Question 1

True or False: It is okay if a system is not deployable at the end of a sprint as bugs can always be fixed in the next sprint

Answer 1

False. The system should be technically deployable at the end of every sprint (code is clean, all tests pass). Deployment should be a business decision

Question 2

Stable Productivity

Answer 2

A feature similar to one that took 2 weeks at the start of project will take 2 weeks a year later

Question 3

What things are expected to improve as more time is invested into a project?

Answer 3

• Design and architecture of a software system
• Code structure
• Efficiency and throughput

Question 4

Fearless Competence

Answer 4

If you see something wrong or dirty, you will fix and clean it

Question 5

Why is test automation desirable?

Answer 5

Asking humans to do what machines can do is expensive, inefficient, and immoral. Every test that can feasibly be automated must be automated.

Question 6

What tools can be used to automate UI acceptance tests?

Answer 6

• Selenium
• Espresso
• Robotium
• others…

Question 7

What is the most honest estimate?

Answer 7

I don’t know

Question 8

How can you get a more honest estimate for user stories?

Answer 8

• Use relative estimates (story points)
• For time estimations, give a range of possibilities

Question 9

Perverse Incentives

Answer 9

Incentives that result in unintended negative consequences due to actions people take to receive the incentive. Specifically, do not judge sprint progress based on:
- Story points complete
- # of stories
- # of bugs fixed

Question 10

Cobra Effect

Answer 10

An attempted solution worsens the original problem (e.g. if a cash reward is given for killing snakes, people will breed snakes just to kill them and make money)

Question 11

True or False: When you don’t believe something is possible (based on the scope, budget, and time allotted for the project), you should say no

Answer 11

True. Even if you are turning down something the client really wants, it is important to say “no” if something is not feasible.

Question 12

What can you do to ensure you are continuously learning software engineering?

Answer 12

• Learn at least 1 new language every year
• Read a technical book and a nontechnical book each month
• Take classes
• Participate in local user groups and meetups
• Experiment with different environments
• Stay current

Question 13

Customer Bill of Rights

Answer 13

• Overall Plan
• Maximize Value
• See Progress
• Change your Mind
• Informed of schedule and estimate changes
• Cancellation

Question 14

Overall Plan (Customer Bill of Rights)

Answer 14

You have the right to an overall plan and to know what can be accomplished when and at what cost

Question 15

Maximize Value (Customer Bill of Rights)

Answer 15

You have the right to get the most possible value out of every iteration

Question 16

See Progress (Customer Bill of Rights)

Answer 16

You have the right to see progress in a running system, proven to work by passing repeatable tests that you specify. Customers need to know what progress is made from their point of view.

Question 17

Change your Mind (Customer Bill of Rights)

Answer 17

You have the right to change your mind, to substitute functionality, and to change priorities without paying exorbitant costs

Question 18

Informed of schedule and estimate changes (Customer Bill of Rights)

Answer 18

You have the right to be informed of schedule and estimate changes, in time to choose how to reduce the scope to meet a required date

Question 19

Cancellation (Customer Bill of Rights)

Answer 19

You may cancel at any time and be left with a useful working system reflecting investment to date

Question 20

Developer Bill of Rights

Answer 20

• Requirements
• Quality of Work
• Ask/Receive Help
• Make/Update Estimates
• Accept Responsibilities

Question 21

Requirements (Developer Bill of Rights)

Answer 21

You have the right to know what is needed with clear declarations of priority

Question 22

Quality of Work (Developer Bill of Rights)

Answer 22

You have the right to produce high-quality work at all times. Customer can’t ask developers to:
- Produce low-quality work
- Ignore ethical problems
- Harm their reputation

Question 23

Ask/Receive Help (Developer Bill of Rights)

Answer 23

You have the right to ask for and receive help from peers, managers, and clients

Question 24

Make/Update Estimates (Developer Bill of Rights)

Answer 24

You have the right to make and update your own estimates

Question 25

Accept Responsibilities (Developer Bill of Rights)

Answer 25

You have the right to accept your responsibilities instead of having them assigned to you. Developers are responsible for getting the training, help, and information they need to ensure their own success

Question 26

Inexpensive Adaptability

Answer 26

You should be able to make changes to your codebase quickly and easily without incurring a high cost