Agile Software Development: Principles, Methods, and Practical Applications - Prof. Michae, Lecture notes of Computer Science

Download Agile Software Development: Principles, Methods, and Practical Applications - Prof. Michae and more Lecture notes Computer Science in PDF only on Docsity!

Software Project

Management

Agile Methods in Practice

In the Beginning: Waterfall Method

1. Requirements
2. Design
3. Implementation
4. Verification
5. Maintenance

Does this look familiar?

In the Beginning: Waterfall Method

Best suited for:

● Projects with well-defined, fixed requirements ● Less complex objectives with predictable outcomes ● Industries requiring high reliability, like aerospace or defense

In 1985, the United States Department of Defense adopted the waterfall model in its DOD-STD-2167 standard for software development contractors.

Rethinking Project Management: Agile Methodology

● Problems associated with the Waterfall approach need to be addressed.

● Agile is a software development methodology (philosophy) that emphasizes iterative progress, collaboration, and flexibility.

● Has enjoyed widespread adoption in software development.

Other Common Challenges Agile Addresses

5. Poor Communication and Collaboration

6. Scope Creep

7. Resource Allocation

8. Timeline Constraints

9. Quality Control

10. Team Collaboration

11. Lack of Stakeholder Engagement

12. Inflexibility

Addresses Common Project Challenges

1. Resistance to Change
2. Insufficient Planning
3. Changing Requirements
4. Lack of Management Support (N/A)

We anticipated these. My expectations went something like this:

“Your plan will be wrong and that’s OK. Change it when needed.”

Agile Manifesto - Four core values

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

Agile Manifesto - 12 Guiding Principles

1. Customer satisfaction through early and continuous delivery of valuable software or products
2. Welcome changing requirements, even late in development
3. Deliver working software frequently
4. Business people and developers must work together
5. Build projects around motivated individuals.
6. The most efficient and effective method of conveying information is face-to-face conversation
7. Working software is the primary measure of progress
8. Agile processes promote sustainable development.
9. Continuous attention to technical excellence and good design enhances agility
10. Simplicity – the art of maximizing the amount of work not done – is essential
11. The best architectures, requirements, and designs emerge from self-organizing teams
12. the team reflects on how to become more effective, then tunes and adjusts its behavior

Some Popular Agile Methods

1. Scrum
2. Kanban
3. Extreme Programming (XP)
4. Lean Development
5. Crystal
6. Dynamic Systems Development Method (DSDM)
7. Feature-Driven Development (FDD)

*plus scaled versions of some of these

3 Popular Agile Methods

1. Scrum
2. Kanban
3. Extreme Programming (XP)

Scrum

● Key concepts: ○ Sprints ○ Product Backlog ○ Sprint Backlog ● Roles: ○ Product Owner ○ Scrum Master ○ Development Team ● Scrum Workflow ○ Sprint Planning ○ Daily Scrum ○ Sprint Review ○ Sprint Retrospective ● Suitable projects: ○ Complex projects with changing requirements, team size of 5-9 members

Kanban

● Key concepts ○ Visualizing workflow ○ Work in Progress (WIP) limits ● Kanban board ● Suitable projects ○ Ongoing work with varying priorities ○ Maintenance projects

Kanban Board

Uses a visual representation of the state of each “work item” represented on a “Kanban card”. The location of the card on the board and, perhaps, its color conveys information about the item and its status.

The card will contain information about the work item:

● Description ● Assignee ● Estimated time for completion

Example status columns: Requested -> in progress - > in review -> done

Extreme Programming (XP)

● Key practices ○ Pair programming ○ Test-Driven Development (TDD) ● Suitable projects ○ Small to medium-sized teams ○ Projects with changing requirements