Using Wiki for Managing Knowledge in Agile Software Development

2016 ◽  
pp. 397-423
Author(s):  
Pankaj Kamthan
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Agile Software Development ◽  
Software System ◽  
Web Environment ◽  
The Past ◽  
Agile Methodologies ◽  
The Social ◽  
Industrial Software ◽  
Agile Software

The movement towards agility is one of the most significant changes in industrial software engineering over the past decade. In the practice of agile methodologies, there are different types of knowledge that is created, communicated, and consumed. For the benefit of the stakeholders involved, there is a pressing need to manage this knowledge, both during development and beyond deployment of a software system. This chapter proposes a framework comprising related conceptual models as means for understanding the use of Wiki for managing knowledge in agile software development. In doing so, Wiki is considered beyond that of a technology or a tool, as a facilitator of knowledge, and placed in a larger context of the Social Web environment. For the sake of practicality, a number of illustrative examples are given, and implications of deploying a Wiki are highlighted.

Teaching Agile Software Development Quality Assurance

2009 ◽  
pp. 2700-2713
Author(s):  
Orit Hazzan ◽  
Yael Dubinsky
Keyword(s):  
Quality Assurance ◽  
Software Engineering ◽  
Software Development ◽  
Software Quality ◽  
Agile Software Development ◽  
Specific Teaching ◽  
Quality Issues ◽  
Agile Software ◽  
Software Development Environments ◽  
The Way

This chapter presents a teaching framework for agile quality—that is, the way quality issues are perceived in agile software development environments. The teaching framework consists of nine principles, the actual implementation of which is varied and should be adjusted for different specific teaching environments. This chapter outlines the principles and addresses their contribution to learners’ understanding of agile quality. In addition, we highlight some of the differences between agile software development and plan-driven software development in general, and with respect to software quality in particular. This chapter provides a framework to be used by software engineering instructors who wish to base students learning on students’ experiences of the different aspects involved in software development environments.

Wiki for Agility

2017 ◽  
pp. 896-916
Author(s):  
Pankaj Kamthan
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Conceptual Model ◽  
Agile Software Development ◽  
Social Aspects ◽  
Social Web ◽  
Agile Methodologies ◽  
The Social ◽  
Industrial Software ◽  
Agile Software

The movement towards agility is one of the most significant human-centered and socially oriented changes in industrial software engineering. In the practice of agile methodologies, there are different types of content (data, information, or knowledge) that are created, communicated, and consumed. It is imperative for an organization to manage such content, both during development and beyond deployment. This chapter proposes a conceptual model for understanding and exploring the use of Wiki as a vehicle for managing content in agile software development. In doing so, the parity between agile software development and Wiki is shown, human and social aspects of each are emphasized, the Social Web-Context of Wiki is demonstrated, illustrative examples are given, and the implications of committing to a Wiki are considered.

scholarly journals Forming and Assessing Student Teams in Software Engineering Courses

2020 ◽  
pp. 298-306
Author(s):  
Henrik Hillestad Løvold ◽  
Yngve Lindsjørn ◽  
Viktoria Stray
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Agile Software Development ◽  
Team Work ◽  
Development Projects ◽  
Work Behaviors ◽  
High Performing ◽  
Student Teams ◽  
Agile Software ◽  
Better Than

Abstract In software development projects, working in teams is essential. Therefore, software engineering courses often require the students to be working in teams to learn about team work behaviors and practices. The instructors of software engineering courses are presented with several challenges when teaching courses that require teamwork. For example, how to form high-performing student teams, and how to assess their work. The aim of this study is to evaluate whether there are differences in performance whether the students form the teams themselves, or if the teams are formed by the instructor. We evaluated a course involving agile software development by 200 students working in 39 teams. A total of 76% of the students chose to form their own teams, the remaining 24% were placed in teams by the instructors. Our findings indicate that teams formed by the students perform slightly better than the teams formed by the instructors.

Teaching Agile Software Development Quality Assurance

2011 ◽  
pp. 171-184 ◽  
Author(s):  
O. Hazzan
Keyword(s):  
Quality Assurance ◽  
Software Engineering ◽  
Software Development ◽  
Software Quality ◽  
Agile Software Development ◽  
Specific Teaching ◽  
Quality Issues ◽  
Agile Software ◽  
Software Development Environments ◽  
The Way

This chapter presents a teaching framework for agile quality—that is, the way quality issues are perceived in agile software development environments. The teaching framework consists of nine principles, the actual implementation of which is varied and should be adjusted for different specific teaching environments. This chapter outlines the principles and addresses their contribution to learners’ understanding of agile quality. In addition, we highlight some of the differences between agile software development and plan-driven software development in general, and with respect to software quality in particular. This chapter provides a framework to be used by software engineering instructors who wish to base students learning on students’ experiences of the different aspects involved in software development environments.

Sign in / Sign up

Export Citation Format

Share Document