I would like to know which are the key factors on agile software development projects and, if possible, which are their influence on the project's success. References for any agile process, methodology or framework (e.g. XP, RUP, Kanban, Scrumban, etc.) are appreciated!
Hi Marco, thanks for the reply.
Key factors: important aspects that influence the success of a project.
I think we could agree that, for software project success, the main key factors would be: software specification, design and implementation, evolution and validation. I want to breakdown each of these key factors into factors that can be measured and build a model. For example, for agile projects, we could have for software specification: Product backlog management and release plan. We could continue breaking the items... For Product backlog management, we could have: estimations quality, emergent, User Story descriptions quality, etc.
I did a similar work for Scrum considering its principles and rules and some "best practices" (e.g., XP practices). I have an article about it in my profile, if you wish to take a look.
I am interested in having a "more generic" model and focus on agile projects. So, before starting to look for data, I would like to know if you have or know any data that could help me.
Cheers
Hi Mirko,
Ok, got it. Well, I think, you have two aspects. First: success factors. As far as I know, this is quite well researched, and you can find numerous case studies reporting on success factors and influence. Good candidates are conferences, such as ICSSP, XP, Profes. Furthermore, several SPI-related studies investigate success factors (mainly for SPI projects), but they are quite close to project-related factors. If this is what you are looking for, just do a little search via Google or Researchgate (several authors have SPI-related contributions there).
A good point to start regarding more concrete metrics is the book by Stephen Kan: Metrics and Models in Software Quality Engineering
There is an online version available here: https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CDkQFjAA&url=http%3A%2F%2Fhornad.fei.tuke.sk%2Fkpi%2Fperson%2Fsamuelis%2Fmetrics%2FMetrics%2520and%2520Models%2520in%2520Software%2520Quality%2520Engineering%2C%25202ed%2520%255BAddison%2520Wesley%272002%255D.pdf&ei=yH09U7q4NIOEtQbAkIGwDA&usg=AFQjCNH0WwdZ1nzsANN17tNZIhUnSXK9jQ&sig2=Mas4e5oqRMWBmlDbi0uXwA&bvm=bv.64125504,d.Yms
- however, there is no copyright statement. Therefore, I don't know whether this is legal (my students found the link the week after I bought it...). Anyway, you can also take a look inside at Amazon ;)
Another aspect is the "more generic model". In fact, we conducted some research on that topic. Right now, we compiling an article regarding such a model. You can have some first insights here:
https://www.researchgate.net/publication/256471532_Towards_Artifact_Models_as_Process_Interfaces_in_Distributed_Software_Projects
In this paper, we present some preliminary findings, inter alia, a generic model (1st iteration), which was crafted from a systematic literature review/mapping study. We use models like this to create measureable artifacts to ease the assignment and use of metrics. Does this go into your direction of interest?
All the best, Marco
Conference Paper Towards Artifact Models as Process Interfaces in Distributed...
Hi Marco! Thanks for the reply! Yes... I think you pointed me to the right direction! I will do some reading and afterwards, if you are interested, we could talk to collaborate on something.
Best regards!
Another key factor is also the usage of only the right degree of agility for specific projects. A good example for degree of agility is the usage of agile practice, and therefore maybe my mapping study could help: https://www.researchgate.net/publication/263398618_Agile_Practices_in_Practice_-_A_Mapping_Study
Best regards!
Conference Paper Agile Practices in Practice - A Mapping Study
- Badges
- Science topic
- Similar topics
- Philosophy
- Esthetics
- Interpretation