Scrumban Demystified. Talk from Agile New England.
A few of the Scrumban Evolutions from Mamamoth bank from the upcoming book on Scrumban.
More excerpts can be found at facebook.com/scrumban
Learn more at scrumban.io
Do you have a case study of applying the Kanban Method in a Scrum context. We want to learn more from your experiments and results. Contact us at info@codegenesys.com
Leading a large-scale agile transformation isn’t about adopting a new set of attitudes, processes, and behaviors at the team level… it’s about helping your company deliver faster to market, and developing the ability to respond to a rapidly-changing competitive landscape. First and foremost, it’s about achieving business agility. Business agility comes from people having clarity of purpose, a willingness to be held accountable, and the ability to achieve measurable outcomes. Unfortunately, almost everything in modern organizations gets in the way of teams acting with any sort of autonomy. In most companies, achieving business agility requires significant organizational change. Join @Mike Cottmeyer live from #Agile2017 during this workshop.
Kanban vs Scrum: What's the difference, and which should you use?Arun Kumar
Originally presented at the 207 Lean Transformation Conference, this presentation provides a practical introduction to Scrum, particularly for public sector employees, and guides you to deciding whether Kanban or Scrum will work best for your teams and projects.
10 steps to a successsful enterprise agile transformation global scrum 2018Agile Velocity
Presented at Scrum Gathering Minneapolis, Senior Agile Coach and Trainer Mike Hall provides leaders and managers 10 steps to a successful enterprise Agile transformation.
Scrum Prioritization Techniques PowerPoint Presentation Slides help you represent the division of large projects into achievable tasks. Use this PPT deck to represent your agile software development approach. Communicate the agile project details and scrum team composition with the visual aid of a well-structured diagram. Demonstrate the goals and phases of your agile project delivery. Explain waterfall technique, scrum-fall, lean, or other methodology for agile application development. The data visualizations featured in this PowerPoint slideshow simplify the translation of agile architecture, and agile automation process. Educate the audience about the project prioritization techniques like MoSCoW, Kano model, and the relative weighting method. Use this PPT presentation to highlight the key priority areas in agile project management. Another important aspect of managing projects is cost. Showcase the agile software project cost using a neat tabular format. You will also get access to the agile program management dashboard diagram to track development. So, smash the download icon and begin instant personalization. Our Scrum Prioritization Techniques PowerPoint Presentation Slides are explicit and effective. They combine clarity and concise expression. https://bit.ly/2IHexRe
The 10 Steps to Becoming a Great Agile CoachLeadingAgile
Recently, at TriAgile 2020, Mike Cottmeyer presented his talk on how to become a great Agile coach. In it, he goes into the four primary areas that make up a great coach, the hard skills you'll need to develop, and how those apply to particular coaching roles.
You can check out the talk here: https://hubs.ly/H0pGFRH0
So you want to become a great Agile coach?
Join us for the premier of Mike Cottmeyer's remote talk that he delivered at TriAgile 2020 and learn the 10 steps you can take to do exactly that.
Watch as Mike explores the four primary skill areas that make a great coach and the hard skills you'll need to develop, and learn how those translate to specific types of coaching roles.
Scrumban Demystified. Talk from Agile New England.
A few of the Scrumban Evolutions from Mamamoth bank from the upcoming book on Scrumban.
More excerpts can be found at facebook.com/scrumban
Learn more at scrumban.io
Do you have a case study of applying the Kanban Method in a Scrum context. We want to learn more from your experiments and results. Contact us at info@codegenesys.com
Leading a large-scale agile transformation isn’t about adopting a new set of attitudes, processes, and behaviors at the team level… it’s about helping your company deliver faster to market, and developing the ability to respond to a rapidly-changing competitive landscape. First and foremost, it’s about achieving business agility. Business agility comes from people having clarity of purpose, a willingness to be held accountable, and the ability to achieve measurable outcomes. Unfortunately, almost everything in modern organizations gets in the way of teams acting with any sort of autonomy. In most companies, achieving business agility requires significant organizational change. Join @Mike Cottmeyer live from #Agile2017 during this workshop.
Kanban vs Scrum: What's the difference, and which should you use?Arun Kumar
Originally presented at the 207 Lean Transformation Conference, this presentation provides a practical introduction to Scrum, particularly for public sector employees, and guides you to deciding whether Kanban or Scrum will work best for your teams and projects.
10 steps to a successsful enterprise agile transformation global scrum 2018Agile Velocity
Presented at Scrum Gathering Minneapolis, Senior Agile Coach and Trainer Mike Hall provides leaders and managers 10 steps to a successful enterprise Agile transformation.
Scrum Prioritization Techniques PowerPoint Presentation Slides help you represent the division of large projects into achievable tasks. Use this PPT deck to represent your agile software development approach. Communicate the agile project details and scrum team composition with the visual aid of a well-structured diagram. Demonstrate the goals and phases of your agile project delivery. Explain waterfall technique, scrum-fall, lean, or other methodology for agile application development. The data visualizations featured in this PowerPoint slideshow simplify the translation of agile architecture, and agile automation process. Educate the audience about the project prioritization techniques like MoSCoW, Kano model, and the relative weighting method. Use this PPT presentation to highlight the key priority areas in agile project management. Another important aspect of managing projects is cost. Showcase the agile software project cost using a neat tabular format. You will also get access to the agile program management dashboard diagram to track development. So, smash the download icon and begin instant personalization. Our Scrum Prioritization Techniques PowerPoint Presentation Slides are explicit and effective. They combine clarity and concise expression. https://bit.ly/2IHexRe
The 10 Steps to Becoming a Great Agile CoachLeadingAgile
Recently, at TriAgile 2020, Mike Cottmeyer presented his talk on how to become a great Agile coach. In it, he goes into the four primary areas that make up a great coach, the hard skills you'll need to develop, and how those apply to particular coaching roles.
You can check out the talk here: https://hubs.ly/H0pGFRH0
So you want to become a great Agile coach?
Join us for the premier of Mike Cottmeyer's remote talk that he delivered at TriAgile 2020 and learn the 10 steps you can take to do exactly that.
Watch as Mike explores the four primary skill areas that make a great coach and the hard skills you'll need to develop, and learn how those translate to specific types of coaching roles.
For those new to Agile there is often an assumption made that the Scrum Master and the Project Manager are the same role.This is absolutely not the case. The two roles are very different and they each fit into approaches to projects that are wildly different as Agile is a Value and Culture driven Project Management Methodology.
I try to address some of the misunderstandings of the Scrum Master Role
You can see some of Scrum Master internal training videos that I did in past.
https://www.youtube.com/my_videos?o=U
How to Become an Indispensable Scrum Master
Modern Professional Scrum using Flow and Kanban - Agile and Beyond Detroit 2019Yuval Yeret
Should you use Scrum or Kanban? You don’t have to choose: Scrum teams improve when they look at flows inside and outside their sprints from a Lean/Kanban perspective. In this session we will talk about Kanban-related myths prevalent in the Scrum world and identify common ground between them. We will look at ways to bring Kanban flow into your Scrum: the Kanban-based Sprint/product backlog, flow-based daily Scrum, visualizing aging work, and flow-based Sprint planning .We will describe ways to wrap Scrum with a Kanban flow system, and how DevOps fits into this picture.
You’ll leave with a better understanding of how Scrum, Kanban, and DevOps relate to each other and with ideas for experiments to try when back at work.
#IBMInterConnect - DCB-3094 Scaling Agile - Launching an Agile Release Train ...Reedy Feggins Jr
In this talk we discuss some of the best practices we have learned for successfully Launching an ART. We discuss how Rational Team Concert (#RTC) can be used to help coordinate the various team activities such as use story analysis, portfolio program and sprint planning, and communicating with the PPM, Agile program and team.
The presentation is from the 2015 #ibminterconnect Conference #feggreed2021
DCB-3094 Scaling Agile Launching a SAFe Agile Release Train using Rational Team Concert – Lesson Learned
Actionable Agile Metrics for Predictability - Daniel VacantiAgile Montréal
Actionable Agile Metrics for Predictability
“When will it be done?” That's the first question customers ask once work is started. Your predictability is judged by the accuracy of your answer. Think about how many times you’ve been asked that question and how many times you’ve been wrong. That you’ve been wrong more times than right is not necessarily your fault. You have been taught to collect and analyze the wrong metrics. Until now.
About Daniel Vacanti
Daniel Vacanti is a 20+ year software industry veteran who has spent most of his career focusing on Lean and Agile practices. In 2007, he helped to develop the Kanban Method for knowledge work and managed the world’s first project implementation of Kanban that year. He has been conducting Lean-Agile training, coaching, and consulting ever since. In 2011 he founded ActionableAgile (previously Corporate Kanban) which provides industry-leading predictive analytics tools and services organizations that utilize Lean-Agile practices. In 2015 he published his book, “Actionable Agile Metrics for Predictability”, which is the definitive guide to flow-based metrics and analytics. Daniel holds an M.B.A. and regularly teaches a class on lean principles for software management at the University of California Berkeley.
Presenter:
Dr. Gail Ferreira, Agile Practice Leader, MATRIX Resources, San Francisco Center of Excellence
Rapid scale directly impacts all levels of decision-making, planning, execution, culture, and communications for executives in hypergrowth companies. In this session, we will discuss how to organize, support, and tailor agile practices for teams and sub-teams in companies with a rapid growth cycle. We will share contemporary case studies of hypergrowth companies who have delivered agile at scale.
Topics will include:
• Basic agile and lean methods
• Scrum of Scrums
• SAFe
• Disciplined Agile Delivery (DAD)
• Agility at Scale (Ambler/Lines)
• Spotify model (Tribes, Squads, Chapters & Guilds, DSDM).
Scrum Teams work best when they collaborate with their product owners to continually refine their backlogs. This is, of course, easier to do when teams are small and collocated. In this webinar, Luke Hohmann, from Conteneo, will present a collection of frameworks that support product owners and Scrum Teams working together to refine backlogs in large and/or distributed teams.
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
Beyond the Scrum Master - Becoming an Agile CoachCprime
For an organization to truly move to agility they must develop more than the traditional Scrum roles of ScrumMaster, Product Owner and Scrum team. They must create internal agile coaches. These agile advocates guide other ScrumMasters and Product Owners, assist teams with problems implementing Scrum and help the organization adopt the agile mindset.
How do you move from the ScrumMaster role to that of an agile coach? In this session, we’ll identify the characteristics of a good agile coach, how the role differs from the ScrumMaster and how to build an internal agile coaching organization. We’ll learn:
• Who makes a good agile coach
• How a typical internal agile coach spends their time
• How to assess problems in an unfamiliar team
• Metrics and tools to help the agile coach
• Getting teams started in Agile
• Continuing your own learning
This session is crucial for anyone who has a desire to help agile practices grow and thrive in the organization.
Team Topologies - how and why to design your teams - AllDayDevOps 2017Matthew Skelton
From the AllDayDevOps 2017 live stream https://www.youtube.com/watch?v=XqowSG2Jxqc
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
Takeaways:
- The implications of Conway’s Law for software teams
- Cognitive Load for teams
- Effective team topologies
- Team evolution
For those new to Agile there is often an assumption made that the Scrum Master and the Project Manager are the same role.This is absolutely not the case. The two roles are very different and they each fit into approaches to projects that are wildly different as Agile is a Value and Culture driven Project Management Methodology.
I try to address some of the misunderstandings of the Scrum Master Role
You can see some of Scrum Master internal training videos that I did in past.
https://www.youtube.com/my_videos?o=U
How to Become an Indispensable Scrum Master
Modern Professional Scrum using Flow and Kanban - Agile and Beyond Detroit 2019Yuval Yeret
Should you use Scrum or Kanban? You don’t have to choose: Scrum teams improve when they look at flows inside and outside their sprints from a Lean/Kanban perspective. In this session we will talk about Kanban-related myths prevalent in the Scrum world and identify common ground between them. We will look at ways to bring Kanban flow into your Scrum: the Kanban-based Sprint/product backlog, flow-based daily Scrum, visualizing aging work, and flow-based Sprint planning .We will describe ways to wrap Scrum with a Kanban flow system, and how DevOps fits into this picture.
You’ll leave with a better understanding of how Scrum, Kanban, and DevOps relate to each other and with ideas for experiments to try when back at work.
#IBMInterConnect - DCB-3094 Scaling Agile - Launching an Agile Release Train ...Reedy Feggins Jr
In this talk we discuss some of the best practices we have learned for successfully Launching an ART. We discuss how Rational Team Concert (#RTC) can be used to help coordinate the various team activities such as use story analysis, portfolio program and sprint planning, and communicating with the PPM, Agile program and team.
The presentation is from the 2015 #ibminterconnect Conference #feggreed2021
DCB-3094 Scaling Agile Launching a SAFe Agile Release Train using Rational Team Concert – Lesson Learned
Actionable Agile Metrics for Predictability - Daniel VacantiAgile Montréal
Actionable Agile Metrics for Predictability
“When will it be done?” That's the first question customers ask once work is started. Your predictability is judged by the accuracy of your answer. Think about how many times you’ve been asked that question and how many times you’ve been wrong. That you’ve been wrong more times than right is not necessarily your fault. You have been taught to collect and analyze the wrong metrics. Until now.
About Daniel Vacanti
Daniel Vacanti is a 20+ year software industry veteran who has spent most of his career focusing on Lean and Agile practices. In 2007, he helped to develop the Kanban Method for knowledge work and managed the world’s first project implementation of Kanban that year. He has been conducting Lean-Agile training, coaching, and consulting ever since. In 2011 he founded ActionableAgile (previously Corporate Kanban) which provides industry-leading predictive analytics tools and services organizations that utilize Lean-Agile practices. In 2015 he published his book, “Actionable Agile Metrics for Predictability”, which is the definitive guide to flow-based metrics and analytics. Daniel holds an M.B.A. and regularly teaches a class on lean principles for software management at the University of California Berkeley.
Presenter:
Dr. Gail Ferreira, Agile Practice Leader, MATRIX Resources, San Francisco Center of Excellence
Rapid scale directly impacts all levels of decision-making, planning, execution, culture, and communications for executives in hypergrowth companies. In this session, we will discuss how to organize, support, and tailor agile practices for teams and sub-teams in companies with a rapid growth cycle. We will share contemporary case studies of hypergrowth companies who have delivered agile at scale.
Topics will include:
• Basic agile and lean methods
• Scrum of Scrums
• SAFe
• Disciplined Agile Delivery (DAD)
• Agility at Scale (Ambler/Lines)
• Spotify model (Tribes, Squads, Chapters & Guilds, DSDM).
Scrum Teams work best when they collaborate with their product owners to continually refine their backlogs. This is, of course, easier to do when teams are small and collocated. In this webinar, Luke Hohmann, from Conteneo, will present a collection of frameworks that support product owners and Scrum Teams working together to refine backlogs in large and/or distributed teams.
Scrum 101 Learning Objectives:
1. Waterfall project methodology basics - what is waterfall and where did it come from?
2. Agile umbrella practices and frameworks - what is agile? what isn't agile? Where does Scrum fit in?
3. Scrum empirical theory - emperical vs. theoretical
4. Parts of the Scrum framework - roles, events / ceremonies, artifacts and rules
5. Features of cultures that use Scrum
Beyond the Scrum Master - Becoming an Agile CoachCprime
For an organization to truly move to agility they must develop more than the traditional Scrum roles of ScrumMaster, Product Owner and Scrum team. They must create internal agile coaches. These agile advocates guide other ScrumMasters and Product Owners, assist teams with problems implementing Scrum and help the organization adopt the agile mindset.
How do you move from the ScrumMaster role to that of an agile coach? In this session, we’ll identify the characteristics of a good agile coach, how the role differs from the ScrumMaster and how to build an internal agile coaching organization. We’ll learn:
• Who makes a good agile coach
• How a typical internal agile coach spends their time
• How to assess problems in an unfamiliar team
• Metrics and tools to help the agile coach
• Getting teams started in Agile
• Continuing your own learning
This session is crucial for anyone who has a desire to help agile practices grow and thrive in the organization.
Team Topologies - how and why to design your teams - AllDayDevOps 2017Matthew Skelton
From the AllDayDevOps 2017 live stream https://www.youtube.com/watch?v=XqowSG2Jxqc
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover the basics of organization design, exploring a selection of key team topologies and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on experience helping companies around the world with the design of their teams.
Takeaways:
- The implications of Conway’s Law for software teams
- Cognitive Load for teams
- Effective team topologies
- Team evolution
In the general view, Scrum is the best Agile method for building a product and developing projects. However, when we have projects that include production support, we should be advised to combine with Kanban. This provides some ideas about Scrumban.
On the one hand, it has the Agile of Scrum, on the other hand it encourages teams to continuously improve their processes along with Kanban.
Scrumban is a solution favored by the service industry, and a great project management tool for teams that deal with product development and its maintenance together.
In this Scrum Breakfast, we would like to share our real life of Scrumban team that we applied to work with our customers.
Topic: The real life of Scrumban team
Speaker: Ms. Anh Thu – Scrum Master at Axon Active Vietnam
Time: Saturday – 25th Feb, 2016 | 9:00 AM – 11:00AM
Venue: Trung Nguyên Cafe, 264A Nam Kỳ Khởi Nghĩa, Ho Chi Minh
#scrum #scrumbreakfast #agile #scrumban #AxonActiveVietnam
Updated version at https://www.slideshare.net/GiulioRoggero/kanban-board-82363781
Do you have a team that works on both project and maintenance? Do you need to organize your team activities? Do you have a lot of activities in parallel and the time to market it's a problem? With a Kanban board and an Agile approach you can solve your problems!
Take a look of the animation of the slides to discover how it works.
Unleashing Your Team's Potential With the Atlassian Team Playbook by John PazJohn Paz
The Team Playbook is free to download, and it's organized and grouped according to the team dynamic you want to address. It includes stories about how Atlassian creates team plays, as well as the plays our Content Designers use most often, and how we use these plays to inform our work.
A workshop I gave at the South African Scrum Gathering on 9 Sep 2011 (#SGZA) in Johannesburg. It examines why sprint reviews are so often awful and how we need to follow some of the rules of a retrospective if we are to achieve value from the review process
Practicing Scrum with Visual Studio 2010 and TFS 2010 - TechEd Middle East 2...Jose Luis Soria
Scrum is maybe the most exciting thing that has happened to the software development world over the last years. Its empirical approach, strikingly changes the way people face projects, and shifts the focus into improving upon development practices, while continuously delivering valuable software increments. Combined with the proper tools and practices, teams can dramatically improve their performance and fulfill customer expectations. This session makes a tour around the Scrum framework, showing how Scrum Teams work in practice, and going into details about how Visual Studio and Team Foundation Server can support and facilitate a great amount of the activities carried out by these teams in their quest for delivering value.
Eve Online has a massive and dedicated audience that is very focused on any changes that CCP makes. By studying and predicting what causes, Anger, CCP can ensure they are making the right decisions for their audience. Our mission is to understand the root cause of Anger in the Eve Online Community and find out what variables can be manipulated to reduce anger in Eve Online Community. We can use this understanding to create a future strategy for CCP that is more aligned with the interests of the community.
ENG 2322College of Professional StudiesProject #4 PortfolioTanaMaeskm
ENG 2322
College of Professional Studies
Project #4: Portfolio
Your syllabus includes the following information about your portfolio:
Portfolio: At the end of the semester, students will choose 2 of the essays they have written, substantially revise them, and, in an appendix, provide samples of process writing related to the two major papers. The portfolio should begin with an introduction that contextualizes the artifacts and accounts for any course outcomes not directly seen in the artifacts.
I will evaluate the papers you submit and assign a grade to the portfolio, which is worth 100 points, approximately 10% of your final grade for ENG 2322. The portfolio is your opportunity to showcase your best work. This is your time to shine! The portfolio will represent your work during the semester and should exemplify your ability to write, as well as revise and edit your own work. You should submit your entire portfolio in ONE Word document.
Portfolio Components:
The portfolio should begin with an introduction that explains which two papers you chose and why. The document should also contain a statement about your writing strengths and weaknesses, as well as a plan to address your weaknesses as you continue to write college-level papers. Next, you should work to discuss whether you believe you have met the specific learning objectives for this course (see below). Finally, the introduction paper should contain a realistic assessment of your work – what grade do you think your portfolio deserves, and why?
Primary Learning ObjectivesDetermine appropriate rhetorical techniques to apply in response to rhetorical situations
Use the writing process to discover and reassess ideasCompose valid arguments in multiple modalitiesSupport arguments with appropriate types of evidenceEvaluate sources for accuracy and authority Navigate print and digital repositories of informationUse the rhetorical situation to determine the appropriate citation systemDescribe how inquiry contributes to a life of significance and worth
After your introduction, you should include your two revised, polished essays that you have chosen to showcase from this course. As a reminder, your options are Project #1, Project #2, and Project #3. Because you have had the opportunity to write, identify errors, and correct them, you are expected to submit papers that are very clean and well written.
After your two polished essays, you should include an appendix that contains the prewriting work that went into your two essays (e.g., brainstorming, journal entries, outlines, drafts, etc.). This appendix should show how your writing has been a process this semester. If you have handwritten any process work for your essays, you can take pictures of it and include those pictures in your Word document.
Project #4 (Portfolio) Rubric
10
9-8
7-6
5-0
Introduction demonstrates thoughtful reflection about personal writing skills
Introduction addresses personal progress toward course learning obj ...
User Experience 6: Qualitative Methods, Playtesting and InterviewsMarc Miquel
This presentation introduces the most fundamental qualitative methods: the playtesting and the interview. It discusses when to use it and the possible bias the researcher may incur.
These slides were prepared by Dr. Marc Miquel. All the materials used in them are referenced to their authors.
B2B payments are rapidly changing. Find out the 5 key questions you need to be asking yourself to be sure you are mastering B2B payments today. Learn more at www.BlueSnap.com.
Anny Serafina Love - Letter of Recommendation by Kellen Harkins, MS.AnnySerafinaLove
This letter, written by Kellen Harkins, Course Director at Full Sail University, commends Anny Love's exemplary performance in the Video Sharing Platforms class. It highlights her dedication, willingness to challenge herself, and exceptional skills in production, editing, and marketing across various video platforms like YouTube, TikTok, and Instagram.
FIA officials brutally tortured innocent and snatched 200 Bitcoins of worth 4...jamalseoexpert1978
Farman Ayaz Khattak and Ehtesham Matloob are government officials in CTW Counter terrorism wing Islamabad, in Federal Investigation Agency FIA Headquarters. CTW and FIA kidnapped crypto currency owner from Islamabad and snatched 200 Bitcoins those worth of 4 billion rupees in Pakistan currency. There is not Cryptocurrency Regulations in Pakistan & CTW is official dacoit and stealing digital assets from the innocent crypto holders and making fake cases of terrorism to keep them silent.
At Techbox Square, in Singapore, we're not just creative web designers and developers, we're the driving force behind your brand identity. Contact us today.
Event Report - SAP Sapphire 2024 Orlando - lots of innovation and old challengesHolger Mueller
Holger Mueller of Constellation Research shares his key takeaways from SAP's Sapphire confernece, held in Orlando, June 3rd till 5th 2024, in the Orange Convention Center.
Premium MEAN Stack Development Solutions for Modern BusinessesSynapseIndia
Stay ahead of the curve with our premium MEAN Stack Development Solutions. Our expert developers utilize MongoDB, Express.js, AngularJS, and Node.js to create modern and responsive web applications. Trust us for cutting-edge solutions that drive your business growth and success.
Know more: https://www.synapseindia.com/technology/mean-stack-development-company.html
Company Valuation webinar series - Tuesday, 4 June 2024FelixPerez547899
This session provided an update as to the latest valuation data in the UK and then delved into a discussion on the upcoming election and the impacts on valuation. We finished, as always with a Q&A
Discover the innovative and creative projects that highlight my journey throu...dylandmeas
Discover the innovative and creative projects that highlight my journey through Full Sail University. Below, you’ll find a collection of my work showcasing my skills and expertise in digital marketing, event planning, and media production.
Personal Brand Statement:
As an Army veteran dedicated to lifelong learning, I bring a disciplined, strategic mindset to my pursuits. I am constantly expanding my knowledge to innovate and lead effectively. My journey is driven by a commitment to excellence, and to make a meaningful impact in the world.
2. Table of Contents
• Introduction
• Getting Started
• Modes of Play
• Teaching Core Concepts
– Leveraging Game Events
– Coaching Tips
– Game Debrief
– Other Resources
Version 0.1 (beta – Sept. 2014)
3. Introduction
The GetScrumban game simulates how
a Software Development team using
Scrum as their chosen framework can
use Scrumban's core principles and
practices to amplify their current
capabilities, overcome common
challenges, or forge new paths to
improved agility.
This “beta” version of our Facilitator’s
Guide is intended to provide basic info
relevant to employing the game as a
training tool. We will modify and add
content as feedback is gained from the
community.
Version 0.1 (beta – Sept. 2014)
4. Core Concepts the Game Reinforces
The game allows players to experiment with and experience
the impact of these principles & practices:
– Expanded Visualizations
• Value Streams
• Types of Work
• Risk Profiles
– Pulling Work vs. Assigning Work
– Evolutionary Adjustments vs. Radical Change
– Cost of Delay vs. Subjective Prioritization
– Distinct Classes of Service vs. Single Workflow
– Continuous Flow vs. Time-boxed Iterations
– Value of Options
– And more…
Version 0.1 (beta – Sept. 2014)
5. Using this Guide
This guide is intended to provide facilitators with
supplemental information and materials that can be used to
improve the benefits of game play.
Purple-shaded boxes call out
segments of game play that
represent appropriate opportunities
for discussing core concepts.
As you become more familiar with the game, you’ll
undoubtedly discover other areas and aspects of play that
represent other opportunities. We invite all facilitators to
share their learnings & suggestions with our trainer
community.
Version 0.1 (beta – Sept. 2014)
6. Getting Started
Single Game vs. Trainer’s Account
Our platform allows anyone to create a single game session
(to be played by one person or one team).
If you’ll be facilitating game play among multiple teams
during a training session, however, we strongly encourage
you to create concurrent sessions under a Trainer’s Account.
This will allow your students to compete against one another
under a common leaderboard you control (and enable you
to coordinate game invitations among multiple participants).
Version 0.1 (beta – Sept. 2014)
7. Training Account Sign-up
Version 0.1 (beta – Sept. 2014)
Individuals who’ve already
created an account can start
new single-session games
here.
Create a trainer or
organizational account by
clicking here.
8. Training Account Sign-up
Version 0.1 (beta – Sept. 2014)
There a 3 levels of trainer’s
accounts. Select a version that
best fits your anticipated
volume of usage.
9. Game Sign-in
If you’ve set up a multiple
game session, instruct your
participants to begin play by
clicking on this icon and
entering their game code.
Version 0.1 (beta – Sept. 2014)
10. Game Sign-in
Version 0.1 (beta – Sept. 2014)
Be sure to instruct your teams
to give themselves a unique
name. This is relevant to
distinguishing themselves on
both your in-class and our
global leaderboards.
11. Video Introduction
Our introductory video provides
background that is relevant to
understanding game play and
highlights common challenges in a
context with which most
participants will be familiar.
Version 0.1 (beta – Sept. 2014)
12. Game Timeline
The Game Timeline is the
mechanism through which
significant events during game
play are communicated.
Participants should click on the
“Close” button to view their
visual work board.
Version 0.1 (beta – Sept. 2014)
13. Initial Task Board
Product / Project
backlog. Hover over
icons to get details
on urgency &
business value.
Work items left over from the
team’s previous Sprint.
Version 0.1 (beta – Sept. 2014)
Team point estimates are
displayed within gold box in
lower right corner of each
user story / bug card.
14. Initial Task Board
Version 0.1 (beta – Sept. 2014)
INSTRUCTION TIP
The game begins on a Sprint
Planning Day.
This is a perfect opportunity to
discuss Cost of Delay concepts
in the context of the projected
business values for features.
Facilitators can also call out
how the visualization of this
info represents a mode of
sharing info that is different
from typical Scrum contexts.
15. Initial Task Board
Version 0.1 (beta – Sept. 2014)
Scrum team members. Workers
surrounded by a green “halo”
are analysts, blue are
developers, and orange are QA
engineers.
INSTRUCTIONAL TIP
Facilitators can point out that daily Scrums are
supposed to bring clarity to what individual
workers are engaged with, what they’re
committing to complete, and any impediments
to their progress.
This is a good point to ask participants to
consider how visualizing work status in more
detail could be beneficial.
16. Modes of Play
Individual Play, Team Play or Both?
Consider whether you want individuals to play this game on
their own, as part of a team, or in both modes (at different
times, naturally).
Team play improves an individual’s ability to communicate
with their team and work together to secure an objective.
Team interaction also better exposes how Scrumban improves
shared understandings and systemic perspectives.
Individual play assures complete engagement and absorption
in the learning experience.
Version 0.1 (beta – Sept. 2014)
17. Team Play - Considerations
The ideal size for a team is between
2-3 people. Players may disengage if more individuals are
involved on a single team.
Because the game involves constant decision-making, some
teams may engage in lengthy analysis. When you have
multiple teams engaged, simultaneous play will help
counter-act this. Offering an additional bonus to the first
team to finish or applying penalties to teams that finish play
past a set time are ways to help assure speedy play.
Version 0.1 (beta – Sept. 2014)
18. Individual Play - Considerations
Individual play allows persons to engage in
trial and error experimentation without having to negotiate
team dynamics. It may be especially beneficial to have
individuals replay the game on an individual basis after a team
play session so they can use that experience as a baseline for
further exploration.
In most circumstances, it’s not pragmatic for a coach or trainer
to engage individual players. Consequently, individuals playing
on their own won’t benefit from pointed questions or guidance
during game play, but game sessions can be assigned as a form
of “homework” or self-study to reinforce concepts discussed in
other settings.
Version 0.1 (beta – Sept. 2014)
19. Teaching Core Concepts
The Game as an Instructional Supplement
GetScrumban is designed to reinforce basic lean
kanban principles and practices to new practitioners. In
our experience, game play is most meaningful when it
participants play as a small team immediately following
1-2 hours of introductory instruction on Scrumban
concepts.
Making the game available for individual play
thereafter is a great way for individuals to further
explore key practices.
Version 0.1 (beta – Sept. 2014)
20. Game Play Cadence
The game purposely introduces a significant
number of events and changing conditions early
on, then smooths out such events over time.
– The swift series of changing conditions helps simulate the
impact of improved understandings and tools within fast
paced environments. It may result, however, in a lighter
absorption of some concepts.
– The slower pace as game the game progresses is intended
to simulate the different experience of evaluating and
responding to current ways of working inb the context of a
regular cadence.
Version 0.1 (beta – Sept. 2014)
21. Initial Task Board
Version 0.1 (beta – Sept. 2014)
INSTRUCTION TIP
Story Point Estimation - On game
day 5, participants are asked to
consider the correlation between
story points and the actual delivery
of completed work.
In our experience, a minority of
Scrum teams realize a close
correlation between these two
metrics.
Though teams won’t have an
opportunity to immediately
address this phenomenon as part
of their game play, it’s a great
place to have participants begin
thinking critically about various
Scrum practices and small steps
that can be taken to improve them.
22. Initial Task Board
Version 0.1 (beta – Sept. 2014)
INSTRUCTIONAL TIP
Deployment Options – When
participants complete all of the
stories under one feature they’ll
be invited to change their policy
around deployment.
This is a good opportunity for
fostering discussion around real
options theory, as well as the
advantages and disadvantages to
deploying completed features
more frequently.
23. Initial Task Board
Version 0.1 (beta – Sept. 2014)
INSTRUCTIONAL TIP
Visualizing the Value Stream – At
the beginning of game day 6,
participants will be given the
option to modify their board
design to better visualize
workflow.
This is a good time to reinforce
the distinction between value
creating steps and functional
hand-offs.
Also, note teams are almost
always presented with a choice
to evolve or not. These events
represent great opportunities to
reinforce this fundamental
principle.
24. Evolved Kanban Board
Version 0.1 (beta – Sept. 2014)
INSTRUCTIONAL TIP
Emergency Work – At the
beginning of game day 7,
participants will be given the
option to complete new work on
an urgent basis.
This is a great opportunity to
contrast differing options under
Scrum and Scrumban (how each
responds to and manages the
reality of urgent work requests).
25. Version 0.1 (beta – Sept. 2014)
Evolved Kanban Board
INSTRUCTIONAL TIP
Expedited Class of Service –
Teams that elect to respond to
the business organization’s
emergency request will be given
the option to modify their visual
board.
This is a good opportunity to
discuss the benefit of visually
distinguishing different types of
work and establishing policies
around them.
26. Version 0.1 (beta – Sept. 2014)
Evolved Kanban Board
INSTRUCTIONAL TIP
Deployment – Deploying features
results in both benefits and costs.
Deployment dates represent a
good opportunity for discussing
these factors, as well as urging
participants to think about ways
they can start managing efforts
to reduce the cost of deployment
while addressing on going
development needs.
27. Version 0.1 (beta – Sept. 2014)
Evolved Kanban Board
INSTRUCTIONAL TIP
Early Benefit – Teams that chose
to expand the visualization of
their work will gain an additional
team member.
Though an indirect benefit, this is
an opportunity to reinforce how
even a small change like
visualizing value streams across
the workflow can help improve
capabilities more intelligently.
28. Version 0.1 (beta – Sept. 2014)
Evolved Kanban Board
INSTRUCTION TIP
Fixed Date Risk Profile – The
product backlog contains fixed
date work items. Stories /
features whose value evaporates
after a given date are highlighted in
yellow.
Facilitators can elect to discuss the
value of visually differentiating
various work item profiles, as well
as discussing concepts of market
risk and cost of delay in this
context.
29. Version 0.1 (beta – Sept. 2014)
Evolved Kanban Board
INSTRUCTIONAL TIP
WIP Limits – If not triggered
earlier by backed up work,
players will be given a choice to
add WIP Limits to their workflow.
These are introduced at this stage
of the game to underscore the
impact of subsequent events and
choices.
41. Group Debriefings
Common Topics for Post-game Discussion
We’ll be adding to this guide over time. Have suggestions?
Be sure to send them our way:
training@codegenesys.com
Version 0.1 (beta – Sept. 2014)