SlideShare a Scribd company logo
Bringing Sense, Sensibility, and Sanity to projects.
What they are and what they are not.
 
WHAT ARE THEY? Unique Output Specific Goals Professional Judgment Distinctive events Change Focus Time Boundaries Temporary Resources Distinct and Interdependent Completion focused Conscious Constitution WHAT THEY ARE NOT. Departments Teams Committees Outsourced Individuals or groups
 
 
Exercise #1 Discuss the project pyramid Exercise #2 What is the most important part of the pyramid for your business.
How work gets done.
Ad-Hoc Waterfall Agile
Hey, can you do me a favor?? Not a formal method Common sense based Dialog becomes action Quick Rework and Patches Problems with this approach Lack of Clarity in Sponsorship Unpredictable schedules and costs Morphing requirements and project drift High potential for surprise factor
 
Long project durations Heavy dependency of the creation of documentation. Lack of flexibility The project is outdated by the time of delivery.
Individuals and interactions  over processes and tools  Working software  over comprehensive documentation  Customer collaboration  over contract negotiation  Responding to change  over following a plan  That is, while there is value in the items on the right, we value the items on the left more. Manifesto for Agile Software Development (February 13 th , 2001)
Ad-hoc and Waterfall approaches to project are not very effective Change happens so fast in business that you need a faster, better and leaner approach to your projects. Agile helps you complete projects to meet the above challenges.
The Who, What, When and Where of Agile project mangement
A collection of features and requirements you need to complete the project. The Scrum Process Sprints to transform features and requirements into product Rapid iterations. Cyclical in nature.
THE PRODUCT BACKLOG Customer Feature #1 Internal Feature #1 Customer Feature #2 Bug fix #1 Internal Feature #2 Internal Feature#3 Customer Feature #3 The wish list of what people want done. THE SPRINT BACKLOG Bug Fix #1 Customer Feature #1 Customer Feature #2 Customer Feature #3 The list of tasks agreed to be completed during the next sprint.
This is where the work gets done At the start of each  working day there is a Scrum meeting to update the team on the sprint. Sprints can be as short as a week and as long as four weeks. Shippable product must be provided at the end of the sprint. Each Sprint is called an iteration.
The scrum master is the project leader and person who works with IT professionals each day.  They keep the project on track, on budget, and with high quality.  They should be good with people and have a solid grounding in technology. The Product Owner works with the Scrum Master.  They understand the business and customers who use the product.  They should be experienced pros who can take vague requirements and turn them into a concrete to do list.
The pigs on the project are the ones who make it a reality.  They are the ones who are committed and have the most to loose if the project fails.  These are your IT professionals.  The Chickens are the ones involved with the project.  They don’t have as much invested and their career is not as impacted by project failure.  These people can affect the project in both positive and negative ways.  These are sales people, marketing professionals, accounting types, and the legal department
 
 
Should start in the IT department for small projects Expand to bigger projects Move to other aspects of the business The entire enterprise should be adopting agile principles.
Get started right away. Set small achievable goals and deadlines and meet them. Soon no project is too big for this approach. When eating an elephant you start one bite at a time.  -Creighton Abrams
Exercise #3 do a project with an agile approach. Exercise #4 how do you think your business is going to change using this approach.
Things you need to do to make agile work in your business.
Commitment Openness Focus Respect Courage
These values must be agreed upon and out in the open. Everyone should practice these virtues and not tolerate those who don’t You must spend more time screening employees to make sure they practice these values.  Average is just not good enough.
Why is all this necessary?
IBM uses it to develop software Fits seamlessly with lean management approaches to business. Software project success rate with Agile is 83% compared with the 24% compared to the chaos study. Scott Ambler July 2008
No cost to the firm More responsive to changes in the business climate Better customer service A process that both IT professionals support and business leaders can understand.
 

More Related Content

PPTX
The 12 Agile Principles
PPTX
Agile development
PPTX
The hothouse approach
PDF
Richard Powell CV
PDF
Starting a new project using Scrum
PPTX
12 agile principles
PPTX
Agile and the BA
PDF
Agile And Lean Practices - The Mobile Academy
The 12 Agile Principles
Agile development
The hothouse approach
Richard Powell CV
Starting a new project using Scrum
12 agile principles
Agile and the BA
Agile And Lean Practices - The Mobile Academy

What's hot (19)

