Week 5 Agile

Question 1

What are the benefits of the waterfall model for the SLDC.

Answer 1

Requirements are clearly defined, easy to arrange tasks, process and results are well documented, easy to manage due to specific deliverables due to rigidity.

Question 2

What are the disadvantages of the waterfall model?

Answer 2

No working software produced until late in cycle when changes are most expensive, rigid and inflexible, difficult to accommodate changing requirements. Poor model for long and ongoing projects.

Question 3

What are the 3 models for software development?

Answer 3

Waterfall model and Iterative/incremental model and finally the spiral model.

Question 4

What is the iterative/incremental model

Answer 4

Break down the projects into smaller projects, then waterfall and repeat.

Question 5

What are the weaknesses of the iterative/incremental model?

Answer 5

Each iteration is still rigid, and if the breakdown of projects is not good requirements may change between the development of various modules.

Question 6

What are the cons of the spiral model.

Answer 6

Heavy on documentation from intermediate stages, a complex process which must be adhered to strictly, slow convergence on a finished product.

Question 7

What is the general aim of agile?

Answer 7

The aim is to reduce overhead during SD and to be adaptable to changing requirements.

Question 8

What is the manifesto for Agile software development?

Answer 8

1. Individuals and interactions over processes and tools.
2. Working software over comprehensive documentation.
3. Customer collaboration over contract negotiation.
4. Responding to change over following a plan.

Question 9

How many agile principles are there?

Answer 9

12

Question 10

What is agile principle 1?

Answer 10

The highest priority is to satisfy the customer through early and delivery of valuable software.

Question 11

What is agile principle 2?

Answer 11

Welcome changing requirements, even late in development. Agile processes must harness change for the customers competitive advantage.

Question 12

What is agile principle 3?

Answer 12

Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

Question 13

What is agile principle 4?

Answer 13

Business people and devs must work together daily throughout the project.

Question 14

What is agile principle 5?

Answer 14

Build projects around motivated individuals. Give them the environment and support they need, trust them to get the job done.

Question 15

What is Agile principle 6?

Answer 15

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

Question 16

What is agile principle 7?

Answer 16

Working software is the primary measure of progress.

Question 17

What is agile principle 8?

Answer 17

Agile processes promote sustainable development. Sponsors, devs and users should be able to maintain a constant pace indefinitely.

Question 18

What is agile principle 9?

Answer 18

Continuous attention to technical excellence and good design enhances agility.

Question 19

What is agile principle 10?

Answer 19

Simplicity, the art of maximising the amount of work not done is essential.

Question 20

What is agile principle 11?

Answer 20

The best architectures, requirements and designs emerge from self-organising teams.

Question 21

What is agile principle 12?

Answer 21

At regular intervals, the team reflects on how to become more effective, adjusting accordingly.

Question 22

What are 2 different implementations of agile?

Answer 22

Scrum and extreme programming (xp)

Question 23

What are the roles within scrum?

Answer 23

Product owner, scrum master and scrum team.

Question 24

What does the scrum product owner do?

Answer 24

• Provide vision
• Manage product backlog
• Define priorities.
• Decide if product is shippable.

Question 25

What does the scrum master do?

Answer 25

- Coaches the team. - Deep understanding of the work. - Schedules resources and facilitates meetings. - Shields the team from product owner.

Question 26

What does the scrum team do.

Answer 26

- 5-7 members - complimenting set of skills. - team spirit. - self organise. - pull work

Question 27

What are the components of the scrum process?

Answer 27

1. Product backlog 2. Sprint backlog 3. Sprint(daily meetings & sprint burndown) 4. Release (sprint review meeting)

Question 28

What template do user stories take?

Answer 28

As a I want So that

Question 29

What is the difference between user stories and requirements?

Answer 29

User stories are much more explicit and concrete representation of requirements. (A requirement can have multiple user stories)

Question 30

How can you think of user stories.

Answer 30

As functional/nonfunctional features.

Question 31

What is the issue with feature interactions?

Answer 31

Interactions between features (user stories) can cause runaway complexity, bugs, cost and schedule overruns in addition to unfortunate user experiences.

Question 32

What is the product backlog?

Answer 32

The list of all items that need to be completed so that the end product is developed.

Question 33

How long are sprints usually?

Answer 33

2-4 weeks.

Question 34

What is the selection phase of the spring cycle?

Answer 34

Where the entire project team work with the customer to select features/functionality to be developed during the sprint.

Question 35

What are the benefits of scrum?

Answer 35

1. Product is broken down into managable chunks. 2. Unstable requirements don't affect progress. 3. Team has greater visibility on whats going on and as such communication is better. 4. Customers see on time delivery of increments and can provide realtime feedback. 5. Trust between customer and developers increases.

Question 36

What are the development practices of extreme programming?

Answer 36

Pair programming code review, user stories, refactoring and testing/continuous integration.

Question 37

What sized project is the best for scrum?

Answer 37

Small-medium size project.

Question 38

When is agile best used?

Answer 38

When you can divide teams into small tightly integrated units and when customers are involved with development.

Question 39

What are some problems with agile methodology?

Answer 39

- Difficulty keeping customers interested/involved in the process. - Team members may be unsuited to intense involvement required. - Prioritising change is difficult with multiple stakeholders. - Maintaining simplicity requires extra work. - Contracts may be problematic.

Question 40

What are some issues which arise in regards to agile methods and maintainability.

Answer 40

- Agile methods must support good maintainability after development. - Emphasis on low documentation. - Changes must be controlled otherwise the scope of the project will become out of control.

Question 41

How can agile be scaled to a big project?

Answer 41

A big project can be divided into many small projects like microservices, each has an agile development team behind it.

Question 42

Why is agile difficult to use for large system development?

Answer 42

- Lare systems are constrained by external rules/regulations limiting them. - Long procurement/dev time. Difficult to maintain coherent teams who know about the system. - Difficult to get stakeholders involved.

Question 43

What is scaling up agile?

Answer 43

Concerned with how agile methods are used to develop large software systems not makeable by a small team.

Question 44

What is scaling out agile?

Answer 44

How can agile methods be introduced across a large organisation with many years of software development experience.

Question 45

What is a key thing to maintain during scaling of agile methods?

Answer 45

Adherence to the agile principles.

Question 46

How is scaling up of agile implemented?

Answer 46

1. More upfront design/documentation. 2. Cross team communication must be improved. 3. Continuous integration must be constrained.

Question 47

What are key issues of scaling out agile?

Answer 47

1. Requires changing culture. 2. Beauracracy conflicts with agile methods. 3. Stakeholders unwilling to deal with risk of a new approach. 4. Lack of involved staff. 5 Cultural resistance.

Question 48

What are some key points of bertrands book.

Answer 48

- Test driven development is useful but should not be the core component of agile. - Sprints are good but should be flexible. - Scaling is difficult.