Abstract
Scrum—Agile programming—is getting more attention in Software Engineering practices. Many software projects began with small and were not certain about the requirements until projects have completed; this makes Scrum more appropriate than other development methodologies. This paper reintroduced Scrum from qualitative perspective by applying ethnography and in-depth interview to two different types of project teams to articulate what the success factors are for running Scrum framework. It clearly demonstrated how qualitative research could help in disclosing the essence of facts during the Scrum adaptation in depth. It also articulated how these successful factors mutually affect to one another from System Dynamics perspective and to give further recommendations to Scrum teams and those who tend to apply Scrum development methodology.
Highlights
Software development is a process of communication [1]
Office layout often determines the effectiveness of team communications, it plays a powerful role in shaping a diverse range of psychological and behavioral outcomes, including individual work motivation, job satisfaction, and patterns of interactions [9]
Requirements are considered to be a set of knowledge that facilitates business processes or help organization achieving business goals, and they are about: 1) Customer Perspective where the requirements regarding the quality of service desired are defined, the knowledge concerning their perception of the service delivered; 2) Business Perspective where the requirements regarding the structure of the business process are defined; 3) Employee Perspective where the requirements concerning the skills and experiences are defined and the knowledge used in the processing of activities based on the knowledge gathered during the previous processing steps; 4) Product Perspective where the requirements regarding the specification of the final product are defined [17]
Summary
Software development is a process of communication [1]. There are many approaches [2] helping the development to produce qualified software to stakeholders. Scrum is an agile framework for completing complex projects. Scrum originally was formalized for software development projects, but works well for any complex, innovative scope of work. Scrum Master leads a Sprint Planning with the team to disassemble the story into tasks, a Sprint Backlog. The cycle repeats until enough items in the product backlog have been completed, the budget is depleted, or a deadline arrives Which of these milestones marks the end of the work is entirely specific to the project. The success of Scrum framework requires mature capabilities such as technical and communication. Project teams are formed to achieve the strategic objectives of the organization, such as increasing market share, launching a generation product, improving quality, enhancing customer relationships and for other purposes. Scientific research consists of an investigation that: 1) seeks answers to a question; 2) systematically uses a predefined set of procedures to answer the question; 3) collects evidence; 4) produces findings that were not determined in advance; 4) produces findings that are applicable beyond the immediate boundaries of the study
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