PPTX
Integrating Ux And Agile
PDF
Perfect Wedding: Lean Startup and Agile
PPTX
What agile is not
PDF
Agile Manifesto
PPTX
Lean software development tips and tricks - Agile Tour Dublin 2014
PPTX
Agile Metrics Meetup: What to Measure and How?
PPTX
Requirements = Scope
PDF
Why small businesses, consultants and freelancer need project management
PPTX
Techniques for Keeping Distributed Retrospectives Effective and Fun
PPTX
Successful Agile/UX
PPTX
Creating your development process
PDF
A Software Development Approach to Help You End Up with the Product You Reall...
PDF
Lean Software Development
PPTX
How to do Estimates (well) in Agile?
PPTX
Non-IT Agile Values and Principles Deck
PPTX
Preparing project professionals for the role of project manager
KEY
Agile intro module 4
PDF
LKCE18 Jesper Boeg - Your improvement potential is much bigger than you think...
PPS
About Conrad Baugh Jan 2011
Integrating Ux And Agile
Perfect Wedding: Lean Startup and Agile
What agile is not
Agile Manifesto
Lean software development tips and tricks - Agile Tour Dublin 2014
Agile Metrics Meetup: What to Measure and How?
Requirements = Scope
Why small businesses, consultants and freelancer need project management
Techniques for Keeping Distributed Retrospectives Effective and Fun
Successful Agile/UX
Creating your development process
A Software Development Approach to Help You End Up with the Product You Reall...
Lean Software Development
How to do Estimates (well) in Agile?
Non-IT Agile Values and Principles Deck
Preparing project professionals for the role of project manager
Agile intro module 4
LKCE18 Jesper Boeg - Your improvement potential is much bigger than you think...
About Conrad Baugh Jan 2011
Ad

Viewers also liked (8)

