Please enable JavaScript.
Coggle requires JavaScript to display documents.
Simplicity in Agile Software Development - Coggle Diagram
Simplicity in Agile Software Development
Abstract
how teams members
interpret their experiences in ADS
Simplicity factors
lightweight process
knowledge acquisition,
personal communication
product with value
time-consuming
Introduction
Project management changes
emerging
challenges
and
opportunities
in software development
flexibility
Collaboration
distribution of responsibilities
initiative to support adaptation
Background
Simplicity in
Information and Communications
Technology
The art of knowing
Structure
Orthogonality
Transparency
Size
Communication
Automation
Context
Subjective/felt complexity
Simplicity in
ADS
get
feedback quickly
by delivering software at
short increments
empirical evidence
about simplicity at work and leads towards proposing a
first model of simplicity in agile software development
Method
Eisenhardt
case study
How is simplicity understood
by the agile team members?
Semi-structured interviews
demographic profile
simplicity in ADS
key dimensions of simplicity
Comparative method of
qualitative analysis
"Without a
research focus
, it is easy to become overwhelmed by volume of data."
Results
Characterising
Simplicity
in ADS
Lightweight process
Knowledge acquisition
Time-consuming
Product with value
Personal Communication
Relating
Practices
and Building
Propositions
Proposition 1:
lightweight process
enhances
personal communication
, reduce
time-consuming
tasks and leads to
simplicity in ADS
.
Proposition 2: the encouragement to
knowledge acquisition
promotes
simplicity in ADS.
Proposition 3: the adoption of a
personal communication
with customer and agile team positively impact the
product with value
and leads to
simplicity in ADS.
Proposition 4: the optimization of
time-consuming
positively promotes on development of
product with value
, and leads to
simplicity in ADS.
Building the Provisional
Theory
Externally-oriented simplicity goals
: lightweight process, knowledge acquisition, ,time consuming and personal communication.
Internally-oriented simplicity goals:
product with value.
Discussion
compared and contrasted construct definitions with literature could be conduct in the future to
ensure consistency with participants
participants sampled with
different roles to increase credibility
limitation that used
interviews only as data collection
method
Theoretical saturation
Replicate the protocol
in other organisations
Conclusion
Results shows that
simplicity is aligned with the grounded categories
of lightweight process, knowledge acquisition, time-consuming, personal communication, aiming for a product with value.
Future Works
Apply the protocol in other organisations and use the
member checking technique to check the consistency of interpretations
and to raise the theoretical level.