DSV SU + IbisSoft Requirements on No Requirements Analysis of agile software development from a Systems and Knowledge Transformation Perspective 1 Ilia Bider Recording on Youtube will be published shortly 06/06/2022 13TH INTERNATIONAL CONFERENCE ON PERSPECTIVES IN BUSINESS INFORMATICS RESEARCH Pre-proceedings http://bit.ly/1vBsgqI - Free access Springer proceedings http://link.springer.com/chapter/10.1007/978-3- 319-11370-8_11
21
Embed
Requirements on No Requirements - When using agile is justified?
Analysis of agile software development from a Systems and Knowledge Transformation Perspective. Presentation at BIR 2014 (13TH INTERNATIONAL CONFERENCE ON PERSPECTIVES IN BUSINESS INFORMATICS RESEARCH). While the Agile Software Development (ASD) has been successfully promoted in the last 15 years, there is no agreement on how to determine whether a particular project is agile or not. Some practitioners consider agility as strict usage of a specific methodology, e.g. SCRUM, others consider agility as adhering to Agile Manifesto. The lack of common view on ASD prevents creating common guidelines on when the usage of ASD is appropriate. This paper presents a model of ASD that helps to differentiate it from the traditional, phase-based development, and more strictly defines the area of its applicability. The model has been built based on the knowledge transformation perspective, as the author considers it to be the most differentiating perspective when comparing ASD to traditional software development. For building the model, the ideas from SECI model of Nonaka have been exploited. The results, in the form of requirements to be fulfilled for successful employment of ASD, are demonstrated through analysis of completed ASD projects.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1DSV SU + IbisSoft
Requirements on No RequirementsAnalysis of agile software development from a
Systems and Knowledge Transformation Perspective
Ilia BiderRecording on Youtube will be published shortly
04/09/2023
13TH INTERNATIONAL CONFERENCE ON PERSPECTIVES IN BUSINESS INFORMATICS RESEARCH
– Set up a list of pre-conditions for success of an agile software development project
• Limitations– We will consider only new software development,
leaving maintenance and farther development outside our consideration
04/09/2023 DSV SU + IbisSoft 3
Plan for reaching the goalBuild models of software development for both traditional – phase-based development (TSD), and agile development (ASD) that help to
– Highlight the essential differences between TSD & ASD– Highlight advantages and risks related to the TSD– Show how ASD can help in mitigating the risks related to TSD– Analyze the conditions required for success of ASD
04/09/2023 DSV SU + IbisSoft 4
Background to built upon• A systems perspective on software development• A knowledge transformation perspective on software
development• Experience of the author in software related projects
– Including requirements engineering, software development, introducing IT in organisations
– big and small, non-agile and agile, successful and unsuccessful
– In different capacities, such as a programmer, group leader, consultant, bug fixer, technical project manager
04/09/2023 DSV SU + IbisSoft 5
Background: Systems perspectiveThree interconnected systems involved in software development:
Software systemS-system
Context SystemC-system
SE projectP-system
S-, P- and C- system needs to be aligned inside and between each other
04/09/2023 DSV SU + IbisSoft 6
Background: Systems perspectiveWhy the project is created: systems coupling diagram
From Lawson, H.W., 2010. A journey through the systems
landscape. Systems Series, Volumes 1 and 5, College Publications.
04/09/2023 DSV SU + IbisSoft 7
Background: Knowledge transformationSECI model of knowledge transformation of Nonaka:
Nonaka, I., 1994. A dynamic theory of organizational knowledge creation. Organization science, 5(1), pp.14-37..
Two types of knowledge:– Explicit– Tacit
04/09/2023 DSV SU + IbisSoft 8
Background: Knowledge transformationAdditional type of knowledge – embedded knowledge
Justification– Every good regulator of a system must be a model of that system
(Conant and Ashby )– A good solution is a model of the problem it solves (Scholten)– A key is a model of the lock it opens (Scholten)– A good software system is a model of the requirements its
implements/satisfy (Me)Se also Armour, P.G., 2000. The Case for a New Business Model. Is software a product or a medium? Communications of the ACM August 2000/Vol. 43, No. 8, 43(8), pp.19-22
04/09/2023 DSV SU + IbisSoft 9
Knowledge transformation in TSDECEA - a model of Traditional Software Development