#1303 Agile Software Engineering change request pending

A new sub-category is needed to address the lack of clarity around agile software development.

Despite some improvements in SFA7, the framework currently reflects a plan-driven model of software development processes. While agile is mentioned is several sub-categories, The overall framework looks like a plan-driven model (with tasks configured around design, implement and test). Agile software development, organises these same tasks within increments (rather than development phases). Nowadays, more than 50% of software development projects use agile methods (in UK and Netherlands and probably USA).


A new sub-category is proposed to empahsise skllls that are currently poorly represented in SFA7, namely: product champion, agile coach and

Product Champion (product owner in Scrum), further details...


Agile Coach (scrum master in Scrum), further details


Self-organising Team member, further details


Here are some empirical research papers that describe these missing skills

Bass, J. M. (2015). How product owner teams scale agile methods to large distributed enterprises. Empirical Software Engineering, 20(6), 1525–1557. https://doi.org/10.1007/s10664-014-9322-z
Bass, J. M. (2016). Artefacts and agile method tailoring in large-scale offshore software development programmes. Information and Software Technology, 75, 1–16. https://doi.org/10.1016/j.infsof.2016.03.001
Noll, J., Razzak, M. A., Bass, J. M., & Beecham, S. (2017). A Study of the Scrum Master’s Role. Product-Focused Software Process Improvement, 307–323. https://doi.org/10.1007/978-3-319-69926-4_22

Current status of this request: pending