16 giugno 2014. WHO NEEDS AGILE Agile has become a bloated conceptual vortex.

Slides:



Advertisements
Similar presentations
Copyright © Jigsaw 1 Marketing Cloud Manifesto First Draft Submitted by Kevin Akeroyd COO/CMO JigsawOctober 21, 2009.
Advertisements

Applying Agile Methodologies to Traditional Publishing Kristen McLean Bookigee, Inc. February 12 th, 2011.
Practical advice from a lifetime of leadership Ian Smith 1.
Agile Software Development کاری از : مهدی هوشان استاد راهنما : استاد آدابی.
An Agile Retrospective Clinton Keith Overview Retrospective format What works (clear wins)? What doesn’t work so well? What do we need to start doing?
How to Implement Agile in Your Organization
Integrated Product Team (IPT) Process Training
Delivering Enterprise Projects Using Agile Methods Brent Barton May 23, 2006.
PROC-1 3. Software Process. PROC-2 What’s a process? Set of activities in creating software It involves creativity –hard to automate –Requires human judgment.
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger
Archana Mehta. Spot a Failing project Costs a lot more than it should Its takes longer than anyone expected The product doesn’t do what it was supposed.
Agile 101.
NAUG NAUG Knowledge Evening – th February 2007.
The Business Analyst Role in Agile Projects
©2013 Scaling Agile With SAFe August 13, 2013.
Agile development By Sam Chamberlain. First a bit of history..
Supporting Organisations Through CHANGE. Who are we……..  Over 25 years experience in industry – Management, L&D, OE  Track record of achieving results.
1 Software Testing and Quality Assurance Lecture 34 – SWE 205 Course Objective: Basics of Programming Languages & Software Construction Techniques.
Introduction to Agile.
2.01 Part 2 EMPLOY ENTREPRENEURIAL DISCOVERY STRATEGIES TO GENERATE FEASIBLE IDEAS FOR BUSINESS VENTURES/PRODUCTS.
Agile Methodologies for Project Management By – Komal Mehta.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
Capable leadership is vital for meeting the challenges faced by aged care provider organisations and for the continued sustainability of the industry.
Adopting Agile for Enterprise Software Joe Bedell, Software Engineer Jason Breen, Software Engineer Peter Melko, Scrum Master June 15 th, 2015.
Agile Software Development What is Agile? And How are we implementing Agile?
OPM: the USAJOBS Product Owner Perspective By Alesia Booth & Richard Cheng.
Agile Software Development Chapter 3 – Lecture 1 Adrián Susinos.
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
AgileCamp Presents: Agile 101. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution.
Leadership Agility Leadership Agility Leadership Agility 360™
Chapter 3 – Agile Software Development Pepper modification of Sommerville presentation & Colm O’hEocha – AgileInnovation Ltd presentation 1Chapter 3 Agile.
Agile Development In 2001, a group called the “Agile Alliance” signed a “manifesto” that stated: Individuals and Interactions over processes and tools.
Overall Presentation Goal Learn about challenges of adopting Scrum in large enterprises and some rules of thumb. Share experiences and.
Rapid-Fire Presentation Guidance and Instructions Time: 5-minutes Order: TBA Materials: PowerPoint are optional All e-presentation materials should be.
© Innovative Intelligence Re-imagine SWEA Assembly, June 12, 2014 Claude Legrand Managing Partner Ideaction.
Agile: Lessons Learned (a retrospective) Tony
Agile Coaching Sabre How to Sustain Agile - Teams and Organizations L ISA S HOOP.
CS3100 Software Project Management Agile Approaches.
Agile Information Management Development. Agile Project Management Characteristics  Acceptance and even welcome of changing requirements  Incremental.
Agile Methodology Paul Mohrbacher. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through.
Why (or When) Agile Fails Creating high performance software delivery teams.
1 Agile Experience communication and collaboration in agile software development teams Elizabeth Whitworth 7th September, 2006.
Personal Kanban: Effective Visual Management for Everyone Crystal Hart, Senior Lean Consultant Lean Transformation Services Location or Date.
Development Strategy for Engineering Going Forward at Pitney Bowes Sue McKinney Vice President, Engineering Pitney Bowes Incorporation.
Recap Systems Philosophy Organization frames Project life cycle IT projects and recent trends Project management process groups 2.
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
Using Scrum to Improve Teamwork, Communication, Quality and Speed
Evan Leybourn STARTING WITH VSM & KANBAN A practical workshop on value stream mapping & WIP Starting with Value Stream Mapping and Kanban by Evan Leybourn.
It’s Agile …. like! A Corkman’s introduction to Agile software delivery.
Agile 101. Feasibility Study SDLC – What is it? Systems Development Life Cycle: The most commonly used, and generally accepted, project management approach..
Agile Challenges and Opportunities From Organizational Change to Co-Location, what types of challenges and opportunities are unique to Agile projects.
How Good are you at Managing your Processes? Operational Excellence.
DAKTRONICS LEAN JOURNEY. DAKTRONICS VISION To be the WORLD LEADER at informing and entertaining people through dynamic audio-visual communication systems.
Presented By : Prima Business Solutions. Agile Software Development Process.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
Scrum BUT Research Adapting Agile principles in a research environment Gary Morgan Chief Science and Technology Office March 16, 2009 PNNL-SA
Shifting to Agile: Are University Libraries Ready?
Domains of Agility Being Agile Doing Agile Evan Leybourn, 2016 PROCESS
Navigating an Agile Transformation
CEN 4010 Intro to Software Engineering Professor Alex Roque
AGILE METHODOLOGY MANAGE PROJECT USING AGILE SCRUM.
Copy rights  Exam Eligibility  Exam Pattern  Pre requisites  Content Distribution  Tools and Techniques  Domains and Tasks for.
Building Organisational Change Capability
Project Management and the Agile Manifesto
How to Successfully Implement an Agile Project
Scrum Science NGSS: Engineering, Technology, Applications of Science
Project Lifecycle and IT Product Life Cycle
Agenda Start with Why What Are Best Practice Frameworks, and Why Do We Need Them? Best Practices Defined Lean, Agile, DevOps and ITSM/ITIL 4 The Increasing.
Agile, Scrum and CMMI Methodologies
SD5953 Successful Project Management AGILE SOFTWARE DEVELOPMENT
Presentation transcript:

