Agile Presentation To IIBA MInneapolis

1,340 views
1,204 views

Published on

Published in: Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,340
On SlideShare
0
From Embeds
0
Number of Embeds
21
Actions
Shares
0
Downloads
80
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide









  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazinf that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazing that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazing that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazing that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazing that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazing that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • It is amazing that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazing that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazing that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • It is amazing that we are ever able to deliver a product that suits a customers’ needs when we deliver it.
    It is amazing that we ever have a happy customer.
    You all have a very tough job. But our efforts would not be successful without your thoughtful and insightful input in this process.
  • Agile is not a methodology, it is a framework. It does not provide a checklist, it is not a step by step process, Agile does not allow you the luxury of relieving yourself of the responsibility to think about your project, your team, your product, and your customer.
  • Agile is not a methodology, it is a framework. It does not provide a checklist, it is not a step by step process, Agile does not allow you the luxury of relieving yourself of the responsibility to think about your project, your team, your product, and your customer.
  • Agile is not a methodology, it is a framework. It does not provide a checklist, it is not a step by step process, Agile does not allow you the luxury of relieving yourself of the responsibility to think about your project, your team, your product, and your customer.
  • Agile is not a methodology, it is a framework. It does not provide a checklist, it is not a step by step process, Agile does not allow you the luxury of relieving yourself of the responsibility to think about your project, your team, your product, and your customer.


































  • The BA assists the customer is soliciting which features of the product are going to produce value for them.

    The customer defines quality, and this definition can change with greater exposure to the product and as market conditions change. Our goal is to create software for our customer’s competitive advantage.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.

    The customer defines quality, and this definition can change with greater exposure to the product and as market conditions change. Our goal is to create software for our customer’s competitive advantage.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.

    The customer defines quality, and this definition can change with greater exposure to the product and as market conditions change. Our goal is to create software for our customer’s competitive advantage.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • The BA assists the customer is soliciting which features of the product are going to produce value for them.
  • Agile Presentation To IIBA MInneapolis

    1. 1. The Agile BA Understanding the BA Role on an Agile Project Presented by Bill Gaiennie, Davisbase Consulting
    2. 2. Introduction and Agenda
    3. 3. Introduction and Agenda • Bill Gaiennie, DavisBase Consulting – 15 years in software development – 4 years working with software development teams, training, leading, and coaching Agile teams. Agenda
    4. 4. Introduction and Agenda • Bill Gaiennie, DavisBase Consulting – 15 years in software development – 4 years working with software development teams, training, leading, and coaching Agile teams. Agenda • A Brief Overview of Agile
    5. 5. Introduction and Agenda • Bill Gaiennie, DavisBase Consulting – 15 years in software development – 4 years working with software development teams, training, leading, and coaching Agile teams. Agenda • A Brief Overview of Agile • The Role of a Business Analyst on a Project
    6. 6. Introduction and Agenda • Bill Gaiennie, DavisBase Consulting – 15 years in software development – 4 years working with software development teams, training, leading, and coaching Agile teams. Agenda • A Brief Overview of Agile • The Role of a Business Analyst on a Project • The Role of a Business Analyst on an Agile Project
    7. 7. Introduction and Agenda • Bill Gaiennie, DavisBase Consulting – 15 years in software development – 4 years working with software development teams, training, leading, and coaching Agile teams. Agenda • A Brief Overview of Agile • The Role of a Business Analyst on a Project • The Role of a Business Analyst on an Agile Project • Why Business Analysts Are Vital to Successful Projects
    8. 8. Introduction and Agenda • Bill Gaiennie, DavisBase Consulting – 15 years in software development – 4 years working with software development teams, training, leading, and coaching Agile teams. Agenda • A Brief Overview of Agile • The Role of a Business Analyst on a Project • The Role of a Business Analyst on an Agile Project • Why Business Analysts Are Vital to Successful Projects • Wrap-up and Q&A
    9. 9. Building a Tire Swing
    10. 10. Building a Tire Swing How the customer described what they wanted...
    11. 11. Building a Tire Swing
    12. 12. Building a Tire Swing
    13. 13. Building a Tire Swing How the project manager understood it...
    14. 14. Building a Tire Swing
    15. 15. Building a Tire Swing
    16. 16. Building a Tire Swing How the architect designed it...
    17. 17. Building a Tire Swing
    18. 18. Building a Tire Swing
    19. 19. Building a Tire Swing How the programmer wrote it...
    20. 20. Building a Tire Swing
    21. 21. Building a Tire Swing
    22. 22. Building a Tire Swing How the business consultant described it...
    23. 23. Building a Tire Swing
    24. 24. Building a Tire Swing
    25. 25. Building a Tire Swing How the the project was documented...
    26. 26. Building a Tire Swing
    27. 27. Building a Tire Swing
    28. 28. Building a Tire Swing What operations installed...
    29. 29. Building a Tire Swing
    30. 30. Building a Tire Swing
    31. 31. Building a Tire Swing How the customer was billed...
    32. 32. Building a Tire Swing
    33. 33. Building a Tire Swing
    34. 34. Building a Tire Swing How it was supported...
    35. 35. Building a Tire Swing
    36. 36. Building a Tire Swing
    37. 37. Building a Tire Swing What the customer really needed...
    38. 38. Building a Tire Swing What the customer really needed...
    39. 39. Building a Tire Swing
    40. 40. Developing Software is Tough!
    41. 41. Developing Software is Tough! • We are building something that doesn’t exist.
    42. 42. Developing Software is Tough! • We are building something that doesn’t exist. • Our customer is attempting to describe what they imagine this non-existent product should be.
    43. 43. Developing Software is Tough! • We are building something that doesn’t exist. • Our customer is attempting to describe what they imagine this non-existent product should be. • We then try to imagine what they are describing.
    44. 44. Developing Software is Tough! • We are building something that doesn’t exist. • Our customer is attempting to describe what they imagine this non-existent product should be. • We then try to imagine what they are describing. • We then try to build the product we believe we heard them describe.
    45. 45. Developing Software is Tough! • We are building something that doesn’t exist. • Our customer is attempting to describe what they imagine this non-existent product should be. • We then try to imagine what they are describing. • We then try to build the product we believe we heard them describe. • And finally, the first opportunity we have to really see if we built a product that they need and want is after we are done with development.
    46. 46. Pop Quiz: Waterfall Requirements Analysis
    47. 47. Pop Quiz: Waterfall Requirements Analysis What percentage of overall project time is spent gathering, elaborating, and communicating product requirements?
    48. 48. Pop Quiz: Waterfall Requirements Analysis What percentage of overall project time is 50% spent gathering, elaborating, and communicating product requirements?
    49. 49. Pop Quiz: Waterfall Requirements Analysis What percentage of overall project time is 50% spent gathering, elaborating, and communicating product requirements? What percentage of requirements, as originally defined, change during the course of the project?
    50. 50. Pop Quiz: Waterfall Requirements Analysis What percentage of overall project time is 50% spent gathering, elaborating, and communicating product requirements? What percentage of requirements, as 35% originally defined, change during the course of the project?
    51. 51. Pop Quiz: Waterfall Requirements Analysis What percentage of overall project time is 50% spent gathering, elaborating, and communicating product requirements? What percentage of requirements, as 35% originally defined, change during the course of the project? What percentage of features, as ultimately delivered, are rarely or never used by the product’s end-users?
    52. 52. Pop Quiz: Waterfall Requirements Analysis What percentage of overall project time is 50% spent gathering, elaborating, and communicating product requirements? What percentage of requirements, as 35% originally defined, change during the course of the project? What percentage of features, as ultimately 65% delivered, are rarely or never used by the product’s end-users?
    53. 53. Developing Software Is TOUGH!
    54. 54. What is Agile All About?
    55. 55. What is Agile All About? • A philosophy about software development.
    56. 56. What is Agile All About? • A philosophy about software development. • A collection of processes and practices that uphold this philosophy.
    57. 57. What is Agile All About? • A philosophy about software development. • A collection of processes and practices that uphold this philosophy. • A grassroots movement to fundamentally change the approach to software development.
    58. 58. What is Agile All About? • A philosophy about software development. • A collection of processes and practices that uphold this philosophy. • A grassroots movement to fundamentally change the approach to software development. “Agility is more attitude than process, more environment than methodology.”
    59. 59. The Agile Manifesto
    60. 60. The Agile Manifesto Individuals and interactions, over processes and tools.
    61. 61. The Agile Manifesto Individuals and interactions, over processes and tools. Working software, over comprehensive documentation.
    62. 62. The Agile Manifesto Individuals and interactions, over processes and tools. Working software, over comprehensive documentation. Customer collaboration, over contract negotiation.
    63. 63. The Agile Manifesto Individuals and interactions, over processes and tools. Working software, over comprehensive documentation. Customer collaboration, over contract negotiation. Responding to change, over following a plan.
    64. 64. The Agile Manifesto 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 simply value the items on the left more.
    65. 65. Companies are Adopting Agile Source: Dr. Dobb’s Agile Survey, 2008
    66. 66. Companies are Adopting Agile • Agile adoption has increased in the last several years across the globe. Source: Dr. Dobb’s Agile Survey, 2008
    67. 67. Companies are Adopting Agile • Agile adoption has increased in the last several years across the globe. • Recent data suggests 69% of companies have adopted an Agile approach in some form. Source: Dr. Dobb’s Agile Survey, 2008
    68. 68. Companies are Adopting Agile • Agile adoption has increased in the last several years across the globe. • Recent data suggests 69% of companies have adopted an Agile approach in some form. • Respondents to a recent survey shared improvements in the following areas after adopting an Agile development approach: Source: Dr. Dobb’s Agile Survey, 2008
    69. 69. Companies are Adopting Agile • Agile adoption has increased in the last several years across the globe. • Recent data suggests 69% of companies have adopted an Agile approach in some form. • Respondents to a recent survey shared improvements in the following areas after adopting an Agile development approach: – Productivity (82%) – Product Quality (77%) – Stakeholder Satisfaction (78%) – Reduced Costs (37%) Source: Dr. Dobb’s Agile Survey, 2008
    70. 70. Why We Develop Software
    71. 71. Why We Develop Software • We develop software for our customers’ benefit.
    72. 72. Why We Develop Software • We develop software for our customers’ benefit. • Change can be good. Change is usually the result of new information and learning.
    73. 73. Why We Develop Software • We develop software for our customers’ benefit. • Change can be good. Change is usually the result of new information and learning. • The software we develop does not create value for our customer at ‘point of plan’.
    74. 74. Why We Develop Software • We develop software for our customers’ benefit. • Change can be good. Change is usually the result of new information and learning. • The software we develop does not create value for our customer at ‘point of plan’. • An Agile approach may require us to be comfortable with the traditionally uncomfortable.
    75. 75. The BA’s Role on a Project
    76. 76. The BA’s Role on a Project BABOK identifies the following:
    77. 77. The BA’s Role on a Project BABOK identifies the following: • Enterprise Analysis • Requirements Planning and Management • Requirements Elicitation • Requirements Analysis and Documentation • Requirements Communication • Solution Assessment and Validation
    78. 78. The BA’s Role on an Agile Project
    79. 79. The BA’s Role on an Agile Project • Enterprise Analysis • Requirements Planning and Management • Requirements Elicitation • Requirements Analysis and Documentation • Requirements Communication • Solution Assessment and Validation
    80. 80. Agile: Enterprise Analysis
    81. 81. Agile: Enterprise Analysis • Work with the customer to develop strategic goals and a product vision.
    82. 82. Agile: Enterprise Analysis • Work with the customer to develop strategic goals and a product vision. • Identifying the “value stream” for the proposed product.
    83. 83. Agile: Enterprise Analysis • Work with the customer to develop strategic goals and a product vision. • Identifying the “value stream” for the proposed product. • Brokering effective information exchange between the customer and the IT team.
    84. 84. Agile: Enterprise Analysis • Work with the customer to develop strategic goals and a product vision. • Identifying the “value stream” for the proposed product. • Brokering effective information exchange between the customer and the IT team. • The correct scope for Agile projects isn’t defined requirements, but the well articulated product vision.
    85. 85. Agile: Enterprise Analysis
    86. 86. Agile: Enterprise Analysis “Quality in a product or service is not what the supplier puts in. It is what the customer gets out and is willing to pay for. A product is not quality because it is hard to make and costs a lot of money, as manufacturers typically believe. This is incompetence. Customers pay only for what is of use to them and gives them value. Nothing else constitutes quality.”
    87. 87. Agile: Enterprise Analysis “Quality in a product or service is not what the supplier puts in. It is what the customer gets out and is willing to pay for. A product is not quality because it is hard to make and costs a lot of money, as manufacturers typically believe. This is incompetence. Customers pay only for what is of use to them and gives them value. Nothing else constitutes quality.” - Peter Drucker
    88. 88. Agile: Enterprise Analysis “Quality in a product or service is not what the supplier puts in. It is what the customer gets out and is willing to pay for. A product is not quality because it is hard to make and costs a lot of money, as manufacturers typically believe. This is incompetence. Customers pay only for what is of use to them and gives them value. Nothing else constitutes quality.” - Peter Drucker Simply stated, the customer defines quality.
    89. 89. Agile: Requirements Planning
    90. 90. Agile: Requirements Planning • Requirements evolve with greater product exposure.
    91. 91. Agile: Requirements Planning • Requirements evolve with greater product exposure. • A lean principle: just enough, just in time.
    92. 92. Agile: Requirements Planning • Requirements evolve with greater product exposure. • A lean principle: just enough, just in time. • Requirements are planned for delivery in time-boxed iterations.
    93. 93. Agile: Requirements Planning • Requirements evolve with greater product exposure. • A lean principle: just enough, just in time. • Requirements are planned for delivery in time-boxed iterations. • The development team creates and commits to a definition of “done”.
    94. 94. Agile: Requirements Planning • Requirements evolve with greater product exposure. • A lean principle: just enough, just in time. • Requirements are planned for delivery in time-boxed iterations. • The development team creates and commits to a definition of “done”. • BA’s help to negotiate standards and the specifics of product requirements.
    95. 95. Agile: Analysis & Documentation
    96. 96. Agile: Analysis & Documentation • Understanding the customer’s needs is essential.
    97. 97. Agile: Analysis & Documentation • Understanding the customer’s needs is essential. • Who are your customers?
    98. 98. Agile: Analysis & Documentation • Understanding the customer’s needs is essential. • Who are your customers? • How will your customer use your product?
    99. 99. Agile: Analysis & Documentation • Understanding the customer’s needs is essential. • Who are your customers? • How will your customer use your product? • What are your customers priorities?
    100. 100. Agile: Analysis & Documentation • Understanding the customer’s needs is essential. • Who are your customers? • How will your customer use your product? • What are your customers priorities? • User Stories capture requirements using the following form:
    101. 101. Agile: Analysis & Documentation • Understanding the customer’s needs is essential. • Who are your customers? • How will your customer use your product? • What are your customers priorities? • User Stories capture requirements using the following form: As a <user>, I want <product requirement>,
    102. 102. Agile: Analysis & Documentation • Understanding the customer’s needs is essential. • Who are your customers? • How will your customer use your product? • What are your customers priorities? • User Stories capture requirements using the following form: As a <user>, I want <product requirement>, so that <desired benefit>.
    103. 103. Agile: Analysis & Documentation
    104. 104. Agile: Analysis & Documentation • Understanding “the why” can be as important as “the what”.
    105. 105. Agile: Analysis & Documentation • Understanding “the why” can be as important as “the what”. As an speaker, I want to make my presentation available to attendees online, so that I do not need to send it.
    106. 106. Agile: Analysis & Documentation • Understanding “the why” can be as important as “the what”. As an speaker, I want to As an attendee, I want make my presentation to download the available to attendees presentation, so that online, so that I do not I share what I have need to send it. learned.
    107. 107. Agile: Analysis & Documentation • Understanding “the why” can be as important as “the what”. As an speaker, I want to As an attendee, I want make my presentation to download the available to attendees presentation, so that online, so that I do not I share what I have need to send it. learned. • Information gems exist in knowing why our customers want what they ask for.
    108. 108. Agile: Requirements Communication
    109. 109. Agile: Requirements Communication • The best method of conveying project progress.
    110. 110. Agile: Requirements Communication • The best method of conveying project progress. • Building a better customer/IT relationship.
    111. 111. Agile: Requirements Communication • The best method of conveying project progress. • Building a better customer/IT relationship. • Emergent requirements.
    112. 112. Agile: Requirements Communication • The best method of conveying project progress. • Building a better customer/IT relationship. • Emergent requirements. • The product backlog.
    113. 113. Agile: Requirements Communication • The best method of conveying project progress. • Building a better customer/IT relationship. • Emergent requirements. • The product backlog. • Burndown charts can help drive better project decisions.
    114. 114. Agile: Requirements Communication • The best method of conveying project progress. • Building a better customer/IT relationship. • Emergent requirements. • The product backlog. • Burndown charts can help drive better project decisions. • Taskboards can visually radiate project progress.
    115. 115. Agile: Requirements Communication • The best method of conveying project progress. • Building a better customer/IT relationship. • Emergent requirements. • The product backlog. • Burndown charts can help drive better project decisions. • Taskboards can visually radiate project progress. • Project documentation.
    116. 116. Agile: Assessment & Validation
    117. 117. Agile: Assessment & Validation • Delivering the solution in small bites.
    118. 118. Agile: Assessment & Validation • Delivering the solution in small bites. • Reviewing requirements during planning.
    119. 119. Agile: Assessment & Validation • Delivering the solution in small bites. • Reviewing requirements during planning. • Reviewing requirements during demo.
    120. 120. Agile: Assessment & Validation • Delivering the solution in small bites. • Reviewing requirements during planning. • Reviewing requirements during demo. • Requirements describe solution to business needs.
    121. 121. Agile: Assessment & Validation • Delivering the solution in small bites. • Reviewing requirements during planning. • Reviewing requirements during demo. • Requirements describe solution to business needs. • Determining requirements as late as possible.
    122. 122. Agile: Assessment & Validation • Delivering the solution in small bites. • Reviewing requirements during planning. • Reviewing requirements during demo. • Requirements describe solution to business needs. • Determining requirements as late as possible. • Validating requirements through prioritizing delivery.
    123. 123. Business Analysts Are Crucial To Agile Project Success
    124. 124. Business Analysts Are Crucial To Agile Project Success • Great products and happy customers begin and end with pliable requirements.
    125. 125. Business Analysts Are Crucial To Agile Project Success • Great products and happy customers begin and end with pliable requirements. • Change happens, how do we embrace it?
    126. 126. Business Analysts Are Crucial To Agile Project Success • Great products and happy customers begin and end with pliable requirements. • Change happens, how do we embrace it? • Expanding our toolkit, redefining nails as opportunities.
    127. 127. Business Analysts Are Crucial To Agile Project Success • Great products and happy customers begin and end with pliable requirements. • Change happens, how do we embrace it? • Expanding our toolkit, redefining nails as opportunities. • Continuous planning recognizes that change can be good.
    128. 128. Wrap-Up
    129. 129. Wrap-Up • Great BA’s assist the customer is defining the best possible product, a standard consistently examined during the entire project.
    130. 130. Wrap-Up • Great BA’s assist the customer is defining the best possible product, a standard consistently examined during the entire project. • Great products emerge from designs that evolve as a result of information made available to the customer and project team.
    131. 131. Wrap-Up • Great BA’s assist the customer is defining the best possible product, a standard consistently examined during the entire project. • Great products emerge from designs that evolve as a result of information made available to the customer and project team. • Great project teams promote open and honest communication, and utilize this information to tune their behavior.
    132. 132. Questions and Answers • Previously submitted. • From the attendees.
    133. 133. Meeting Close • Thank you. • Bill Gaiennie, Davisbase Consulting • bill@davisbase.org • http://www.davisbase.org • (949) 303-9109

    ×