The goal of this course is to allow the student knowing the basic concepts and principles of agile software project management methods and techniques. To achieve this aim, the students have to acquire specific knowledge and a set of skills and competencies.
Regarding the students knowledge at the end of this course, the student has to know:
1) Basic principles of the agile software development approach. (PO: a, c)
2) Most relevant methods for agile software development. (PO: a, c)
3) Know the business processes related to the creation of innovative and disruptive software services or products (PO: a, c)
a) Lean Startup Overview
b) Minimum Viable Product
e) Business Model Canvas
4) Know the processes and techniques for an agile requirements management. (PO: a, c)
a) Techiques to discover and elicit new products or services: Product Visión Box, Story Mapping y Story Telling
b) Techniques to manage a product backlog: Estimation, Priorization Technical Debt
5) The foundations of the management of software projects based on an incremental and iterative lifecycle with time-boxed iterations. (PO: a, c)
a) Porfolio, Product, release and iteration planning.
b) Quantitative agile projects control and tracking.
c) Iterations control and tracking.
d) Showcases and retrospectives.
6) Understand the difference between traditional and agile software development methods, being able to determine the most appropriate approach depending on a specific Project restrictions. (CECRI16) (PO: a, c)
Regarding the skills and competencies, they can be classified in two groups: specific and generic competences.
Regarding the specific competences, at the end of the course, an student has to be able to (CG1):
1) Organize the strategic project for creating a disruptive service or product (PO: a, c, i, k)
2) Identify and manage the user needs regarding an information system using the user stories technique. (PO: a, c, i, k)
3) Organize the different iterations of a software development project applying the adaptative planning technique (CESI5). (PO: a, c, i, k)
4) Know agile project control techniques: daily meetings, burn down/up charts, showcases and retrospectives. (PO: a, c, i, k)
Regarding the generic competences, at the end of the course, an student has to be able to:
1) Organize, plan and manage a team to develop a project applying the agile software development principles. (PO: d)
2) Follow a plan to obtain a product with the required level of quality. (PO: e)
3) Apply the principles learnt to the management of a software project.
4) Problems resolution including the identification and validation of an hypothesis to solve the problem in a collaborative and participative way (PO: d, e)
5) To control and communicate effectively the current state, results and benefits of a software project using objective evidences. (PO: g)