16 giugno 2014

WHO NEEDS AGILE Agile has become a bloated conceptual vortex

What do you think Agile is?

Then what is agile? Agile is the ability to adapt to changes as fast or faster than changes occur. Adapt or DIE An Adjective

 Daily Standups  Close contact with management  Face to face communication  Test Driven Development  Value Stream Mapping  Sustainable pace  Retrospectives  Pair development  …. What is all that other stuff?

A Broader Definition Change Cycle Build Cycle

 Respond to technology change  Reduce investment overhead  Respond to customer need  Drop bad business quickly  Improved predictability  Improved Quality  Try ideas quickly  Reduced Risk  Transparency  Faster Breakeven (ROI) Benefits of Agility

Management Innovation 1911-Fredick W. Taylor Scientific Management Industrial Revolution Pivot

Pivot Again 1911-Fredick W. Taylor Scientific Management Industrial Revolution Pivot

Mental Shifts

Types of Work

Part or Art Part workArt Work Predictable Assembly Focus on Conformance Low change rate Variation is bad Coordinate & Control End is CLEAR Purpose is to deliver Unpredictable Discovery Focus on Creativity High change rate Variation is good Inspect & Adapt End is Ambiguous Purpose is to discover

Part or Art Predictable Assembly Focus on Conformance Low change rate Variation is bad Coordinate & Control End is CLEAR Purpose is to deliver Unpredictable Discovery Focus on Creativity High change rate Variation is good Inspect & Adapt End is Ambiguous Purpose is to discover

Revisiting the Definition Change Cycle Build Cycle

Nested Agility Sequential I & I Sequential I & I = Iterative & Incremental

Practical Example  Shell  Engine Technology  Flight Guidance  Back of the Seat  Tires

1. Retrospectives 2. Teamwork 3. Standups 4. Servant Leadership 5. Value Stream Mapping 6. Long-Lived Teams 7. Collocation 8. Dedicated Teams 9. Pairing What can we learn from the movement?

Lessons Learned  Lessons Learned  Post Mortem  Results are  Project Specific  Team Specific  Domain Specific  Useful LL  Requirements  Communication  Resources (people) DON’T WORK

Retrospective  Frequent  Whole Team  Must be interesting  Project Specific  Team Specific  Domain Specific

Retro Process Set the Stage 1 Collect Data 2 Generate Insights 3 Decide What to do 4 Close 5

Open Q&A

 Agile Community of Practice  Over 32,000 members  Webinars  Experience Reports  Blogs  Wiki  Discussions PMI Agile CoP

Joseph Flahiff, CEO  PMI-Agile Community of Practice Engagement Lead  Lean|Agile Coaching - Training - Consulting  Certified Provider of  Scaled Agile Framework (SAFe)  How NASA Builds Teams   Thank you