System Development. Software Project Management Triangle Waterfall Model V-Model Agile Development User Acceptance Test Minimum Viable Product

Transcription

1 System Development Software Project Management Triangle Waterfall Model V-Model Agile Development User Acceptance Test Minimum Viable Product

2 The Problem

3 Agile versus Classic Management Status Quo Agile Verbreitung und Nutzen agiler Methoden, 2012.

4 Software Project Management The old iron triangle John Manuel Kennedy T.

5 Software Project Management The new iron triangle John Manuel Kennedy T.

6 Definitions System development Market research, conception of requirements, implementation, testing, deployment, maintenance Elements (4) of the iron triangle Scope (what must be built) Schedule (when it must be built by) Resources (how much it must cost) Quality of functions

7 Software Process Models Waterfall model V-Model Scrum (for Software development)

8 Waterfall Model (1956) Was new: Software dev was split up in different phases as program became more complex

9 Waterfall with test Internal Action Waterfall + Big Bang User involved action Start identify Requirements Estimation & Planning Contract Implementation Big-Bang Test Time The customer signs the technical specification ( Pflichtenheft ) as a contract after planning the project manager broadcasts the plan that is to follow

10 V-Model (1991) New: testing as important as development System development lifecycle Left: definition requirements, formulation of specs Right: test on different levels Running from left to right and up again (no loop)

11 Test driven V-Modell Requirements driven design & testing at different levels V-Modell Unit test (regression test: automated unit test that is repeated after each change of the source code, nightly builds) Integration Test (testing interfaces between classes) System Test (testing the software build into the custumer's system) User acceptance Test (the user plays with the system) Identify US Start document US write acceptance tests Estimation & Planning Impl. US1 Impl. US2 Impl. US3 Impl. US4 Test Test Test Test Contract Time

12 Acceptance Test User story pattern AS A [user of the function] I WANT [functionality] SO THAT [benefit to the user] Acceptance test pattern GIVEN [an initial context] WHEN [some event happens] THEN [an expected state linked to the functionality]

13 User Acceptance testing is the process of verifying that stories were developed such that each works exactly the way the customer expected it to work Mike Cohn used by the product owner to know that the acceptance criteria have been met and the User Story is Done help drive development in an Acceptance Test Driven Development environment (see V-Model) Acceptance tests serve as the source of product regression tests (for automatic testing at changes) Integration / units tests are derived

14 Scrum A general management method (not only for software) transfers responsibility from Manager to team Measures what really works for the customer (tested prototypes) instead of artificial indices fosters individual motivation

15 Agile Manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan

16 The goal New: don't deliver the product as monolith but in the form of incremental deliverables The most important functionality first Least viable product component (inspired by lean startup Perfection is achieved, not when there is nothing left to add, but when there is nothing left to remove. Antoine de Saint-Exupéry) Fail fast fail early The most knowledge about specification and customer needs can only be gained by delivering a working prototype

17 Minimum Viable Product

18

19 SCRUM Scrum User involved action Internal Action 1st User Story Processing Select Estimation 1st US User Story Estimation Requirements Prioritize Test deliverable Start Implementation Time USP User Story Processing PRIO Prioritize EST Estimation Scrum Contract US Start EST PRIO Sprint 1 Time Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6

20 Charts Kanban Chart Self-assignment of tasks Burndown Chart Project monitoring and Time to market prediction

21 Visualize status with Kanban board Thomas Daniel Tobias

22 Lean Management with Kanban 6 columns Backlog contains the User Stories (US) Todo (Bereit) Splits US into tasks with an effort between 1h and 1 day Doing To prevent overloading of team members, the number of items is restricted (2) Ready to test Done

23 measures the speed of the team wrt to usergoals Enables the estimation of the time to done -boards/en/resources/fig4_dailyburndown.jpg Predict future with burndown chart