Continuous
Improvement
Agile : A Preview
Sue Yeh Johnson,
Sue.Johnson@snapstreamllc.com
Alpharetta-User Group Meeting Organizer
First Meetup, Tuesday, July 28, 2015 5:45-6:45 PM
Evans Technology 3655 North Point Pkwy #600,
Alpharetta, GA 30005
CSP, CSM, CSPO and PMP
Continuous
Improvement
• 17 year veteran within the IT field
• Previous: BA, SA, QA, and PM
• Sectors: IT Telecom, Transportation, Retail and Healthcare
• Now: Agile Coach
• Passionate about all things Agile
Bio and experience
1
Continuous
Improvement
• Alpharetta-Agile User Group meetup
• Scrum Alliance Gatherings
• Agile Coach’s Circle
• Scrum Master Community of Practice
• Agile Boot Camp Training
• Private, Team & Organizational Agile Coaching
Highlights
2
Continuous
Improvement
House keeping
• Sign in and start networking
• Know the Restrooms and Exits
• Partake in Pizza and Refreshments
• Thanks to Evans Technology for the space
• Thanks to Sponsors Optomi Staffing Agency for Pizza
http://vector-magz.com/wp-content/uploads/2013/09/housekeeping-clipart.gif
3
Continuous
Improvement
• Icebreakers and Housekeeping (10 min)
• Agile Background and Overview (15 min)
• Group Exercises (10 min)
• Review and Q &A (5-10 min)
• Wrap up and ideas for next meetup (20-25min)
• Adjourn
agenda
http://www.meggin.com/wp-content/uploads/2013/07/graphic-road-sign-change-ahead.jpg
4
Continuous
Improvement
• Introduce yourself to the people close to you
• Are you practicing Agile at your work?
• If so, what are some challenges?
• What do you want to get out of this workshop?
• Give them high fives for coming here
icebreakers (5 min)
http://www.trainsmartinc.com/wp-content/uploads/2014/02/ice-breakers-for-presentations.jpg
5
Continuous
Improvement
What this workshop is not
• Not a boot camp
• Not a certification
• No quick answers
6
Continuous
Improvement
What this workshop is
• Observations from the field
• Provide an Agile coaching perspective
• Excite you to learn more about Agile
• Focus is mostly on SCRUM
7
Continuous
Improvement
https://Wordpress.tifannybrown.com
Is this agile ?
8
Continuous
Improvement
Or this?
Not the Agile what we will be talking about…
9
Continuous
Improvement
what is agile methodology?
Agile software development is a group of software
development methods in which requirements and solutions
evolve through collaboration between self-organizing,
cross-functional teams.
10
Continuous
Improvement
Decided to go agile?
• Have a Scrum Team?
• Have Product Owner and Scrum Master?
• Have a Team Room?
• Have a team trained on Agile and Business Domain?
Now What?
11
Continuous
Improvement
Start a Working Agreement
http://www.humanworkplace.com/wp-content/uploads/2013/04/Start-Here-BETTER-COLOR-300x225.jpg
12
Continuous
Improvement
Sample working agreement
• Help one another
• Hold each other accountable
• Have the courage to be honest
• Help each other to do their best
• Have the best intentions
• Have the freedom to speak up
13
Continuous
Improvement
Creating a Working Agreement/Container together
Exercise: 5 min
 Example: Cell phones should be turned on silent?
