This is a 45 minute presentation I will be delivering at a company-wide meeting to discuss:
* How push-button release was used to help entire enterprise go from 6 month to 1 week release cycles
* How a "No Defect" team policy with ATDD drives greater productivity
Integrating Quality into Project Portfolio ManagementChris Sterling
Traditionally, projects are managed based on cost, schedule, and scope. This continues to be insufficient and leads to poor outcomes, unsustainable development efforts, quality issues, and software that may meet requirements but not the expectations of users. This talk will go into how organizations can integrate quality and value considerations into their portfolio management strategies leading to less surprises and more valuable outcomes. The talk will go into detail about how Agile, Lean thinking, and Managing Software Debt can give a more holistic view of the project portfolio.
This presentation is from Scrum Gathering 2011 in Seattle, WA, USA. Much of the presentation involved showing tools and techniques outside the slide deck along with exercises that the participants would perform for learning purposes.
This is a 45 minute presentation I will be delivering at a company-wide meeting to discuss:
* How push-button release was used to help entire enterprise go from 6 month to 1 week release cycles
* How a "No Defect" team policy with ATDD drives greater productivity
Integrating Quality into Project Portfolio ManagementChris Sterling
Traditionally, projects are managed based on cost, schedule, and scope. This continues to be insufficient and leads to poor outcomes, unsustainable development efforts, quality issues, and software that may meet requirements but not the expectations of users. This talk will go into how organizations can integrate quality and value considerations into their portfolio management strategies leading to less surprises and more valuable outcomes. The talk will go into detail about how Agile, Lean thinking, and Managing Software Debt can give a more holistic view of the project portfolio.
This presentation is from Scrum Gathering 2011 in Seattle, WA, USA. Much of the presentation involved showing tools and techniques outside the slide deck along with exercises that the participants would perform for learning purposes.
Earned Value Management and Agile Tips for Success Brent Barton
As the Department of Defense focuses on "delivering 75% solutions in months [instead of] 100% solutions in years" Agile is finding its way into big, traditionally managed programs. This event http://www.afei.org/events/2A01/Pages/default.aspx specifically addresses Agile in Defense. This presentation was an invitation following a successful meeting at the ADAPT meeting.
Secrets of a Scrum Master! Agile Practices for the Service DeskITSM Academy, Inc.
Can agile concepts be applied to the service desk? Absolutely! This session describes the benefits of agile practices and provides a brief introduction to Scrum – an agile way to handle complex projects. The session focuses on specific ways that Scrum and other agile practices can be used to significantly increase the performance of service and support teams. Takeaway tips and techniques you can use to get started immediately, along with lessons learned.
Expectations from IT Team
Project Methodology - Why it is as important as the Technology for your Product
Gaps in Recent Graduates
How to bridge these gaps?
2011 pmo symposium Bridging the Agile-to-PMO Communication GapBrent Barton
Traditional EVM makes no sense in software (and is potentially harmful) because claiming value earned based on intermediate work products--without an assertion of quality--does not provide reasonable forecasts. Agile provides an assertable and inspectable quality. Also, by ordering in terms of highest Business Value and risk considerations along with potentially shippable increments, I believe starts to include notions of value. Still, AgileEVM measures performance against plans (that can be re-baselined every iteration if needed). AgileEVM integrates cost management. Doing it well means not giving up what Agile offers: adaptive planning, quality.
A presentation I did for the Agile Profesionals Network (APN) Wellington branch. Even if we have a recipe the context of the situation can mean we can\’t replicate a successful dish in a different environment. The key are Principles. Know your system, know your customer and desired output. Like a good chef have practices but understand the base principles of why things work.
Hundreds of organizations have now realized the benefit of Rapid Release Planning! Compared to traditional release planning, this increases your estimation and sizing accuracy from 34% to over 85%! Rapid Release Planning is one of the CORE Components for getting teams engaged early and using their Rapid Sizing to better forecast which candidates will successfully be a part of the release. The keys to making this work successfully revolve around making gut decisions about size and relative complexity of the items being estimated and validated.
Facilitation Foundations - A Guide to Effective Agile MeetingsAgileDad
Facilitation Foundations is a presentation that has been given at multiple Agile Conferences. The focus of the presentation is improving the quality and effectiveness of Agile Meetings.
Many who have downloaded this deck have made it a standard for assisting organizations who are struggling with spending too much time and money on Agile Meetings.
The Empowering Agile Teams Presentation has been presented at numerous Agile Conferences and has been VERY well received. Many teams get frustrated due to the lack of understanding of what they are expected to deliver vs what has been perceived. Gone are the days of opacity. Teams are better equipped to handle the day to day workload and are less fearful of commitment in an environment where healthy team relationships are valued.
Integrating Quality into Portfolio Management Brent Barton
Traditionally, projects are managed based on cost, schedule, and scope. This has lead to poor outcomes, unsustainable development efforts, quality issues, and less than ideal software in terms of value to its users. Our talk will go into how organizations can integrate quality and value considerations into their portfolio management strategies to have a more holistic view leading to less surprises and more valuable outcomes. The talk will go into detail about how Agile plus traditional Earned Value Management (EVM) alongside Managing Software Debt can give a more holistic view of the project portfolio.
Earned Value Management and Agile Tips for Success Brent Barton
As the Department of Defense focuses on "delivering 75% solutions in months [instead of] 100% solutions in years" Agile is finding its way into big, traditionally managed programs. This event http://www.afei.org/events/2A01/Pages/default.aspx specifically addresses Agile in Defense. This presentation was an invitation following a successful meeting at the ADAPT meeting.
Secrets of a Scrum Master! Agile Practices for the Service DeskITSM Academy, Inc.
Can agile concepts be applied to the service desk? Absolutely! This session describes the benefits of agile practices and provides a brief introduction to Scrum – an agile way to handle complex projects. The session focuses on specific ways that Scrum and other agile practices can be used to significantly increase the performance of service and support teams. Takeaway tips and techniques you can use to get started immediately, along with lessons learned.
Expectations from IT Team
Project Methodology - Why it is as important as the Technology for your Product
Gaps in Recent Graduates
How to bridge these gaps?
2011 pmo symposium Bridging the Agile-to-PMO Communication GapBrent Barton
Traditional EVM makes no sense in software (and is potentially harmful) because claiming value earned based on intermediate work products--without an assertion of quality--does not provide reasonable forecasts. Agile provides an assertable and inspectable quality. Also, by ordering in terms of highest Business Value and risk considerations along with potentially shippable increments, I believe starts to include notions of value. Still, AgileEVM measures performance against plans (that can be re-baselined every iteration if needed). AgileEVM integrates cost management. Doing it well means not giving up what Agile offers: adaptive planning, quality.
A presentation I did for the Agile Profesionals Network (APN) Wellington branch. Even if we have a recipe the context of the situation can mean we can\’t replicate a successful dish in a different environment. The key are Principles. Know your system, know your customer and desired output. Like a good chef have practices but understand the base principles of why things work.
Hundreds of organizations have now realized the benefit of Rapid Release Planning! Compared to traditional release planning, this increases your estimation and sizing accuracy from 34% to over 85%! Rapid Release Planning is one of the CORE Components for getting teams engaged early and using their Rapid Sizing to better forecast which candidates will successfully be a part of the release. The keys to making this work successfully revolve around making gut decisions about size and relative complexity of the items being estimated and validated.
Facilitation Foundations - A Guide to Effective Agile MeetingsAgileDad
Facilitation Foundations is a presentation that has been given at multiple Agile Conferences. The focus of the presentation is improving the quality and effectiveness of Agile Meetings.
Many who have downloaded this deck have made it a standard for assisting organizations who are struggling with spending too much time and money on Agile Meetings.
The Empowering Agile Teams Presentation has been presented at numerous Agile Conferences and has been VERY well received. Many teams get frustrated due to the lack of understanding of what they are expected to deliver vs what has been perceived. Gone are the days of opacity. Teams are better equipped to handle the day to day workload and are less fearful of commitment in an environment where healthy team relationships are valued.
Integrating Quality into Portfolio Management Brent Barton
Traditionally, projects are managed based on cost, schedule, and scope. This has lead to poor outcomes, unsustainable development efforts, quality issues, and less than ideal software in terms of value to its users. Our talk will go into how organizations can integrate quality and value considerations into their portfolio management strategies to have a more holistic view leading to less surprises and more valuable outcomes. The talk will go into detail about how Agile plus traditional Earned Value Management (EVM) alongside Managing Software Debt can give a more holistic view of the project portfolio.
Agile development poses several challenges to effectively testing software. Many myths have become "common wisdom" about how testing is much more difficult, even impossible, in an agile environment. Aricent's software testing experts look at 7 of these myths, and based on their years of experience debunk them.
Continuous Testing: A Key to DevOps SuccessTechWell
As IT organizations adopt a DevOps strategy, continuous testing (CT) becomes a key ingredient of the DevOps ecosystem. CT enables faster release cycles, more changes per release, upfront isolation of risks, and reduced operations costs. The approach to scale the traditional automation testing infrastructure, test environments, and test data management requires a culture shift using new tools and techniques. Sujay Honnamane discusses a CT strategy for aspiring and already implemented DevOps organizations. Sujay shares examples of tools, techniques, and practical solutions that include continuous integration using the Jenkins CI server, service virtualization through CA Lisa tools, automated code coverage analysis to create impact-based tests, automated test script load balancing for effective use of test environments, and faster test cycles, providing a holistic approach/workflow for CT. Sujay and his teams have successfully implemented CT for several clients in their DevOps journey to achieve a repeatable and highly predictable software delivery process.
This is a presentation made to Surge Accelerator in Houston in March 2013. This serves as a Guide to Early Stage Technology Companies, building enterprise class software.
This covers the typical lifecycle of a software start-up, fundamentals of Agile software development, and some do's and don't for how to build successful software companies.
More and more companies worldwide are excited about DevOps and the many potential benefits of embarking on a DevOps transformation. The challenge many of them are having, however, is figuring out where to begin and how to scale DevOps practices over time. These challenges can be especially daunting in large enterprises. In this webinar we will discuss a maturity model for framing your transformation, then focus on analyzing your deployment pipeline and identify existing inefficiencies in software development and deployment.
More and more companies worldwide are excited about DevOps and the many potential benefits of embarking on a DevOps transformation. The challenge many of them are having, however, is figuring out where to begin and how to scale DevOps practices over time. These challenges can be especially daunting in large enterprises. In this webinar we will discuss a maturity model for framing your transformation, then focus on analyzing your deployment pipeline and identify existing inefficiencies in software development and deployment.
Presentation used at the CollabNet Dallas CI/CD/DevOps highly practical and interactive workshop which was designed to address specific challenges, opportunities and specific recommendations on how to scale CI, CD and DevOps across the enterprise to support decision making.
Now that you've sold it how do you build it - XMPie Users Conference XUG 202...Jeffrey Stewart
Hello, I’m Jeff Stewart, XMPie Services Director
Today I will present the new service offering from XMPie started last year.
The motivation is to help customers succeed using the XMPie suite of platforms and tools
We Can Help You Get Started Fast, Do It Well The First Time, Learn While We Build It Together
Key takeaways
- Continuous “everything” is at the heart of agile and devops
- Continuous activities result in faster delivery and higher quality
- Rapid feedback and practice are essential for confidence in your delivery process
View webinar recording - http://testhuddle.com/resource/continuous-everything/
Agile has become mainstream in the IT industry, since that the multiplication of Agile practices which makes Agile implementation complex and uncertain, we have started to see failure in Agile implementations.
During this presentation we will start a simplification process by going back to the source of Agile, understand what Agile is and what it is not. We will discover what is the Heart of Agile, its essence, and how it embraces management.
Reference: Agile Manifesto, Heart of Agile blogs Alistair Cockburn, plus historical information about Agile mouvement
Is agility really possible when people are thousands of miles apart from each other? Yes! In this talk, Pete Deemer shared tips and techniques gleaned from nearly a decade of working with distributed Scrum teams in Asia.
From Continuous Integration to DevOps - Japan Innovate 2013Sanjeev Sharma
Presentation on the history of evolution of DevOps from CI. Delivered at Innovate Japan 2013. Hat Tip to Eric Minick who presented earlier version at Innovate 2013 in Orlando, FL
Japanese ver available here: http://www.slideshare.net/sanjeev-sharma/from-continuous-integration-to-dev-ops-japan-innovate-2013-japanese
Similar to Utah PMA Quarterly Meeting, June, 2009 (20)
2. Introduction
• Bryan Tew of DavisBase Consulting
• Agile Trainer and Coach
• 10+ years in software development industry
• IT Roles include PMO Director, Project Manager, Program Manager,
Business Analyst, Process Manager
• Novell, The Generations Network, Solution Stream, ASPE
• 4+ years implementing Agile practices with software development
teams and IT organizations
• MBA, Certified Scrum Master & Practitioner
Copyright 2009 Davisbase LLC
3. Objectives
• Understand the differences and benefits of
Agile development
• Provide knowledge and understanding of
Agile principles and practices
• Understand the role of the Product Owner
and how to work with an Agile team
• Learn how you can help your teams get
started
Copyright 2009 Davisbase LLC
4. Traditional Development
• Waterfall uses the ‘Big Bang’ approach:
The product
is delivered
At the
completion
of testing
Copyright 2009 Davisbase LLC
5. The Triple Constraint
Schedule Cost
Timetable for creating the People, materials, and
deliverables equipment used to create
the deliverables
Scope
Feature/functionality
deliverables for the project
Copyright 2009 Davisbase LLC
6. What is Agile?
• A philosophy about software development
• A collection of processes and practices that
uphold that philosophy
• A grassroots movement to revolutionize
software development
• What is the problem we’re trying to solve?
Copyright 2009 Davisbase LLC
7. The Agile Advantage
• With incremental delivery:
– We address the greatest risks early in the
project
– We can make corrections/adjustments with
each iteration
– The Product Owner sees the product emerge
before their eyes and has visibly helped to
create it
– The team incrementally improves with each
iteration
Copyright 2009 Davisbase LLC
8. Waterfall vs Agile
Target
Waterfall/’Big Bang’
Agile
Time
• Waterfall can lead to a large gap
between what the Product Owner
wants and what is actually delivered
• Agility adjusts to the goal based on
customer feedback with each iteration.
- 0 +
Variance from Target
Copyright 2009 Davisbase LLC
9. Why Agile?
1. Manage rapidly
changing priorities
2. Accelerate time to
market
3. Increase
Productivity
4. Improve Quality
VersionOne/AgileAlliance Survey, August 2006
Copyright 2009 Davisbase LLC
11. Paradigm Shift
Features Fixed___ Date Cost
Agile
Traditional
Date Cost Flexible Features
Copyright 2009 Davisbase LLC
12. Agile Manifesto
We are uncovering better ways of developing software by doing it and
helping others do it. Through this work we have come to value:
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.
http://agilemanifesto.org/
Copyright 2009 Davisbase LLC
13. Agile Fundamentals:
Working Software = Customer Satisfaction
• Working software is the primary measure of progress
• Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software
• Deliver working software frequently, from a couple of weeks to a
couple of months, with a preference to the shorter timescale
Q: When you go to a car
Q: When you need a CRM
dealership to buy a car,
system for your business,
does the dealer:
1. Show you a blueprint of
does IT:
1. Show you a set of wireframes
the car?
representing the software?
2. Put you in the make and
2. Develop some functionality so
model of the car so that
you can try it out?
you can take it for a test
drive?
Copyright 2009 Davisbase LLC
14. Agile Fundamentals:
Adaptability & Change Are Welcome
• Welcome changing requirements, even late in development.
Agile processes harness change for the customer's competitive
advantage
– ‘Plans are useless..., planning is indispensable” - Eisenhower
• The plan is only a point estimate - a moment in time
• Planning is the ongoing response to a changing reality
– Recognize that changing user needs, market conditions and
regulations will necessitate changes to the ‘plan’
– While there is a legitimate reason for changes in scope, the
notion of ‘scope creep’ has little meaning in this model
15
Copyright 2009 Davisbase LLC
15. Agile Fundamentals:
Sustainable Development
• Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace
indefinitely.
start end
– Prevents the ‘student syndrome’ on projects
80 Effort/hrs
– Sustainable, even pace of work allows for more
Hrs/week
accurate extrapolation of timeline and budget, higher 40
product quality
– Team is not consistently working in a state of
Duration
emergency or burnout:
Copyright 2009 Davisbase LLC
16. Agile Fundamentals:
Go See for Yourself
• The most efficient and effective method of conveying
information to and within a development team is face-to-face
conversation
– Do not depend on what you see:
• On a computer screen
• In an e-mail
• On an MS Gantt Chart
– Crucial conversations are best had face-to-face. Messages only realize:
• 7% of their impact via the actual words
• 38% of their impact from vocal inflection
• 55% of their impact from body language
Copyright 2009 Davisbase LLC
17. Agile Fundamentals:
Self Organizing Teams
• The best architectures, requirements, and designs emerge
from Self-Organizing Teams
– The technical team knows ‘how’ to get the job done based
upon technical expertise
– The team knows best how to organize itself to accomplish the
work
– The team obtains the ‘what’ from the customer/sponsor
"Never tell people how to do things. Tell them what to do and they will
surprise you with their ingenuity.“ – General George S. Patton Jr.
Copyright 2009 Davisbase LLC
18. Agile Fundamentals:
Collaboration is Key
• Business people and developers must work together daily
throughout the project
– “Throw it over the wall” is not a management option
– Continuous customer collaboration ensures the product
development is on track and stays on track
– Daily stand-ups with the Product Owner (or the P.O.s proxy)
will elevate project issues immediately and allow for timely
adjustments of the deliverables
Copyright 2009 Davisbase LLC
19. Process Overview
Scrum Alliance 2008
Copyright 2009 Davisbase LLC
20. Process Overview
Scrum Alliance 2008
Copyright 2009 Davisbase LLC
22. Forming the Agile Team
• Customer Unit • Developer Unit
• Product Manager • Developer
• Customer • Business Analyst
• QA
• Business Analyst
• DBA
• Marketing
• Project Manager
• Executives
• Creative/Design
• More....
• IT/IS
Copyright 2009 Davisbase LLC
23. Rock Band Analogy
#1 The Team is the rock band – people pay to attend concerts to see and listen to the band.
#2 The Product Owner(s) are the fans – those who pay to attend concerts, pay for the music
and therefore ultimately determine what music is popular and what music the band plays.
#3 The Scrum-Master is the bouncer/manager – they protect the band from over enthusiastic
fans, make sure no harm comes to them, book the gigs and make sure the band shows up on
time
Copyright 2009 Davisbase LLC
24. Product Owner Role
• Identify markets and • Create user stories
customers
• Be prepared with details at
• Define products the appropriate time
• Establish the Product • Set clear expectations for
Vision and Roadmap acceptance
• Drive and quantify • Convince Customers to
business value buy and Executives to
invest
• Prioritize and manage the
product backlog • COMMUNICATE
Copyright 2009 Davisbase LLC
26. Team Best Practices
• Start as a team, finish as a team
• Appropriate team size
• Empowerment
• Decision making pushed down to lowest level
• Come together
• Do you have the space for co-location?
• Are you available for daily collaboration?
• Open and Honest Communication
• Inspect and Adapt
Copyright 2009 Davisbase LLC
27. Communication
• Forums for communication
• Daily Standup/Scrum
• Iteration Planning
• Iteration Review/Demo
• Retrospectives
• Taskboards
• Burndown Charts
Copyright 2009 Davisbase LLC
28. How to get started with
agile ?
• Find a coach on your team or mentor outside
• Start with a project that will span at least 3 or 4
sprints
• Pick people who will give it a fair trial (skeptics
okay)
• Support it. Listen to what team and data tell
you
• Have that team coach the next
Copyright 2009 Davisbase LLC
29. Things to Remember
• Establish a cadence
• Focus on practices that add value -
eliminate waste whenever possible
• Communication - transparent and on
the main path
• Patience - don’t expect perfection
• Inspect and adapt always!
Copyright 2009 Davisbase LLC
30. DavisBase Offerings
• Agile for Product Owners
• Agile for Executives
• Agile Boot Camp
• Agile Project Management
• Agile Requirements
• Agile Essentials
• Transitioning from Waterfall to Agile
• ...Coaching Services
Copyright 2009 Davisbase LLC