| 1. |
- Alégroth, Emil, 1984, et al.
(författare)
-
Teaching scrum – what we did, what we will do and what impedes us
- 2015
-
Ingår i: Lecture Notes in Business Information Processing. - 1865-1348 .- 1865-1356. - 9783319186115 ; 212, s. 361-362
-
Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
- This paper analyses the way we teach Scrum. We reflect on our intended learning outcomes, which challenges we find in teaching Scrum and which lessons we have learned during the last four years. We also give an outlook on the way we want to introduce and apply Scrum in our teaching and how we intend to improve the curriculum.
|
|
| 2. |
- Berger, Christian, 1980, et al.
(författare)
-
Expectations and Challenges from Scaling Agile in Mechatronics-Driven Companies - nA Comparative Case Study
- 2015
-
Ingår i: Agile Processes, in Software Engineering, and Extreme Programming, Xp 2015. - Berlin : Springer-Verlag Berlin. - 9783319186122 ; 212, s. 15-26, s. 15-26, s. 15-26
-
Bokkapitel (refereegranskat)abstract
- Agile software development is increasingly adopted by companies evolving and maintaining software products to support better planning and tracking the realization of user stories and features. While convincing success stories help to further spread the adoption of Agile, mechatronics-driven companies need guidance to implement Agile for non-software teams. In this comparative case study of three companies from the Nordic region, we systematically investigate expectations and challenges from scaling Agile in organizations dealing with mechatronics development by conducting on-site workshops and surveys. Our findings show that all companies have already successfully implemented Agile in their software teams. The expected main benefit of successfully scaling agile development is a faster time-to-market product development; however, the two main challenges are: (a) An inflexible test environment that inhibits fast feedback to changed or added features, and (b) the existing organizational structure including the company's mind-set that needs to be opened-up for agile principles.
|
|
| 3. |
- Bjarnason, Elizabeth, et al.
(författare)
-
An Industrial Case Study on Test Cases as Requirements
- 2015
-
Ingår i: Agile Processes in Software Engineering and Extreme Programming : 16th International Conference, XP 2015, Helsinki, Finland, May 25-29, 2015, Proceedings - 16th International Conference, XP 2015, Helsinki, Finland, May 25-29, 2015, Proceedings. - Cham : Springer International Publishing. - 1865-1356 .- 1865-1348. - 9783319186115 - 9783319186122 ; 212
-
Konferensbidrag (refereegranskat)abstract
- It is a conundrum that agile projects can succeed ‘without requirements’ when weak requirements engineering is a known cause for project failures. While Agile development projects often manage well without extensive requirements documentation, test cases are commonly used as requirements. We have investigated this agile practice at three companies in order to understand how test cases can fill the role of requirements. We performed a case study based on twelve interviews performed in a previous study. The findings include a range of benefits and challenges in using test cases for eliciting, validating, verifying, tracing and managing requirements. In addition, we identified three scenarios for applying the practice, namely as a mature practice, as a de facto practice and as part of an agile transition. The findings provide insights into how the role of requirements may be met in agile development including challenges to consider.
|
|
| 4. |
- Martini, Antonio, 1982, et al.
(författare)
-
Towards introducing agile architecting in large companies: The CAFFEA framework
- 2015
-
Ingår i: Lecture Notes in Business Information Processing, Agile Processes in Software Engineering, and Extreme Programming 16th International Conference, XP 2015, Helsinki, Finland, May 25-29, 2015. - Cham : Springer International Publishing. - 1865-1348 .- 1865-1356. - 9783319186115 ; 212
-
Konferensbidrag (refereegranskat)abstract
- To continuously deliver value both in short-term and long-term, a key goal for large product lines companies is to combine Agile Software Development with the continuous development and management of software architecture. We have conducted interviews involving several roles at 3 sites from 2 large companies employing Agile. We have identified current architect roles and gaps in the practices employed at the organizations. From such investigation, we have developed an organizational framework, CAFFEA, for Agile architecting, including roles, teams and practices.
|
|
| 5. |
- Fabijan, A., et al.
(författare)
-
- 2015
-
Ingår i: Lecture Notes in Business Information Processing. - 1865-1356 .- 1865-1348. - 9783319186115 ; 2012, s. 350-351
-
Konferensbidrag (refereegranskat)abstract
- Software development companies experience the road mapping and requirements ranking process to be complex as product management (PdM) strives in getting timely and accurate feedback from the customers. Often, companies have insufficient knowledge about how their products are being used, what features the customers appreciate and which ones will generate revenue. To address this problem, this research aims at helping the companies in closing the ‘open’ feedback loop that exists between PdM and customers. Moreover, the research strives at exploring techniques that can be used to involve customers in continuous validation of software functionality in order to provide PdM with the evidence needed for accurate R&D investments.
|
|
