1. This sprint "backlog"

2. Day 1

3. Day 2

4. Day 3

  • Practice

  • Documentation production

5. Materials in live…​

http://bit.ly/jmb-map

6. Principles (Product Backlog)

Application

⇒ Software

Production

⇒ Professional activity ⇒ build

Methods

Agile Methods, wit focus on the Scrum method

Tools

We will combine modern production tools

7. Time schedule and organisation

# Date Topic

1

Jan. 27th

Introduction

2

Jan. 27th

Agile methods

3

Jan. 27th

Project setup

4

Jan. 28th

Agile Manifesto

5

Jan. 28th

Scrum practice

6

Jan. 28th

Scrum practice

7

Jan. 28th

Team building & Sprint 0

8-15

Mar. 3-4

Feedbacks on self-practice; Demo and presentations

16-25

Mar. 17-19

Continuous Integration; Build techniques; Reporting

26-32

Apr. 14-15

Quality assessment; Reporting

8. Evaluation

9. Online practices

https://www.edx.org/course/agile-software-development-ethx-asd-1x

mooc results
Figure 1. My own results

  • Good way of staying in the field between two venues

  • Proof of success (>60%) will count in the evaluation

10. Assignement 2

  • Find a provocative statement about Agile/Scrum

  • Explain in one slide

  • Give your opinion (right/wrong)

11. Assignement 2: Illustration (link)

provocative
Figure 2. Provocative Statement (https://hackernoon.com/agile-doesnt-have-a-brain-51c2835a838#.5i0a1hbbm)

12. Assignement 2: Illustration (hypothesis)

We’ve traded in results for velocity
— Jeff Gothelf
guitare
Figure 3. Bad agile product (https://hackernoon.com/agile-doesnt-have-a-brain-51c2835a838#.5i0a1hbbm)

13. Assignement 2: Illustration (statement)

How to improve:

  • Understanding your customer needs

    • by interviewing them regularly

  • Understanding what’s getting in the way of them being successful

    • by analyzing their behavior on your system

  • Using that information to drive prioritization of features

  • Building in regular feedback loops

    • quantitative and qualitative

    • that confirm that our ideas did indeed add value

  • Letting the right solutions emerge from the use of the system

    • Don’t attempt to predict exactly how each interaction will best be served.

    • Customer usage of early-stage features informs future iterations of those features.

  • Leverage the agility of this way of working to change course

    • re-prioritize when the facts disagree with your plan