28,879 research outputs found
USING HYBRID SCRUM TO MEET WATERFALL PROCESS DELIVERABLES
System Development Life Cycles (SDLCs) for organizations are often based upon traditional software development models such as the waterfall model. These processes are complex, heavy in documentation deliverables, and are rigid and less flexible than other methods being used in modern software development. Consider by contrast, agile methods for software development. In essence, agile methods recommend lightweight documentation and simplified process. The focus shifts to completed software as the "measure of success" for delivery of product in software projects, versus accurate and comprehensive documentation, and the accomplishment of static milestones in a work breakdown structure. This thesis implements, explores, and recommends a hybrid agile approach to Scrum in order to satisfy the rigid, document-laden deliverables of a waterfall-based SDLC process. This hybrid Scrum is a balance of having enough documentation and process - but not too much - to meet SDLC deliverables, while at the same time focusing on timely product delivery and customer interactions that come from an agile approach to software development.M.S
Non-Technical Individual Skills are Weakly Connected to the Maturity of Agile Practices
Context: Existing knowledge in agile software development suggests that
individual competency (e.g. skills) is a critical success factor for agile
projects. While assuming that technical skills are important for every kind of
software development project, many researchers suggest that non-technical
individual skills are especially important in agile software development.
Objective: In this paper, we investigate whether non-technical individual
skills can predict the use of agile practices. Method: Through creating a set
of multiple linear regression models using a total of 113 participants from
agile teams in six software development organizations from The Netherlands and
Brazil, we analyzed the predictive power of non-technical individual skills in
relation to agile practices. Results: The results show that there is
surprisingly low power in using non-technical individual skills to predict
(i.e. explain variance in) the mature use of agile practices in software
development. Conclusions: Therefore, we conclude that looking at non-technical
individual skills is not the optimal level of analysis when trying to
understand, and explain, the mature use of agile practices in the software
development context. We argue that it is more important to focus on the
non-technical skills as a team-level capacity instead of assuring that all
individuals possess such skills when understanding the use of the agile
practices.Comment: 18 pages, 1 figur
What influences the speed of prototyping? An empirical investigation of twenty software startups
It is essential for startups to quickly experiment business ideas by building
tangible prototypes and collecting user feedback on them. As prototyping is an
inevitable part of learning for early stage software startups, how fast
startups can learn depends on how fast they can prototype. Despite of the
importance, there is a lack of research about prototyping in software startups.
In this study, we aimed at understanding what are factors influencing different
types of prototyping activities. We conducted a multiple case study on twenty
European software startups. The results are two folds, firstly we propose a
prototype-centric learning model in early stage software startups. Secondly, we
identify factors occur as barriers but also facilitators for prototyping in
early stage software startups. The factors are grouped into (1) artifacts, (2)
team competence, (3) collaboration, (4) customer and (5) process dimensions. To
speed up a startups progress at the early stage, it is important to incorporate
the learning objective into a well-defined collaborative approach of
prototypingComment: This is the author's version of the work. Copyright owner's version
can be accessed at doi.org/10.1007/978-3-319-57633-6_2, XP2017, Cologne,
German
Recommended from our members
Designing a consulting services architecture model
textDuring my years of experience in the technology industry, it has become obvious that standard processes and methodologies within the engineering discipline are at a mature state. The realization though is that software engineering specifically lags behind. Most software engineering methodologies that I have studied focus on the mission of software development. It is this realization and the need for structure that led me to review existing methodologies used within my company's software services organization. The definition of what a successful software services methodology entails is rather limited. This report will provide a history of existing software engineering methodologies that I have studied, describe an initial services method that was being developed within my organization, develop a new model that addresses previous shortcomings and identify additional components required to further define a strong software services-oriented delivery methodology.Electrical and Computer Engineerin
Roles and responsibilities in agile ICT for development
This paper examines the different roles in designing interactive software in a ICT for development context.
Using experiences from a participatory action research project, in which we used agile methods to design and
deploy an system to support ‘agricultural information flow’ for a co-operative of small farmers in rural India, we
identify points of difference between the roles in standard descriptions of agile software methods and the roles as
they emerged in our project. A key finding is the critical role played by a ‘Development Project Manager’ in
facilitating dialogue, orchestrating the activities of other actors and in building the capabilities and confidence of
all the participants in joint action
- …