1. Alcatel-Lucent CDC Workshop, Coaching & Knowledge Transfer Project Management

2. The Project Lifecycle

3. Presales Requirements Functional Analysis & Design Technical Design & Setup Iterative Development Functional Testing Maintenance

4. Presales Phase  Used to determine size of project  Separate analysis phase  Scope determination (requirements phase or not)  Business Case validation

5. Requirements Phase  All requirements are analyzed and roughly estimated  Draft technical design  Draft planning is drawn up (EMS)

6. Functional design & technical design  Functional (Genesis) design is initiated  Begin of Genesis cycle  Use case definition  Detailed data model

7. Iterative Development Phase  Scrum  Short sprints are essential  Fast feedback  Tight integration of development process aspects

8. Functional Testing Phase  ‘uncovered’ business logic still is manual process   in near future this will be integrated into Genesis  With proper ‘test writing skills’  90% coverage

9. Maintenance Phase  Genesis   Low maintenance cost  Easy change management procedure  Software factory

10. Use Case Driven Functional Analysis

11. What  Defines the interactions between external actors and the system under consideration to accomplish a goal.  System as a black box, what must the system do

12. How  Actors  Someone or something that acts on or is acted on  Preconditions  Conditions that must be true  State of the system  Normal Flow  Primary scenario of the system  Alternate Flow  Secondary or alternative scenarios

13. Why  Easy understandable by business users  Clearly define context  No specific language needed  Track back to business requirements

14. Functional Design

15. Use Cases  All functionalities of the application are described in functional use cases:  Diagram  Description  Preconditions  Normal Flow  Alternate Flow  Mockup

16. Diagram  A use case diagram graphically describes the relationships between various use cases

17. Use Cases  Description  A textual description of the use case  Preconditions  The positive / negative requirements for the use case  Normal Flow  The normal behavior of the use case  Alternate Flow  The abnormal behavior of the use case (error conditions,...)

18. Mockup  A visual screen design is added in the document  Describes how the screens should look like

19. Project Methods / Processes  Various agile methods available:  Lean  Kanban  eXtreme Programming  Scrum  DSDM  Various non agile methods available:  PMBOK  Prince2  LAD  RUP

20. Scrum

21. What  Process skeleton that includes a set of practices and predefined roles  Iterative, incremental process  Agile process  Team based approach

22. Why  Customers become part of the team  Frequent intermediate deliveries with working functionality  Risk mitigation, monitoring and management  Transparancy  Tackles rapidly changing requirements  Maximizes productivity

23. How  Iterative delivery  Incremental delivery  Customer collaboration  Individuals and interaction

24. How

26. Preparation  Contractual agreement  Vision  Initial product backlog  Initial release plan  Assemble team

27. Scrum Roles  Stakeholders  Enable the project  Customers, vendors  Only involved at sprint reviews  Users  The people for who the software is built  Product Owner  Voice of the customer  Verifies use cases  Fills the product backlog  Provides scrum team with right business things

28. Scrum Roles  Scrum Master  Remove impediments  Not the leader of the team  Buffer between team and distracting influences  Enforcer of rules  Team Members  Responsible to deliver the product  Cross-functionally skilled  Typically 5-9 people

29. Scrum Artefacts  Product backlog  High-level  Broad descriptions of all required features and wish-list items  “What” will be built  Open and editable by anyone  Managed by product owner

30. Scrum Artefacts  Sprint backlog  More detailed than product backlog  What the team will implement in the current sprint  Impediment list  Problems, obstacles, unknowns,...

31. Sprint Cycle  Sprint planning meeting  Product owner describes highest priority tasks  Team members choose from the highest priority tasks  Move tasks from product backlog to sprint backlog  How much can the team commit during the coming sprint  Daily Scrum  Same location, same time (ideally in the morning)  Pigs / Chickens  All team members required  Others may attend to listen, but aren’t allowed to talk  Status information  What did you do  What will you do  Any impediments?

32. Sprint Cycle  Sprint review  Team shows what has been accomplished  Demo of new features  Informal meeting  Checking of sprint goal  Sprint retrospective  What went well, not well during the sprint  What improvements can be made on the next sprint

33. Scrum Process

34. Basic Ideas

35. eXtreme Programming

36. Project Dashboard: EMS  The standard way:  Spreadsheets  Emails  Phone calls  Paper documents  No timesheet  No accurate reporting

37. Project Dashboard: EMS  With EMS:  Master projects  All information in one place  Collaboration  Transparancy  Structure  Detailed tracking of every performed minute  Detailed analysis of data  Detailed reporting and follow up

38. Project Dashboard: EMS

44.  How to use  Task assigned after sprint planning  Daily reporting using timesheet component (hours and actual progress)  Issue management and follow up  Benefits  Easy follow up on the progress  Easy coaching  Strong reporting

45. Contact Item Solutions Plantin en Moretuslei 155 2140 Borgerhout  +32 3 236 64 03  info@itemsolutions.com Speaker Kristof Rennen  kristof.rennen@itemsolutions.com