PPT
Learning to Manage IT workers
PPT
Song Of Roland
PDF
成功するチームの隠し味
PDF
The impact of innovation on travel and tourism industries (World Travel Marke...
PPSX
Reuters: Pictures of the Year 2016 (Part 2)
PDF
Open Source Creativity
PDF
The Outcome Economy
PDF
The Six Highest Performing B2B Blog Post Formats
Learning to Manage IT workers
Song Of Roland
成功するチームの隠し味
The impact of innovation on travel and tourism industries (World Travel Marke...
Reuters: Pictures of the Year 2016 (Part 2)
Open Source Creativity
The Outcome Economy
The Six Highest Performing B2B Blog Post Formats
Ad

Similar to Agile And Your Business V2 (20)

PDF
Glossary of Agile Terms
PDF
A real-life overview of Agile workflow practices
PPTX
Software Engineering And Project Management Basics
PPTX
Agile pm v2
PPT
Outsourcing With Agile
PPTX
Professional Project Manager Should Be Proficient in Agile
PDF
The Business value of agile development
PPTX
Introduction to Agile
PPTX
What are the Tools & Techniques in Agile Project Management?
PPT
Agile intro resources
PPT
Agile Project Management training by manohar prasad
PDF
Introduction to Agile Dr Richard Guerrero_Wessex AHSN Learning Lab
PPTX
Scrum jan 22nd - manoj vadakan - conscires agile practices
DOC
The Agile Alliance has Stated in their Manifesto
PDF
Agile Project Management Part 1 Final
PPTX
Close to agile
PPTX
Agile and its impact to Project Management 022218.pptx
DOCX
PMI-ACP Study Guide
PPTX
Agile Development at W3i
PDF
Agile project management using scrum
Glossary of Agile Terms
A real-life overview of Agile workflow practices
Software Engineering And Project Management Basics
Agile pm v2
Outsourcing With Agile
Professional Project Manager Should Be Proficient in Agile
The Business value of agile development
Introduction to Agile
What are the Tools & Techniques in Agile Project Management?
Agile intro resources
Agile Project Management training by manohar prasad
Introduction to Agile Dr Richard Guerrero_Wessex AHSN Learning Lab
Scrum jan 22nd - manoj vadakan - conscires agile practices
The Agile Alliance has Stated in their Manifesto
Agile Project Management Part 1 Final
Close to agile
Agile and its impact to Project Management 022218.pptx
PMI-ACP Study Guide
Agile Development at W3i
Agile project management using scrum

Agile And Your Business V2

  • 1. Bringing Sense, Sensibility, and Sanity to projects.
  • 2. What they are and what they are not.
  • 3.  
  • 4. WHAT ARE THEY? Unique Output Specific Goals Professional Judgment Distinctive events Change Focus Time Boundaries Temporary Resources Distinct and Interdependent Completion focused Conscious Constitution WHAT THEY ARE NOT. Departments Teams Committees Outsourced Individuals or groups
  • 5.  
  • 6.  
  • 7. Exercise #1 Discuss the project pyramid Exercise #2 What is the most important part of the pyramid for your business.
  • 10. Hey, can you do me a favor?? Not a formal method Common sense based Dialog becomes action Quick Rework and Patches Problems with this approach Lack of Clarity in Sponsorship Unpredictable schedules and costs Morphing requirements and project drift High potential for surprise factor
  • 11.  
  • 12. Long project durations Heavy dependency of the creation of documentation. Lack of flexibility The project is outdated by the time of delivery.
  • 13. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Manifesto for Agile Software Development (February 13 th , 2001)
  • 14. Ad-hoc and Waterfall approaches to project are not very effective Change happens so fast in business that you need a faster, better and leaner approach to your projects. Agile helps you complete projects to meet the above challenges.
  • 15. The Who, What, When and Where of Agile project mangement
  • 16. A collection of features and requirements you need to complete the project. The Scrum Process Sprints to transform features and requirements into product Rapid iterations. Cyclical in nature.
  • 17. THE PRODUCT BACKLOG Customer Feature #1 Internal Feature #1 Customer Feature #2 Bug fix #1 Internal Feature #2 Internal Feature#3 Customer Feature #3 The wish list of what people want done. THE SPRINT BACKLOG Bug Fix #1 Customer Feature #1 Customer Feature #2 Customer Feature #3 The list of tasks agreed to be completed during the next sprint.
  • 18. This is where the work gets done At the start of each working day there is a Scrum meeting to update the team on the sprint. Sprints can be as short as a week and as long as four weeks. Shippable product must be provided at the end of the sprint. Each Sprint is called an iteration.
  • 19. The scrum master is the project leader and person who works with IT professionals each day. They keep the project on track, on budget, and with high quality. They should be good with people and have a solid grounding in technology. The Product Owner works with the Scrum Master. They understand the business and customers who use the product. They should be experienced pros who can take vague requirements and turn them into a concrete to do list.
  • 20. The pigs on the project are the ones who make it a reality. They are the ones who are committed and have the most to loose if the project fails. These are your IT professionals. The Chickens are the ones involved with the project. They don’t have as much invested and their career is not as impacted by project failure. These people can affect the project in both positive and negative ways. These are sales people, marketing professionals, accounting types, and the legal department
  • 21.  
  • 22.  
  • 23. Should start in the IT department for small projects Expand to bigger projects Move to other aspects of the business The entire enterprise should be adopting agile principles.
  • 24. Get started right away. Set small achievable goals and deadlines and meet them. Soon no project is too big for this approach. When eating an elephant you start one bite at a time. -Creighton Abrams
  • 25. Exercise #3 do a project with an agile approach. Exercise #4 how do you think your business is going to change using this approach.
  • 26. Things you need to do to make agile work in your business.
  • 27. Commitment Openness Focus Respect Courage
  • 28. These values must be agreed upon and out in the open. Everyone should practice these virtues and not tolerate those who don’t You must spend more time screening employees to make sure they practice these values. Average is just not good enough.
  • 29. Why is all this necessary?
  • 30. IBM uses it to develop software Fits seamlessly with lean management approaches to business. Software project success rate with Agile is 83% compared with the 24% compared to the chaos study. Scott Ambler July 2008
  • 31. No cost to the firm More responsive to changes in the business climate Better customer service A process that both IT professionals support and business leaders can understand.
  • 32.  

Editor's Notes

  • #3: People talk about projects all the time but before we begin we really need a few definitions of what projects are and are not.
  • #4: Have you had a conversation like this.
  • #6: Who fill the roles of Chickens and Pigs in your office. Can you understand their different approaches to projects. IT people are usually your pigs.
  • #7: Discuss the project pyramid, scope, schedule, Resources.
  • #10: The is how we deal with structural ambiguity.
  • #12: Now you know why it is called waterfall. The further down you go the more expensive changes become.
  • #19: Remember a sprint is not a hamster wheel. Their must be downtimes between sprints and their must be meetings to follow up on lessons learned after each sprint.
  • #20: Remember in Managing geeks this is how you deal with task ambiguity.
  • #21: These are not stereotypes but roles which govern how the project is completed.
  • #22: Remember the product backlog is created by the users, the sprint backlog is agreed upon by the product owner, scrum master and team, the sprints are performed by your chickens and pigs, the product is for your customers. Managers set priorities technologists set timelines and each must be respected by the other side.
  • #23: Each scrum should have each person ask the following questions: What did you do yesterday? What are you going to work on today? Are their any risks preventing you from getting your job done today?