Information Technology Reference
In-Depth Information
have the user stories readily identified that are most important at the current
stage of the development. After the sprint is done, the product owner is also
responsible for deciding whether a user story has been suciently realized, or
whether there is work remaining.
Fig. 1.
Agile Development with Scrum
This requires that the product owner has a deep understanding of what the
team has actually produced during the sprint. Especially when the product owner
has to fulfill other duties in the organization, it can be overwhelmingly complex
and time-consuming to keep up with the current status of the development. Dur-
ing a sprint, developers typically coordinate themselves in daily Scrum meetings,
personal communication, etc., but the product owner is usually only a passive
participant. For agile software development by Scrum to work, however, it is cru-
cial that the product owner has the relevant requirements and user stories for
the system to be developed and their priorities available when needed. Clearly,
the product owner is not omniscient and may sometimes not be aware of recent
development activities. Therefore, a monitoring process that can help the prod-
uct owner to take decisions can prevent taking wrong priorities and thus a waste
of resources.
In this position paper, we propose the use of natural language processing
(NLP) techniques to overcome the problem that the product owner needs to keep
track of the current status of development and the completed or non-completed
user stories. By analyzing the artifacts created by the developers, such as source
code, code comments or bug reports, connections can be established between
the user stories that are planned to be completed during the sprint and the
actual progress achieved by the development team. As the artifacts that are pro-
duced usually are not captured by some formal representation, natural language
Search WWH ::
Custom Search