Agile Case Studies 8 3
Agile Case Studies 8 3
Group 1: 09/08/2023
Group 2: 10/08/2023
Group 3: 16/08/2023
Group 1: Kanban
Kanban – literally translated from Japanese means a signboard or billboard – started life as a
scheduling system in the motor industry and is now one of the fastest growth areas in the agile
market. It’s easy to grasp, simple to implement and costs pretty much nothing. A big advantage
to Kanban is that it can be used by individuals or teams to manage their workload or on full-
scale projects.Kanban – literally translated from Japanese means a signboard or billboard –
started life as a scheduling system in the motor industry and is now one of the fastest growth
areas in the agile market. It’s easy to grasp, simple to implement and costs pretty much nothing.
A big advantage to Kanban is that it can be used by individuals or teams to manage their
workload or on full-scale projects.
Work to be done
In about 8 to 10 pages (Time News Roman, font size 12, spacing 1.5) present the Kaban. Define
the key terms, explain the mindset essentials, present its application domains along side with
the best practices guidelines for each domain. How is it being addressed in your country?
1
Group 2: Scrum
Scrum now happily co-exists with a whole range of other agile frameworks and although they
frequently snap at its heels for the No.1 spot, it remains the most popular primarily because it is
just prescriptive enough to be helpful without drowning people and teams in burdensome rules,
process and dogma. Moreover, it’s one of the safest way to get started with for those new to
the agile discipline because it has clearly defined roles and responsibilities, ceremonies and
artefacts, yet allows enough flexibility in their implementation to let its customers feel
supported but not suffocated.
Work to be done
In about 8 to 10 pages (Time News Roman, font size 12, spacing 1.5) present the scrum . Define
the key terms, explain the mindset essentials, present its application domains along side with
the best practices guidelines for each domain. How is it being addressed in your country?
Iterative and incremental development is at the top of our list. When we defined an Agile
methods we considered IID the heart of any Agile method. People were using these approaches
successfully in the 70s and the 80s. Larman and Basili found early roots for (IID) iterative and
incremental development since 1950s in NASA and IBM Federal Systems Divisions (FSD) [21].
According to them, NASA’s 1961-63 Project Mercury was run with “short half-day iterations”. In
addition, the Extreme Programming practice of test-first development was applied as tests
were planned and written and then the code were written to pass the tests. Furthermore, they
use continuous integration as each mini-iteration required integration of all code and passing of
the tests. Iterative and incremental development is at the top of our list. When we defined an
Agile methods we considered IID the heart of any Agile method. People were using these
approaches successfully in the 70s and the 80s. Larman and Basili found early roots for (IID)
iterative and incremental development since 1950s in NASA and IBM Federal Systems Divisions
(FSD) [21]. According to them, NASA’s 1961-63 Project Mercury was run with “short half-day
iterations”. In addition, the Extreme Programming practice of test-first development was
2
applied as tests were planned and written and then the code were written to pass the tests.
Furthermore, they use continuous integration as each mini-iteration required integration of all
code and passing of the tests.
Work to be done
In about 8 to 10 pages (Time News Roman, font size 12, spacing 1.5) present the extreme
programming. Define the key terms, explain the mindset essentials, present its application
domains alongside with the best practices guidelines for each domain. How is it being
addressed in your country?