Laimonas Lileika will encourage you to unleash your Project Management creativity by combining Agile and Waterfall paradigms. This speech is for you if you are interested in: Importance of Context in Project Management; Most frequent misperceptions about Agile and Waterfall models; Pragmatic approach to project management: how to make a hybrid work in real.

1. Laimonas Lileika
Project Management Practitioner
Vilnius University Lecturer

2. PART I. CONTEXT
L. Lileika | Agile Tour 2015 2

3. Size of
organization?
Requestor
Internal/External?
Budget?
Public or Private? Risk Tolerance? Team?
Culture?
L. Lileika | Agile Tour 2015 3

4. Project management is application of
knowledge, skills, tools, and techniques to
project activities to meet project requirements
PMBOK® Guide and Standards
L. Lileika | Agile Tour 2015 4

5. Project management is application of
knowledge, skills, tools, and techniques to
project activities to meet project g o a l
PMBOK® Guide and Standards (not quite)
L. Lileika | Agile Tour 2015 5

6. Creativity is a phenomenon whereby something
new and somehow valuable is formed, such as
an idea, a scientific theory, an invention, a
literary work, a painting, a musical composition,
a joke, etc.
Wikipedia
L. Lileika | Agile Tour 2015 6

7. Creativity is a phenomenon whereby something
new and somehow valuable is formed, such as
an idea, a scientific theory, an invention, a
literary work, a painting, a musical composition,
a joke, hybrid project management.
Almost Wikipedia
L. Lileika | Agile Tour 2015 7

8. Context
Project management
Creativity
L. Lileika | Agile Tour 2015 8

9. Takeaway1
Project management excellence
and creativity comes from
project manager’s ability to
assess the context, and apply
different tools, techniques and
skills to reach the project goal
L. Lileika | Agile Tour 2015 9

10. PART II. PROCESS VS LIFE CYCLE
L. Lileika | Agile Tour 2015 10

11. Initiate
Plan
Execute
Control
Close
L. Lileika | Agile Tour 2015 11

12. Initiate
Plan
Execute
Control
Close
L. Lileika | Agile Tour 2015 12

13. …initiated by completing
project charter
…planned by producing backlog,
release plan, high level design, etc.
…executed in small iterations where each iteration
ends with the production ready product increment
…monitored (inspected), and planned forward
based on actual data available at time (adopted)
…closed when deliverables are
accepted by requestor and ELS is over.
L. Lileika | Agile Tour 2015 13
project needs to be …

14. Takeaway2
There is only one project
management process, regardless
of the life cycle used
L. Lileika | Agile Tour 2015 14

15. PART III. AGILE OR WATERFALL?
L. Lileika | Agile Tour 2015 15

16. Similar
Medium Process
Different
Language
Roles
Life cycle
Metrics
L. Lileika | Agile Tour 2015 16

17. L. Lileika | Agile Tour 2015 17
Waterfall
Detailed
planning in the
beginning
One moves to
next step only
after completing
previous one
All steps are laid
out and
dependencies
mapped

18. L. Lileika | Agile Tour 2015 18
Waterfall
Best known for…
Dealing with
physical
objects
Reliable
future project
forecast
Defined tasks and
phases that must
be completed in a
specific sequence
Criticized for…
Less effective for software,
design and other non-physical
or services-bases projects
Scope changes are
usually slow
Requires substantial
scope and schedule
planning before
work begins

19. L. Lileika | Agile Tour 2015 19
Agile
Flexible
approach to
project
management
Principles of
collaboration,
adaptability and
continuous
improvement
Iterative project
release cycles

20. L. Lileika | Agile Tour 2015 20
Agile
Best known for…
Service-oriented
projects like
Software
development
projects
Engagement and
collaboration from
all team members
Quick course
correction based on
early feedback
Empowers team to
work creatively and
efficiently
Criticized for…
Not suitable for
strictly defined
scope and
requirements
Continues hard
work on backlog
maintenance and
tech debt
management
High risk due to
uncertainty around
triple constraint at
the beginning

21. Takeaway3
Hybrid project management is
application of two (or more)
project management
life_cycles/methodologies in a
single project
L. Lileika | Agile Tour 2015 21