14
Continuous
Improvement
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 value the items on the left more.
15
Continuous
Improvement
TWELVE PRINCIPLES OF AGILE SOFTWARE
1 Our highest priority is to satisfy the
customer through early and
continuous delivery of valuable
software.
7 Working software is the primary
measure of progress.
2 Welcome changing requirements,
even late in development. Agile
processes harness change for the
customer's competitive advantage.
8 Agile processes promote sustainable
development. The sponsors,
developers, and users should be able
to maintain a constant pace
indefinitely.
3 Deliver working software frequently,
from a couple of weeks to a couple of
months, with a preference to the
shorter timescale.
9 Continuous attention to technical
excellence and good design
enhances agility.
4 Business people and developers must
work together daily throughout the
project.
10 Simplicity -- the art of maximizing the
amount of work not done -- is
essential.
5 Build projects around motivated
individuals. Give them the
environment and support they need,
and trust them to get the job done.
11 The best architectures, requirements,
and designs emerge from self-
organizing teams.
6 The most efficient and effective
method of conveying information to
and within a development team is
face-to-face conversation.
12 At regular intervals, the team reflects
on how to become more effective,
then tunes and adjusts its behavior
accordingly.
From Robert Matheson.com16
Continuous
Improvement
Types of agile
Image taken from Haresh Karkar ‘Overview of Agile Methodology’ from Slideshare
17
Continuous
Improvement
Best videos on scrum
18
Continuous
Improvement
Hold each other accountable
Scrum ceremonies
• Daily Standup (aka Scrum)
• Sprint Review (Demo)
• Sprint Retrospectives
• Sprint Planning
• Also Backlog Grooming/Refinement
• And Release Planning
Continuous
Improvement
Successful Agile companies
• Spotify
• SalesForce.com
• Apple
• Google
20
Continuous
Improvement
Why you should care:
• A framework for the future: New Economy (Denning)
• A framework to Manage Changing Priorities (87%) ¹
• A framework to Fulfilling customer needs (49%) ²
• A framework for Quality of Work Life (87% ) ²
• A framework for On-Time Delivery (58%)¹
• A Framework for Product Quality (48%) ¹
1-Versionone ‘State of Agile Survey’ 9th annual
2-Scrum Alliance ‘The 2015 Scrum Report’
21
Continuous
Improvement
Scrum Roles
Ideal Team Size = 7 ( +/- 2 People
Scrum Master
Product Owner
Scrum Team
Idea size is 7 (+ or – 2)
Data Trends on these roles
• Dedicated Scrum master (24%)
• Scrum Masters on multiple teams (37%)
• PO dedicated to team (29%)
• PO works directly with team (26%)
Scrum Alliance ‘The 2015 Scrum Report’
Interesting Trend!
22
Continuous
Improvement
Background and observations
• Scrum has been around for +14 years
• Agile Manifesto is a Guideline, not a plan
• Scrum requires Mindset Shift of Many
• Scrum requires Top Down and Bottom up Support
• Requires Training, Coaching and ….Time
• But—it’s worth trying 23
Continuous
Improvement
Beyond software or IT
• Hardware [Transportation, automotive, manufacturing] 8%
• Finance (12%)
• Healthcare (6%)
• Government (6%)
• Telecommunications (6%)
• IT/Software (29%)
Scrum Alliance “The 2015 State of Scrum Report”
24
Continuous
Improvement
Empower knowledge workers
• Want a sense of purpose
• Want to master their craft
• Want to work with others
• Want to continuously learn and improve
25
Continuous
Improvement
Team observations
• Losing privacy (cubes)
• Roles not clearly defined
• Varied member investment
• Becoming a hive (swarm)
• No control over own destiny
• Not aware why going agile
• No transformation plan progress/buy in
26
Continuous
Improvement
Reality of scrum teams
• Privacy is reconciled by friendship and laughter
• Takes time to Form and Storm
• Legitimization helps teams with controlling destiny
• Velocity impacted by adding new members
• Difficult to reach 100% Cross functional
• Expectations versus Reality
27
Continuous
Improvement
Scrum is simple but not easy
• Lack of defined metrics for success transition (52%)²
• Lack of Agile experience (44%)¹
• Company philosophy at odds with Agile values (42%) ¹
• Lack of ability to change organization culture (44%) ¹
• Lack of transition from waterfall to Agile (32% ¹, 46% ²)
• Alignment with other projects and portfolio (41%) ²
1-Versionone ‘State of Agile Survey’ 9th annual
2-Scrum Alliance ‘The 2015 Scrum Report’ 28
Continuous
Improvement
Critical success factors
• Working Agreements
• Support, Safety and Protection
• Learning and Experimenting
• Trust and listen to the team
• Support the Scrum Master
• Importance of Team Rooms
29
Continuous
Improvement
It’s all about team work
• Must be able to form and unite as a team
• Must have a Working Agreements
• Must have Support, Safety and Protection
• Must be able to Learn and Experiment
• Must be able to Agree and disagree as a team
30
Continuous
Improvement
Group exercise (5 min)
• Break into groups
• Talk amongst yourself if you have working agreement
elements in your previous job
• Select one volunteer to speak
• If yes or no, why is it important? Take tally
• What can you do to make it better?
31
Continuous
Improvement
Your team should look like this
33
32
Continuous
Improvement
Or like this
http://static1.1.sqspcdn.com/static/f/917789/25534409/1412901035680/Realy-
race.jpg?token=6nfnF4QrqRMy6ybqbD1znNsr4zA%3D
33
Continuous
Improvement
But does it look more like this?
34
Continuous
Improvement
Or like this?
35
Continuous
Improvement
Team Mission: Follow the below example and build a catapult
from normal office materials like:
Try some games
• Popsicle sticks
• Rubber bands
• Bottle caps
• Scotch tape
http://students.jccc.edu/mamatos/boardgames/images/board-games-1.png
36
Continuous
Improvement
Good for
throwing
cookies !
• Duration= 45 minutes
• 5 team members
• 2 separate design at first
• Final design at minute
42
• Team internalized the
building experience
Like This: Team Catapult
37
Continuous
Improvement
Or this Game:
As a team, build a X wing fighter using Legos
• Must use Angry Bird as pilot
• Must have propulsion
• Must have weaponry
• Must have all team members contribute
• Must have one member present final design (demo)
• Must have PO final approval38
Continuous
Improvement
Captain Angry Bird
Star date 0728
39
Continuous
Improvement
Tips For scrum teams
• Gain Agile and Domain knowledge quickly
• Sit in a Team Room together
• Be patient with each other
• Know how to use all tools
• Learn on building a consensus
40
Continuous
Improvement
Tips on how to help
• Support the team-Scrum Masters
• Help remove impediments or assist as needed
• Don’t disturb or pressure the team
• Allow knowledge acquisition
• Speak to the team about decisions
• Be transparent to the team
41
Continuous
Improvement
42
Continuous
Improvement
Dream markers
43
Continuous
Improvement
Suggested Reading:
• Drive by Daniel Pink
• Joy, Inc. by Richard Sheridan
• Essential Scrum by Kenneth S. Rubin
• Succeeding With Agile by Mike Cohn
• Crucial Conversations by Patterson et al
• And many more…. 44
Continuous
Improvement
resources:
• Scrum User Groups
• Conferences
• Webinars/Youtube videos
• Training and Certifications
• Onsite coaching
45
Continuous
Improvement
Agile coach Toolkits
• Scrum Tool Belt
• Training and Certifications
• Lots of non stop reading
• Keeping up with the latest trends
46
Continuous
Improvement
Review
• Shared passion and field experience on Agile
• Provided background on Agile
• Highlighted mostly on Scrum
• Detailed the importance of teamwork
• Performed some fun team exercises
47
Continuous
Improvement
Questions, observations or comments
• Take 5 or 10 minutes
48
Continuous
Improvement
Group exercise (10-20 min)
• Discuss as a group to brain ideas for the next Alpharetta Agile User
group meetup
• Volunteers needed:
 Photographers
 Assistant Organizer
 Co-organizers
 Guest speakers
 Graphic artist -Logo 49
Continuous
Improvement
Conclusion
• Live Long and Prosper in Agile
• Do Good Scrum, not ‘Scrumbutt’
• Upload pictures of this meetup
• Tweet, provide feedback on Social Media
• Keep in touch and thank you for coming
50

Power point template_bootcamp_abridged

  • 1.
    Continuous Improvement Agile : APreview Sue Yeh Johnson, Sue.Johnson@snapstreamllc.com Alpharetta-User Group Meeting Organizer First Meetup, Tuesday, July 28, 2015 5:45-6:45 PM Evans Technology 3655 North Point Pkwy #600, Alpharetta, GA 30005 CSP, CSM, CSPO and PMP
  • 2.
    Continuous Improvement • 17 yearveteran within the IT field • Previous: BA, SA, QA, and PM • Sectors: IT Telecom, Transportation, Retail and Healthcare • Now: Agile Coach • Passionate about all things Agile Bio and experience 1
  • 3.
    Continuous Improvement • Alpharetta-Agile UserGroup meetup • Scrum Alliance Gatherings • Agile Coach’s Circle • Scrum Master Community of Practice • Agile Boot Camp Training • Private, Team & Organizational Agile Coaching Highlights 2
  • 4.
    Continuous Improvement House keeping • Signin and start networking • Know the Restrooms and Exits • Partake in Pizza and Refreshments • Thanks to Evans Technology for the space • Thanks to Sponsors Optomi Staffing Agency for Pizza http://vector-magz.com/wp-content/uploads/2013/09/housekeeping-clipart.gif 3
  • 5.
    Continuous Improvement • Icebreakers andHousekeeping (10 min) • Agile Background and Overview (15 min) • Group Exercises (10 min) • Review and Q &A (5-10 min) • Wrap up and ideas for next meetup (20-25min) • Adjourn agenda http://www.meggin.com/wp-content/uploads/2013/07/graphic-road-sign-change-ahead.jpg 4
  • 6.
    Continuous Improvement • Introduce yourselfto the people close to you • Are you practicing Agile at your work? • If so, what are some challenges? • What do you want to get out of this workshop? • Give them high fives for coming here icebreakers (5 min) http://www.trainsmartinc.com/wp-content/uploads/2014/02/ice-breakers-for-presentations.jpg 5
  • 7.
    Continuous Improvement What this workshopis not • Not a boot camp • Not a certification • No quick answers 6
  • 8.
    Continuous Improvement What this workshopis • Observations from the field • Provide an Agile coaching perspective • Excite you to learn more about Agile • Focus is mostly on SCRUM 7
  • 9.
  • 10.
    Continuous Improvement Or this? Not theAgile what we will be talking about… 9
  • 11.
    Continuous Improvement what is agilemethodology? Agile software development is a group of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. 10
  • 12.
    Continuous Improvement Decided to goagile? • Have a Scrum Team? • Have Product Owner and Scrum Master? • Have a Team Room? • Have a team trained on Agile and Business Domain? Now What? 11
  • 13.
    Continuous Improvement Start a WorkingAgreement http://www.humanworkplace.com/wp-content/uploads/2013/04/Start-Here-BETTER-COLOR-300x225.jpg 12
  • 14.
    Continuous Improvement Sample working agreement •Help one another • Hold each other accountable • Have the courage to be honest • Help each other to do their best • Have the best intentions • Have the freedom to speak up 13
  • 15.
    Continuous Improvement Creating a WorkingAgreement/Container together Exercise: 5 min  Example: Cell phones should be turned on silent? 14
  • 16.
    Continuous Improvement Agile Manifesto Individuals andinteractions 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. 15
  • 17.
    Continuous Improvement TWELVE PRINCIPLES OFAGILE SOFTWARE 1 Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 7 Working software is the primary measure of progress. 2 Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 8 Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 3 Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 9 Continuous attention to technical excellence and good design enhances agility. 4 Business people and developers must work together daily throughout the project. 10 Simplicity -- the art of maximizing the amount of work not done -- is essential. 5 Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 11 The best architectures, requirements, and designs emerge from self- organizing teams. 6 The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 12 At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. From Robert Matheson.com16
  • 18.
    Continuous Improvement Types of agile Imagetaken from Haresh Karkar ‘Overview of Agile Methodology’ from Slideshare 17
  • 19.
  • 20.
    Continuous Improvement Hold each otheraccountable Scrum ceremonies • Daily Standup (aka Scrum) • Sprint Review (Demo) • Sprint Retrospectives • Sprint Planning • Also Backlog Grooming/Refinement • And Release Planning
  • 21.
    Continuous Improvement Successful Agile companies •Spotify • SalesForce.com • Apple • Google 20
  • 22.
    Continuous Improvement Why you shouldcare: • A framework for the future: New Economy (Denning) • A framework to Manage Changing Priorities (87%) ¹ • A framework to Fulfilling customer needs (49%) ² • A framework for Quality of Work Life (87% ) ² • A framework for On-Time Delivery (58%)¹ • A Framework for Product Quality (48%) ¹ 1-Versionone ‘State of Agile Survey’ 9th annual 2-Scrum Alliance ‘The 2015 Scrum Report’ 21
  • 23.
    Continuous Improvement Scrum Roles Ideal TeamSize = 7 ( +/- 2 People Scrum Master Product Owner Scrum Team Idea size is 7 (+ or – 2) Data Trends on these roles • Dedicated Scrum master (24%) • Scrum Masters on multiple teams (37%) • PO dedicated to team (29%) • PO works directly with team (26%) Scrum Alliance ‘The 2015 Scrum Report’ Interesting Trend! 22
  • 24.
    Continuous Improvement Background and observations •Scrum has been around for +14 years • Agile Manifesto is a Guideline, not a plan • Scrum requires Mindset Shift of Many • Scrum requires Top Down and Bottom up Support • Requires Training, Coaching and ….Time • But—it’s worth trying 23
  • 25.
    Continuous Improvement Beyond software orIT • Hardware [Transportation, automotive, manufacturing] 8% • Finance (12%) • Healthcare (6%) • Government (6%) • Telecommunications (6%) • IT/Software (29%) Scrum Alliance “The 2015 State of Scrum Report” 24
  • 26.
    Continuous Improvement Empower knowledge workers •Want a sense of purpose • Want to master their craft • Want to work with others • Want to continuously learn and improve 25
  • 27.
    Continuous Improvement Team observations • Losingprivacy (cubes) • Roles not clearly defined • Varied member investment • Becoming a hive (swarm) • No control over own destiny • Not aware why going agile • No transformation plan progress/buy in 26
  • 28.
    Continuous Improvement Reality of scrumteams • Privacy is reconciled by friendship and laughter • Takes time to Form and Storm • Legitimization helps teams with controlling destiny • Velocity impacted by adding new members • Difficult to reach 100% Cross functional • Expectations versus Reality 27
  • 29.
    Continuous Improvement Scrum is simplebut not easy • Lack of defined metrics for success transition (52%)² • Lack of Agile experience (44%)¹ • Company philosophy at odds with Agile values (42%) ¹ • Lack of ability to change organization culture (44%) ¹ • Lack of transition from waterfall to Agile (32% ¹, 46% ²) • Alignment with other projects and portfolio (41%) ² 1-Versionone ‘State of Agile Survey’ 9th annual 2-Scrum Alliance ‘The 2015 Scrum Report’ 28
  • 30.
    Continuous Improvement Critical success factors •Working Agreements • Support, Safety and Protection • Learning and Experimenting • Trust and listen to the team • Support the Scrum Master • Importance of Team Rooms 29
  • 31.
    Continuous Improvement It’s all aboutteam work • Must be able to form and unite as a team • Must have a Working Agreements • Must have Support, Safety and Protection • Must be able to Learn and Experiment • Must be able to Agree and disagree as a team 30
  • 32.
    Continuous Improvement Group exercise (5min) • Break into groups • Talk amongst yourself if you have working agreement elements in your previous job • Select one volunteer to speak • If yes or no, why is it important? Take tally • What can you do to make it better? 31
  • 33.
  • 34.
  • 35.
    Continuous Improvement But does itlook more like this? 34
  • 36.
  • 37.
    Continuous Improvement Team Mission: Followthe below example and build a catapult from normal office materials like: Try some games • Popsicle sticks • Rubber bands • Bottle caps • Scotch tape http://students.jccc.edu/mamatos/boardgames/images/board-games-1.png 36
  • 38.
    Continuous Improvement Good for throwing cookies ! •Duration= 45 minutes • 5 team members • 2 separate design at first • Final design at minute 42 • Team internalized the building experience Like This: Team Catapult 37
  • 39.
    Continuous Improvement Or this Game: Asa team, build a X wing fighter using Legos • Must use Angry Bird as pilot • Must have propulsion • Must have weaponry • Must have all team members contribute • Must have one member present final design (demo) • Must have PO final approval38
  • 40.
  • 41.
    Continuous Improvement Tips For scrumteams • Gain Agile and Domain knowledge quickly • Sit in a Team Room together • Be patient with each other • Know how to use all tools • Learn on building a consensus 40
  • 42.
    Continuous Improvement Tips on howto help • Support the team-Scrum Masters • Help remove impediments or assist as needed • Don’t disturb or pressure the team • Allow knowledge acquisition • Speak to the team about decisions • Be transparent to the team 41
  • 43.
  • 44.
  • 45.
    Continuous Improvement Suggested Reading: • Driveby Daniel Pink • Joy, Inc. by Richard Sheridan • Essential Scrum by Kenneth S. Rubin • Succeeding With Agile by Mike Cohn • Crucial Conversations by Patterson et al • And many more…. 44
  • 46.
    Continuous Improvement resources: • Scrum UserGroups • Conferences • Webinars/Youtube videos • Training and Certifications • Onsite coaching 45
  • 47.
    Continuous Improvement Agile coach Toolkits •Scrum Tool Belt • Training and Certifications • Lots of non stop reading • Keeping up with the latest trends 46
  • 48.
    Continuous Improvement Review • Shared passionand field experience on Agile • Provided background on Agile • Highlighted mostly on Scrum • Detailed the importance of teamwork • Performed some fun team exercises 47
  • 49.
    Continuous Improvement Questions, observations orcomments • Take 5 or 10 minutes 48
  • 50.
    Continuous Improvement Group exercise (10-20min) • Discuss as a group to brain ideas for the next Alpharetta Agile User group meetup • Volunteers needed:  Photographers  Assistant Organizer  Co-organizers  Guest speakers  Graphic artist -Logo 49
  • 51.
    Continuous Improvement Conclusion • Live Longand Prosper in Agile • Do Good Scrum, not ‘Scrumbutt’ • Upload pictures of this meetup • Tweet, provide feedback on Social Media • Keep in touch and thank you for coming 50

Editor's Notes

  • #2 There are two reasons why I am here First, to share my passion for Agile Second, to kick off new user group From a field perspective
  • #3 I am 1 out 4 kids of Taiwanese immigrant family (Chinese from Taiwan) Came over when I was 9-did not speak English Lived in a small southern town with a small family restaurant While most teenagers went to football games-I was working Being an immigrant -I know what is like to sometimes be marginalized Now, I make sure that my voice is heard
  • #4 These are some highlights of my career Doing Scrum for about five years Attend the yearly scrum gatherings and volunteer Organize a scrum community practice on client site Contact me for team or organizational Agile Transformations Agile boot camp is done through Evans Or I can come onsite
  • #5 Share business cards Networking is everything, ‘Who’ you know Thank you Heidi Thank you Daniel Do anyone of you want to say something?
  • #6 Want to leave some time at the end for Group Meetup Planning discussion
  • #7 Introductions to left or right of you Say, your name Ask if you are doing Agile, if so, how is it going? If not, what do you want to learn today? Give each other high fives for coming here
  • #8 Which is part of an Agile Boot camp is available through Evans if interested Scrum Masters and PO’s can report user group as Scrum Education hours (SEU) Should never stop learning You can get certification from a certified Scrum Trainer
  • #9 There are tons of resources Agile Training Some of them are free from youtube Can go to free meetups like this
  • #10 Let’s get started Is this Agile?
  • #11 Cheetahs can go up to 35 miles an hour Scrum teams are not cheetahs It’s like you are trying to create a relay team with non-runners Everyone runs at their own pace, it is very difficult to sync up You may end up with a team that runs 12 min pace with all team members- but they can finish the race
  • #12 According to Wiki **Question-how many people are working on a team? Raise your hand Build things through teams by using collaboration with customer voice Used all over the world
  • #13 Got everything you need to start Then go to the next step
  • #14 Success of the team depends on how you operate You can set up the tone by working agreements It’s like a contract with each other I would even go further and create a team bill of rights Surprised that most team members are afraid to speak up That is because of command and control/hierarchy
  • #15 Success of the team depends on how you operate You can set up the tone by working agreements It’s like a contract with each other I would even go further and create a team bill of rights Surprised that most team members are afraid to speak up
  • #16 One of the things I learned from Lyssa Adkins What can we create during this meeting together to make sure this meeting is successful? This can be used anywhere at home or at work What are some guidelines? Cell phones on silent No typing on computers No personal agendas Best Intentions (no harassing others or the speaker) In Agile, we call it the No Asshole Policy **Pause for Questions
  • #17 **Raise your hand if heard of Agile Manifesto During blank, 11 people and Jeff Sutherland created this (bund of geeks) Scrum Software Methodology **True or False- is Scrum effective only for software?
  • #18 Here are twelve principles of Agile Software that is part of the Agile Manifesto Agile Boot camp, CSM, or CSPO training goes further in details Read it in detail at your leisure
  • #19 Have a good visualization for Agile Left is more lightweight Scrum-Jeff Sutherland Crystal-Alistair Cockburn (no artifacts) Kanban- Taiichi Ohno Means card, from lean manufacturing like Toyota Can see, Scrum is the middle ground for not too much and too little rules
  • #20 Recommend watching these Scrum videos by Collabnet 6 parts and they are available for free on Youtube Most of my teams have seen this & like them Saw Michael James at a Scrum Gathering Yes, he does look like the guy in the hat I do not get any $ from Collabnet
  • #21 *Do you know how many Scrum ceremonies there are? * Can you list them? 2 week sprints A pretty fast pace in s/w development
  • #22 Most innovative companies use Scrum (Spotify, Salesforce.com and Apple) Organization will have to change in order to survive These companies recognize the importance of delivering solutions via teams new trend, self organizing teams -**Ask the audience-Which companies will do better, those who guess what the customer wants but never talks to them? Or one who has a rep who surveys them while working/sitting with a delivery team?
  • #23 According to Steven Denning, Agile is the new economy
  • #24 **Ask the audience what the scrum roles are Delivery teams can be developers, architects, BA’s, CM, and QA But only 26% of Product owners work with the teams Are these trend good or not?
  • #25 Scrum is not new been around for 15 years Bunch of developers went to a ski resort and create it, include Jeff Sutherland Agile Manifesto does not tell exactly how to do it It is hard to change a human behavior, more or less an entire organization Worth trying, the alternative is not an choice
  • #27 Knowledge workers are those who are paid for their technical expertise (entrepreneurs, innovators, technical people) Carrots and sticks/command and control do not work The want to be engaged **Ask the audience-do you want to be engaged and empowered? Raise your hands
  • #28 Scrum is hard because making a change is hard Due to politics and relationships involved Sometimes there are challenges in relationships within hierarchies (politics) Change to organizations is hard, because it is hard to change people
  • #31 -These are important pillars -Sometimes they are overlooked -No one should control these pillars -SM can help to facilitate -But sometimes SM need the support and help
  • #32 -I use must instead of should
  • #34 Personal testimonial about Paddle boarding It was our anniversary No paddleboards -canoe **Raise your hand if you have seen a crew team (don’t look awesome?) Saw a crew/rowing team pass us by Not buff like the picture But still trying to work as team Crew work all year round and exercises every day They had two coaches Guy in the middle is funny Year round, full commitment Team work is an individual skill Crew does weights and runs on a daily basis
  • #36 Personal testimonial about Paddle boarding It was our anniversary No paddleboards -canoe **Raise your hand if you have seen a crew team (don’t look awesome?) Saw a crew/rowing team pass us by Not buff like the picture But still trying to work as team They had two coaches Guy in the middle is funny Year round, full commitment Team work is an individual skill Crew does weights and runs on a daily basis
  • #37 Personal testimonial about Paddle boarding It was our anniversary No paddleboards -canoe **Raise your hand if you have seen a crew team (don’t look awesome?) Saw a crew/rowing team pass us by Not buff like the picture But still trying to work as team They had two coaches Guy in the middle is funny Year round, full commitment Team work is an individual skill Crew does weights and runs on a daily basis
  • #39 -Exercise with a scrum team -People are not used to it -Thought it was kindergarten games -Was to create a challenge for the team -to perform in that 45 minutes -Internalize team building
  • #41 -Here’s the result -**How many parents do we have in the audience? -I bet you guys know who Thomas is -According to the team, Thomas shoots lasers at other ships
  • #42 Teams have to sit together in order to be successful Companies have to invest into Agile space Teams have to know their stuff Surprise! Some people don’t know some stuff 5. Conference bridge 6. Speaking in front of a group 7. Their jobs or how to do it 8. Know the space/area 9. Many orgs will try to do agile with new team members who don’t know agile or how to do their jobs
  • #44 This is a very good hand drawn while board illustration by Thoughtworks Helps managers on how to help scrum teams during transformation One of things you may not know is that white board drawing helps with shared understanding Neat set of whiteboard markers from Germany is $400 Taken from http://labs.openviewpartners.com/10-things-agile-executives-need-to-do-differently/
  • #45 May sound counter intuitive to use handwriting But the author of that drawing gets the point across Reuse ideas by taking pictures of it Communicate faster by drawing it during collaboration
  • #47 1. There are always resources and teams don’t have to do it alone
  • #48 Take a look at my tools of the trade
  • #49 Almost done Review what we’ve talked about
  • #50 1. Take some time for questions.
  • #51 What would you like it to be? You guys can be product owners or Agile User group committee Scrum master community of practice? Agile Coaching Circle? Have an idea for product already-just need the team/volunteer?
  • #52 Get business card from me Give me a card Go do good scrum How many people are members of multiple meetups? Appreciate everyone who helped or show up to be part of this experience The CEO of Meetup says that sponsoring a meetup takes leadership I hope you start a meetup too