This work is about how lately Agile and especially Scrum have become more and more popular. A lot of people in higher management see the agile way of working as the key to success. But is this actually true? Have we found the silver bullet? Can every individual work in an agile way? If yes, does this mean that the team that he is part of will also adopt and use the agile way of working and thinking successfully? All those questions triggered this research.
One of the first questions we ask ourselves for each of our project implementations is "Which development methodology should we use?". This is a topic that gets a lot of discussion as it’s the way of organizing the work for the project and not as often misinterpreted about a style of project management or a specific technical approach. The two basic and most popular methodologies are: 1.Waterfall: which is known as the "traditional" approach, and 2.Agile: a specific type of Rapid Application Development and newer than Waterfall, but not that new, which is often implemented using Scrum. Both are usable, mature methodologies.
I started by providing basic information about both methodologies (Waterfall and Agile). I try to make the differences between the two methodologies visible and by giving more emphasis to the second one i present the history behind the methodology, the advantages and disadvantages and i try to come to a conclusion on what is agile and what is not. Next, at section two i briefly present the basic Agile Methods and Practices. I continue with section 3, that i explain Scrum and all the ceremonies and roles related to this methodology.
Table of Contents
Section 1: Waterfall versus Agile
1.1 Waterfall Model design
1.2 Agile Methodologies
Section 2: Most commonly used Agile Methods & Practices
2.1 Introduction
2.2 Agile Methodologies
2.2.1 Adaptive software development (ASD)
2.2.2 Agile modelling
2.2.3 Crystal Clear methods:
2.2.4 Dynamic systems development method (DSDM):
2.2.5 Extreme programming (XP):
2.2.6 Feature-driven development (FDD):
2.2.7 Lean software development:
2.2.8 Kanban
2.2.9 Scrum
2.2.10 Scrumban
2.2.11 Rapid application development (RAD)
2.3 Agile practices
2.3.1 Acceptance test-driven development (ATDD)
2.3.2 Behaviour-driven development (BDD)
2.3.3 Business analyst designer method (BADM)
2.3.4 Cross-functional team
2.3.5 Continuous integration (CI):
2.3.6 Domain-driven design (DDD)
2.3.7 Pair programming
2.3.8 Planning poker
2.3.9 Refactoring
2.3.10 Test-driven development (TDD)
2.3.11 User story
2.3.12 Story-driven modelling
2.3.13 Retrospective
2.3.14 Velocity tracking
2.3.15 User Story Mapping
2.3.16 More Practices:
Section 3 – Scrum
3.1 Roles
3.1.1 Product Owner
3.1.2 Scrum Master
3.1.3 Scrum Team
3.1.4Stakeholders
3.2 Artifacts
3.2.1 Product Backlog
3.2.2 Sprint Backlog
3.2.3 Product increment
3.3 Workflow
3.3.1 The Scrum process
3.3.2 Sprint Planning
3.3.3 The Daily Scrum
3.3.4 Sprint Review
3.3.5 Sprint Retrospective
3.4 Work & Delivery Flow-Example
Objectives and Topics
The primary objective of this work is to evaluate the effectiveness of agile software development methodologies—specifically Scrum—in comparison to the traditional Waterfall model. The research addresses whether Agile serves as a universal solution for successful project management and explores how teams adapt these practices in real-world environments.
- Comparison between Waterfall and Agile software development models.
- Examination of various Agile methodologies, including Scrum, Kanban, and Extreme Programming.
- Detailed analysis of the Scrum framework, covering key roles, artifacts, and ceremonies.
- Practical application of Agile practices such as test-driven development, user stories, and refactoring.
- Overview of operational workflows for managing agile project delivery.
Excerpt from the Book
Agile is a silver bullet:
You can fail just as spectacularly on an Agile project as you can be using any other traditional method. The difference to that is that You’ll fail faster using Agile (due to the transparency and visibility it brings) but unfortunately, it's not a silver bullet or an excuse to stop thinking.
There's nothing inherently magical about Agile. It basically says Bring your development team and customer as close together as you can, give them what they need, and then get out of the way.
Summary of Chapters
Section 1: Waterfall versus Agile: This chapter introduces the linear-sequential Waterfall model and contrasts it with the iterative, time-boxed nature of Agile methodologies.
Section 2: Most commonly used Agile Methods & Practices: This chapter provides an overview of various Agile frameworks like Scrum, XP, and Kanban, alongside detailed definitions of common technical and process-oriented Agile practices.
Section 3 – Scrum: This chapter focuses specifically on the Scrum framework, detailing the responsibilities of product owners and scrum masters, the role of artifacts like the backlog, and the mechanics of the sprint workflow.
Keywords
Agile, Scrum, Waterfall Model, Software Development, Iterative, Sprint, Backlog, Kanban, Extreme Programming, User Stories, Test-Driven Development, Continuous Integration, Refactoring, Project Management, Software Engineering
Frequently Asked Questions
What is the fundamental focus of this work?
This work explores the shift from traditional, linear project management methods like the Waterfall model toward more flexible, iterative approaches, specifically highlighting the Scrum framework.
What are the central themes of this document?
The central themes include the history of the Agile Manifesto, the comparative analysis of development models, detailed definitions of popular Agile methodologies, and the practical implementation of Scrum roles and ceremonies.
What is the primary research goal?
The goal is to determine the validity of the "silver bullet" claim regarding Agile—specifically whether the Agile methodology guarantees success and how team dynamics influence the efficacy of this approach.
Which scientific methodologies are employed?
The author employs a comparative analysis of project management frameworks, literature-based reviews of industry standards, and a practical exploration of operational workflows within software development.
What topics are covered in the main body?
The main body covers the theoretical foundations of Waterfall and Agile, a breakdown of various Agile practices (such as ATDD, BDD, and Pair Programming), and a technical walkthrough of the Scrum framework and its specific delivery flows.
Which keywords characterize this document?
Key terms include Agile, Scrum, Waterfall, iterative delivery, backlog management, sprint, and software engineering best practices.
What are the specific properties of a Scrum Product Backlog?
The document defines the Product Backlog as an ordered, living document where all entries must provide customer value, be estimated, and avoid low-level tasks.
How is the "Scrum Master" role defined in this work?
The Scrum Master is described as a facilitator who is not a project leader and is not held accountable for outcomes; instead, they are responsible for protecting the team from distractions and removing impediments.
What does the "Work & Delivery Flow-Example" illustrate?
It illustrates a practical case-by-case branching strategy, detailing the steps from dragging an item into "WIP" (Work In Progress) to code review, functional review, testing, and final deployment.
- Citation du texte
- Ajit Singh (Auteur), 2019, Agile Methodology With Scrum, Munich, GRIN Verlag, https://www.grin.com/document/488863
