RANDOM WEEK 1

Question 1

Waterfall

Answer 1

• DSLC
• inflexible
• big projects
• risk averse
• structured

Question 1

prototype

Answer 1

breaks away from waterfall by involving customers earlier and use incomplete versions. the final product can be very different from first prototype model.

Question 2

incremental

Answer 2

• little more is added each time
• the parts that you have are already finished
• combines waterfall and iterative philosophy of prototyping

Question 3

iterative

Answer 3

• repeating small cycles
• each version is better/more complete of the final version
• you have all the game elements but dont have the complete functionality yet

Question 4

spiral

Answer 4

• combining elements of prototyping stage/waterfall
• for large expensive and complicated projects
• advantages of top down and bottom up concepts

Question 5

RAD

Answer 5

• minimal planning and fast prototyping
• developing instead of planning
• lack of preplanning allows software to be written faster/easier to change requirements

Question 6

RUP

Answer 6

• iterative software
• no concrete prescriptive process
• adaptable

Question 7

difference between RAD and RUP

Answer 7

RAD: small medium projects/ highly flexible/uses feedback

RUP: large/structured/planning

Question 8

agile

Answer 8

• self-organizing cross functional teams
• adaptive planning
• time-boxed iterative approach
  -rapid and flexible response
• evolutionary development and delivery

Question 9

lean (kanbon)

Answer 9

• focuses on starting small with minimum viable product (basic version to test it).
• developers use real time feedback/data
• avoids waste

Question 10

lean principles

Answer 10

1. eliminate waste
2. amplify learning
3. decide as late as possible
4. deliver as late as possible
5. empower the team
6. build integrity in
7. see the whole

Question 11

scrum

Answer 11

• incremental and iterative
• flexible holistic
• development team works as an atomic unit
• 1) product backlog (everything needs to be done)
  2) sprint backlog (the team selects tasks that will be completed)
  3) daily checkins
  4) finish sprint and deliver work
  5) repeat cycle

Question 12

extreme programming (XP)

Answer 12

• improve software quality to customer requiremnets
• frequent short development cycles

Question 13

test driven development (TDD)

Answer 13

• you create tests before writing the actual code
• belongs to extreme programming

Question 14

feature driven development (FDD)

Answer 14

• delivering real, useful features that the client values, rather than just completing technical tasks