confoo-2015-beyond-agility.pdf

Over the past decade the Agile practice has become the defacto methodology to manage project. But how come we still have projects that go over schedule and budget?

In this presentation, Yann Larrivée will show you how you can improve your team performance by using some of the core concept of Agility. Additional technics will be presented to help fill-in the gaps left by Agility.

Transcript

1. foolab.ca | @foolabca Beyond Agility for Faster Delivery ConFoo, Montréal – February 19, 2015
2. 2 Yann Larrivée • Developer & consultant at FooLab • I bring projects to success • Twitter: @ylarrivee
3. foolab.ca | @foolabca Lessons learned from my journey through Mordor.
4. 4 Open your mind
5. 5 Presentation objectives #1 It's not about:  It's not about "Agile is bad"  It's not about a new project management methodology  It's not about comparing methodologies: Scrum Kanban, XP, Lean, ...
6. 6 Presentation objectives #2 It's about:  A "mental framework"  Delivering projects faster  Increase your level of happiness and satisfaction with what you do  It's about success  Spend more time with your family
7. 7 What is agility ? “The ability to think and draw conclusions quickly” “The power of moving quickly and easily”
8. 8 We can resume“Agility” to:  Think  Move  Quickly  Easily  Draw Conclusion
9. 9 What is needed to be Agile?  A destination  A point of origin  Identify/understand threats
10. 10 How to reach objectives? The state of mind  Winning mindset  Understand your objectives  Believe the objectives are achievable  You need skills  Determination : Passion for what you do  Discipline
11. 11 The Point of Origin: Situation Appraisal It includes:  Business Vision  Business Mission Defining the Situation Appraisal:  Who are we as a business?  What are we doing as a business?  Who are we doing it for?
12. 12 Defining the value #1 Determine the actors: Who will this project affect?  Business owners  Employees (internal users)  Partners (third party)  End customers
13. 13 Defining the value #2  How will it improve the current situation?  Why is this situation worth to be addressed?  How will we feel once these goals are achieved?  How will we feel if they are not achieved?
14. 14 Defining the value #3 Why should I care?  It justifies why you are doing this.  Your level of commitment to the success.  In case of doubt, always refer to the value.  Always deliver value, not features.
15. 15 The destination: Business Objectives Determining the Business Objectives  What is the ideal expected outcome?  What results are we trying to accomplish?  What are we trying to improve?  Why are we seeking to do this project?
16. 16 Measure progress Have you reached the finish line? • Have clear metrics of success  Increase performance by 50%  Optimize the platform to serve X million customers  Reduce the response time to 5 seconds
17. 17 Options of Implementation • How we will achieve these goals? • Strategies and tactics to be explored.
18. 18 Timing What needs to be done and when? • Software architecture • Coding & demos • Beta testing • Live in production • Staging and production servers • SSL certificates • Confirm wireframes • Technological choices
19. 19 Project threats Anything that can make a project at risk:  Human resources  Lack of expertise  Servers  SSL certificates  Dependency on third party ...
20. 20 Accountability: Who is responsible for what?  Giving access to servers, database, git  Architecture, project management, deployment  Raising flags, share information  Follow-ups, project management
21. 21 Objective Driven Development  Situation appraisal  Value  Objectives  Metrics  Options  Timing  Project Threats  Accountability
22. 22 Creating the plan #1 • Project definition • Create wireframes • Validate the wireframes • Document the wireframes
23. 23 Creating the plan #2 • Mind Maps (Impact Mapping) • Use case diagrams • ERD • Flow charts • ...
24. 24 Time line • What's your go live date? • Work your way backward • Have iterations • Project should takes weeks to do, not months • Leave yourself some buffer • Nothing goes according to plan
25. 25 Execution #1:The meetings • Kick off and iteration meeting • Daily status meetings • Weekly retro
26. 26 Execution #2: Coding • Code • Test • Review • Demo
27. 27 What is “Beyond Agility”? #1 It's about Success • It's about reaching goals • It's about winning • Winning is a choice
28. 28 What is “Beyond Agility”? #2 Winning is a mindset • Be realistic and positive. • See problems as opportunities. • Don't focus on problems, focus on solutions. • Focus on the great outcome. • Create a winning scenario. • Believe you can achieve this.
29. 29 What is “Beyond Agility”? #3 • Create a winning team • People who desire to win • People who complete your skill set • People with positive energy • Execute and validate everything with the outcome
30. 30 Celebrate like you won the Stanley Cup!
31. 31 What is “Beyond Agility”? #4 • Have pride in your achievements • Write your success story • Share it with your peers • Be a winner • Be EPIC
32. 32 Win the CUP every day! This is “Beyond Agility” This is “Objective Driven Development.” Twitter: @ylarrivee E-mail: yann@foolab.ca Website: foolab.ca Advice, project rescue, objective-driven developmenta.