No Gain without Pain: Feelings an Emotional Practices in an Information System Project
2017
- 223Usage
Metric Options: CountsSelecting the 1-year or 3-year option will change the metrics count to percentiles, illustrating how an article or review compares to other articles or reviews within the selected time period in the same journal. Selecting the 1-year option compares the metrics against other articles/reviews that were also published in the same calendar year. Selecting the 3-year option compares the metrics against other articles/reviews that were also published in the same calendar year plus the two years prior.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Metrics Details
- Usage223
- Downloads188
- Abstract Views35
Artifact Description
This longitudinal study examined how an information systems development team transitioned to an agile way of working. We describe the main events of a large, inter-organizational project, where agile methods and practices were applied for the first time. The organizations involved had a long tradition in heavy, waterfall style projects, and many of those past projects had severe challenges. We examine how the agile way of working was understood by particular groups (project team, management and suppliers), as well as how these understandings changed over time. The lack of experience with agile development, no common view on ‘agility’ and its key principles and practices were obvious challenges for the transition. Our study suggests that complex agile projects need to have very clear goals and management has to be able to communicate these, while preserving the autonomy of teams and individual team members.
Bibliographic Details
Provide Feedback
Have ideas for a new metric? Would you like to see something else here?Let us know