22. PART IV. HOW TO…?
L. Lileika | Agile Tour 2015 22

23. 23
• Agile means continuous planning
• Documentation is still important, but the format could vary
• Agile embraces complaints, as a trigger for improvements!
%
Yay, let’s do Agile
L. Lileika | Agile Tour 2015

24. What will you need?
L. Lileika | Agile Tour 2015 24
Assess the context
Respect the fact of ONE process
Produce project charter to support hybrid delivery
Acquire Team to work Agile, and team to work Waterfall
Develop single project schedule
Capture project and product scope
Setup common reporting and metrics
Sell this idea to stakeholders!

25. Challenges.
Nothing comes easy
because
CONTEXT
does differ
L. Lileika | Agile Tour 2015 25

26. Meet the Team
L. Lileika | Agile Tour 2015 26

27. Development Team
Dedicated
Collocated
Infrastructure Team
Virtual
On estimated effort basis
L. Lileika | Agile Tour 2015 27
Meet the Team

28. Definition of Scope
Project scope
Product scope
Infrastructure Requirements
Product Requirements
L. Lileika | Agile Tour 2015 28

29. Magic behind Estimating
Estimating Product Backlog
Estimating Infrastructure setup
Estimating Release plan
Adding Management and coordination
L. Lileika | Agile Tour 2015 29

30. Project Schedule Concept
L. Lileika | Agile Tour 2015 30

31. Project Schedule Concept
L. Lileika | Agile Tour 2015 31

32. Project Schedule
L. Lileika | Agile Tour 2015 32

33. Project Schedule
L. Lileika | Agile Tour 2015 33

34. Project Schedule
L. Lileika | Agile Tour 2015 34

35. L. Lileika | Agile Tour 2015 35

36. Team Management
36
Demo /
Retrospect
Visual
Board
Definition
of Done
Daily
Standup
Sprint
Planning
Sprint
Goal
Achieving Commitment
Embracing
Accountability
Focusing
on results
Team
Building
workshops
L. Lileika | Agile Tour 2015

37. Ground Rules
37
• Sprint Lenght
– 4 Weekes
• Sprint Planning
– First Monday every 4th week
• F2F
• Scope 9:00 –12:00
• Team Lunch
• Tasking out 13:00 – 15:00
• Daily Scrum
– Monday-Thursday
• 9:00 – 09:15
• Call in if you cannot attend F2F
• Sprint Review
– Last Thursday every 4th week
• Demo 10:00 – 11:00
• Team Lunch
• Retrospective 12:00 – 13:00
• Work@Home
– Fridays
• Holiday tracker – 1 Sprint ahead
• Don’t be late
• Don’t attend meetings with no agenda
• Prepare for meetings
• Respect Definition of Done
Team
Ground
Rules
L. Lileika | Agile Tour 2015

38. Definition of Done
• Coded/implemented
• Peer reviewed (pair programming counts as peer review)
• Code is run against current version in source control
• Code is commented in source control and checked in
• Code is commented with VB Commenter on Public/Friend methods
• Story/use case manual test plan updated
• Fit test written (with help of SQA person)
• UML diagram updated
• Unit tests written and passing
• 90 percent code coverage achieved
• Build and package changes are communicated to build master (i.e.
introducing a new file or something)
• Task list hours are updated and task is closed out
• All to-do items in code are completed
L. Lileika | Agile Tour 2015 38

39. Takeaway4
Don't look for one process, one methodology to fit all projects
Choose one dominant methodology
Bring Agile values to hardware development
If something doesn’t work – don’t stick with it
Be creative about delivery and focus on value
Call it Enterprise – it sounds good!
L. Lileika | Agile Tour 2015 39

40. Takeaway1
Project management excellence
and creativity comes from
project manager’s ability to
assess the context, and apply
different tools, techniques and
skills to reach the project goal
L. Lileika | Agile Tour 2015 40

41. Takeaway2
There is only one project
management process, regardless
of the life cycle used
L. Lileika | Agile Tour 2015 41

42. Takeaway3
Hybrid project management is
application of two (or more)
project management
life_cycles/methodologies in a
single project
L. Lileika | Agile Tour 2015 42

43. etc.

44. Laimonas Lileika: professional profile