Midterm Study - Agile Development

Question 1

What is agile modelling?

Answer 1

Agile Modelling is a collection of practices based on several values and proven software engineering principles. It is an alternative to traditional project management, typically used in software development. It helps teams respond to unpredictability through incremental, iterative work cadences, known as sprints.

Question 2

What would an agile project visual representation look like?

Answer 2

Question 3

What are the 10 Principles of Agile Development?

Answer 3

1. Our heighest priority is to satisfy the customer through early and continuous deliver of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
3. Deliver working software frequently.
4. Build projects around motivated individuals.
5. The most efficient and effective method of conveying information to and within a development team is face to face communications.
6. Working software is the primary measure of progess
7. Agile processes promote sustainable development, the sponsors, developers, and users should be able to mantain a constant pace indefinitely.
8. Continuous attention to technical excellence and good design enhances agility.
9. The best architectures, requirements, and designs emerge from self-organizing teams
10. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly

Question 4

What is the main agile methodology used?

Answer 4

SCRUM

Question 5

What is SCRUM?

Answer 5

Scrum is a subset of agile, it is a lightweight process framework for agile development, and the most widely-used one. SCRUM , mainly consists of a scrum master, scrum team and product/project owner. You sort the list by priority and estimate the relative effort for each item. Split time into short fixed-length iterations/sprints (usually 2- 4 weeks), with potential shippable code demonstrated after each iterations. Split your project into Small, cross-functional, Self-organization team. Split the work into a list Of small, concrete deliverables. During each sprint the team creates an increment of potential shippable software. The set of features of features that go into sprint come from the product backlog. Which backlog items go into the sprint is determined during the sprint planning meeting. The team then determines how much of this they can commit to complete during the next sprint. During the sprint, no one is able to change the sprint backlog. The project/product is described as a list of features: the backlogs. The features are described in terms of user stories. The scrum team estimates the work associated with each story. Features in the backlog are ranked in order of importance. Results: a ranked and weighted list of product features, a roadmap. Daily scrum meeting to discuss: What did you do yesterday? What will you do today? Any obstacles? Scrum projects make progress in a series of “Sprints”. Typical duration is 2-4 weeks or a calendar month at most. A constant duration leads to a better rhythm. Product is designed, coded, and tested during the sprint