"Can I have my cake and eat it too? Of course, as long as it is one slice at a time!"
Revisit proven strategies and patterns to create small pieces of useful, testable functionality, and explore strategies for getting stories to “ready” and “done”.
Agile India 2017 Conference is Asia's Largest and Premier Conference on Agile, Scrum, eXtreme Programming, Lean, Kanban, DevOps, Enterprise Agile, Lean Startup, Continuous Delivery, Research and Patterns. Get to meet pioneers and expert practitioners from around the world on Agile Mindset, Scaling Agility, Lean Product Discovery, Continuous Delivery and DevOps. 6 - 12 March 2017 at ITC Gardenia, Bangalore. More details: http://2017.agileindia.org
The document examines the product owner role, providing an overview of its history and responsibilities. It discusses how product owners focus on outcomes rather than outputs, build shared understanding among stakeholders, and ensure decisions are made. The document also explores where product owners fit within common organizational models, such as reporting to the product manager, business analyst, or both. It questions whether product owners are needed and ultimately argues they are essential for product ownership by making sure decisions are made, focusing on outcomes over outputs, and building a shared understanding.
Why Scaling Agile Doesn't Work (and What to Do About It)Jez Humble
There are now several frameworks designed to address the demand for "big agile."
In this talk Jez will explain the flaws in such frameworks, why they so often fail to produce the desired effects, and what we should do instead. He will also address some common organizational obstacles to moving fast at scale: governance, budgeting, and the project paradigm - and discuss how to address them. Warning: this talk will include liberal use of real, statistically sound data.
At the core of lean product delivery is -of course- the continuous delivery of a product. Yet, how does this impact the architecture, especially when welcoming changing requirements (even late in development)? Basically, the architecture should be enabled to incorporate these changes and therefore to emerge over time. This implies not to finalize the architecture upfront.
For a small team being jointly responsible for the product delivery AND the architecture this is often already a challenge yet even more so for a large team. But, also for large-scale agile development the requirement for an emergent architecture holds true. However, it is difficult if not unrealistic to expect e.g. 300 team members to decide jointly on the architecture.
Moreover, the role of and support for the architecture depends not only on the degree of the size of your development effort but as well on the degree of complexity of the system.
In this session I report on my experiences using different models for supporting an emergent architecture in different (mainly large-scale) environments that take the degree of complexity into account.
Value Driven Development by Dave Thomas Naresh Jain
Agile, OOP... are like good hygiene in the kitchen, it results in meals with consistent quality and predictable prep and service times. It doesn't result in great meals nor substantially impact the ROI! Lean Thinking clearly shows that the only way to make a significant impact is to improve the value chain by improving flow. If everyone is following best practices no one has competitive advantage. Major improvements in the value chain depend on continued disruptive innovations. Innovations leverage people and their ideas. We use case studies to illustrate the different business and technical innovations and their impact. We conclude with a discussion of how to build and leverage an innovation culture versus a sprint death march when dealing with high value time to market projects.
More details: https://confengine.com/agile-india-2017/proposal/3608/value-driven-development-maximum-impact-maximum-speed
Design Thinking vs. Lean Startup: Friends or Foes?Tathagat Varma
My talk at #AgileIndia2017 on what are the similarities and strengths of Design Thinking and Lean Startup, and where and how we could use them more effectively.
“Every line is the perfect length if you don't measure it.” - Marty Rubin
So your organization has embarked upon a transformation to be more nimble and responsive by employing the latest tools and thinking in the Agile and DevOps arena. In this transformational context, how do you know that your initiatives are effective? Empirical measurements should provide insights on business value flow and delivery efficiency, allowing teams and organizations to see how they are progressing toward achieving their goals, but all too often we find ourselves mired in measurement traps that don't quite provide the right guidance in steering our efforts.
Rooted in contemporary thinking and tested in practice, this talk explores the principles of good measurement, what to measure, what not to measure, and enumerates some key metrics to help guide and inform our Agile and DevOps efforts. If done right, metrics can present a true picture of performance, and any progression, digression of these metrics can drive learning and improvement.
It is our hope that this session inspires organizations and teams to start or take a fresh look at implementing a valuable measurement program.
This document discusses stages of agile adoption from different perspectives - "HowTo", "Therapy", and "Purpose". It describes three stages: (1) viewing agile as a silver bullet solution, (2) despairing when agile is not working, and (3) intentionally contributing value through collaboration and experimentation. The final stage involves refactoring culture with a shared vision and a focus on usefulness, prototyping ideas, and driving transformational change.
Agile India 2017 Conference is Asia's Largest and Premier Conference on Agile, Scrum, eXtreme Programming, Lean, Kanban, DevOps, Enterprise Agile, Lean Startup, Continuous Delivery, Research and Patterns. Get to meet pioneers and expert practitioners from around the world on Agile Mindset, Scaling Agility, Lean Product Discovery, Continuous Delivery and DevOps. 6 - 12 March 2017 at ITC Gardenia, Bangalore. More details: http://2017.agileindia.org
The document examines the product owner role, providing an overview of its history and responsibilities. It discusses how product owners focus on outcomes rather than outputs, build shared understanding among stakeholders, and ensure decisions are made. The document also explores where product owners fit within common organizational models, such as reporting to the product manager, business analyst, or both. It questions whether product owners are needed and ultimately argues they are essential for product ownership by making sure decisions are made, focusing on outcomes over outputs, and building a shared understanding.
Why Scaling Agile Doesn't Work (and What to Do About It)Jez Humble
There are now several frameworks designed to address the demand for "big agile."
In this talk Jez will explain the flaws in such frameworks, why they so often fail to produce the desired effects, and what we should do instead. He will also address some common organizational obstacles to moving fast at scale: governance, budgeting, and the project paradigm - and discuss how to address them. Warning: this talk will include liberal use of real, statistically sound data.
At the core of lean product delivery is -of course- the continuous delivery of a product. Yet, how does this impact the architecture, especially when welcoming changing requirements (even late in development)? Basically, the architecture should be enabled to incorporate these changes and therefore to emerge over time. This implies not to finalize the architecture upfront.
For a small team being jointly responsible for the product delivery AND the architecture this is often already a challenge yet even more so for a large team. But, also for large-scale agile development the requirement for an emergent architecture holds true. However, it is difficult if not unrealistic to expect e.g. 300 team members to decide jointly on the architecture.
Moreover, the role of and support for the architecture depends not only on the degree of the size of your development effort but as well on the degree of complexity of the system.
In this session I report on my experiences using different models for supporting an emergent architecture in different (mainly large-scale) environments that take the degree of complexity into account.
Value Driven Development by Dave Thomas Naresh Jain
Agile, OOP... are like good hygiene in the kitchen, it results in meals with consistent quality and predictable prep and service times. It doesn't result in great meals nor substantially impact the ROI! Lean Thinking clearly shows that the only way to make a significant impact is to improve the value chain by improving flow. If everyone is following best practices no one has competitive advantage. Major improvements in the value chain depend on continued disruptive innovations. Innovations leverage people and their ideas. We use case studies to illustrate the different business and technical innovations and their impact. We conclude with a discussion of how to build and leverage an innovation culture versus a sprint death march when dealing with high value time to market projects.
More details: https://confengine.com/agile-india-2017/proposal/3608/value-driven-development-maximum-impact-maximum-speed
Design Thinking vs. Lean Startup: Friends or Foes?Tathagat Varma
My talk at #AgileIndia2017 on what are the similarities and strengths of Design Thinking and Lean Startup, and where and how we could use them more effectively.
“Every line is the perfect length if you don't measure it.” - Marty Rubin
So your organization has embarked upon a transformation to be more nimble and responsive by employing the latest tools and thinking in the Agile and DevOps arena. In this transformational context, how do you know that your initiatives are effective? Empirical measurements should provide insights on business value flow and delivery efficiency, allowing teams and organizations to see how they are progressing toward achieving their goals, but all too often we find ourselves mired in measurement traps that don't quite provide the right guidance in steering our efforts.
Rooted in contemporary thinking and tested in practice, this talk explores the principles of good measurement, what to measure, what not to measure, and enumerates some key metrics to help guide and inform our Agile and DevOps efforts. If done right, metrics can present a true picture of performance, and any progression, digression of these metrics can drive learning and improvement.
It is our hope that this session inspires organizations and teams to start or take a fresh look at implementing a valuable measurement program.
This document discusses stages of agile adoption from different perspectives - "HowTo", "Therapy", and "Purpose". It describes three stages: (1) viewing agile as a silver bullet solution, (2) despairing when agile is not working, and (3) intentionally contributing value through collaboration and experimentation. The final stage involves refactoring culture with a shared vision and a focus on usefulness, prototyping ideas, and driving transformational change.
Towards FutureOps: Stable, Repeatable environments from Dev to ProdNaresh Jain
Modern human history is a story of humans inventing new tools to do more with less. "Doing more" has allowed most of us to no longer worry about producing our own food, collecting water, planning long journeys, etc. Instead, we’re able to specialize, buy what we need for less, and to some extent explore ourselves a lot more.
We're far from done, and of course humanity is far from perfect. In this talk, Mitchell Hashimoto discusses the role that automations and computers play in building a brighter future.
More details: https://confengine.com/agile-india-2017/proposal/3618/towards-futureops-stable-repeatable-environments-from-dev-to-prod
Mindfulness is a great tool to enhance Emotional Intelligence which is important for Agile mindset - self-organizing, collaborating team members and facilitative leadership.
Traditional business models are failing to keep up with the needs of the modern economy. While business has never been predictable, technological and cultural change is occurring at faster rates than ever before. In this climate, modern enterprises live or die on their ability to adapt – which is where Business Agility comes in. Business Agility provides a context for organisations to embrace change; changing how to think, changing how to work and changing how to interact.
Whether you’ve heard of Holocracy or Teal Organisations; it seems that lean and agile business models are gaining interest across different business sectors. This presentation will provide engaging and enlightening stories of Agile beyond IT; from lean startups to large enterprises. These will be reinforced with practical approaches for the design and leadership of teams, divisions and businesses across 4 key domains;
1. The Structure of an Agile Organisation - Efficient, transparent and collaborative techniques to manage cross-functional, self-organising and potentially self-managing teams.
2. You, the Agile Manager - What makes a good agile manager and how do their responsibilities change?
3. Integrated Customer Engagement - Collaboration and communication techniques to build trust and deliver Customer needs efficiently, with minimal waste, and to everyone’s satisfaction.
4. Work, the Agile Way - Managing all types of business functions, from software, HR, finance to legal, by using Just-In-Time planning and incremental or continuous delivery processes.
Joshua Kerievsky's 2016 keynote speech at Agile2016. Speech abstract follows...
----
Over the past decade, innovative companies, software industry thought leaders and lean/agile pioneers have discovered simpler, sturdier, and more streamlined ways to be agile. While there is timeless wisdom in agile, today's practitioners would do well to bypass outmoded agile practices in favor of modern approaches.
Modern agile methods are defined by four guiding principles
• Make people awesome
• Make safety a prerequisite
• Experience & learn rapidly
• Deliver value continuously
World famous organizations like Google, Amazon, Air BnB, Etsy and others are living proof of the powers of these four principles. However, you don't need to be a name brand company to leverage modern agile wisdom.
In this talk, Josh will explain what he means by modern agility, share real-world modern agile stories, show how modern agile addresses key risks while targeting results over rituals, and reveal how the 2001 agile manifesto can be updated to reflect modern agile's four guiding principles.
All too often we’ve been measuring activity and cost, not outcomes and value. And it’s important to understand that an organisation that plans for growth outcomes (without binding a team to a specific output) can fundamentally adapt to a changing market. By creating clearly defined, non-conflicting, outcomes and common working principles senior management can delegate the “how” to their teams, while retaining ownership of the “what” and “why”.
This interactive presentation will help participants define the real outcomes and associated measures for their work and teams. Participants will come to understand that outcomes can be complex, interdependent and occasionally conflicting. Therefore we will create 3 elements;
1. the profile of the outcome,
2. the relationship between outcomes, and
3. the principles that align work across all outcomes
Technical practices like refactoring and TDD (Test-Driven Development) have become mainstream in software development. However, software developers I met in many companies are either oblivious or have a different interpretation. My interest is to help developers adopt technical practices and being a mentor has played a big part. Through the years I've tried many ways to maximise the effectiveness of mentee's learning and also brings many challenges and discoveries. In this talk, I'll share the experiments I tried and hope it'll inspire you to help others improve their technical practices.
Why don’t we hear as much in the BI space when it comes to Agile? This is probably attributed to the ad-hoc nature of BI projects and fluid nature of End Goals. We over the last few years tried to change this perception and leverage the goodness and effectiveness of being Agile in the BI space. BI is so vast that there are different areas where you can bring in the principles and process of Agile. We are incorporating XP, Scrum and Kanban principles to transform the way we do development and support our businesses. We were also successful in incorporating CI within the BI area using tools such as Jenkins, Stash and Git.
Tis better to be effective than efficientKent McDonald
Better. Faster. Cheaper. Many IT organizations are constantly seeking the "best" practices that will deliver those characteristics, and the fact that they continue to search indicates they haven’t found them yet.
It could be they are looking in the wrong place. Most efforts around achieving better, faster, cheaper center around becoming ultra efficient.
Effectiveness may just be the better target.
Join Kent McDonald to explore the difference between efficiency and effectiveness and learn three simple, yet powerful, techniques that he has found can help teams be more effective. You’ll learn how to:
Build a shared understanding of the problem you are trying to solve
Establish clear guard rails for distributed decision making
Measure progress based on outcome, not output
Along the way he’ll share stories about how he has used these techniques and help you figure out when these techniques may work in your situation.
You may be able to get faster and cheaper with efficiency, but in order to get better outcomes, you need to be effective. Come to this session to learn how.
Agile india 1 day workshop quality in use user experience v5 for sharingIsabel Evans
The document discusses quality in use and user experience. It introduces key concepts like quality, user experience, quality in use, and internal quality. It explains that quality in use looks at how a product influences users' effectiveness, productivity, safety and satisfaction. The document also discusses applying user-centered design principles like creating personas, contexts of use, and quality attributes to design products that meet users' needs.
Continuous Delivery Sounds Great but it Won't Work HereJez Humble
Since the Continuous Delivery book came out in 2010, it's gone from being a controversial idea to a commonplace... until you consider that many people who say they are doing it aren't really, and there are still plenty of places that consider it crazy talk.
In this session Jez will present some of the highlights and lowlights of the past six years listening to people explain why continuous delivery won't work, and what he learned in the process.
This slide deck accompanies a workshop I ran at Agile India in March 2017. The majority of the audience were scrummasters, agile coaches, team managers etc.
It leans on the Heart of Agile meme.
The workshop focused on two activities;
1. thinking about better than best practices so that we can escape the tyranny of other people's patterns.
2. Getting people to reflect on the experience of telling/being told versus collaborating on a problem.
Mythos High Performance Teams - Ein Wunschtraum?Gerrit Beine
Mein Talk von der Agile World 2014:
Sind High Performance Teams ein Mythos?
Ich denke nicht, denn ich hatte das Glück ScrumMaster eines solchen Teams gewesen zu sein.
Wie entsteht so ein Team? Wie erhält man so ein Team?
Und: Wie wird so ein Team noch besser?
Welche Anforderungen stellt ein solches Team an den ScrumMaster und an den Product Owner?
Ich möchte einen Einblick in mein Team geben, wie sie gearbeitet haben, aber auch welche Sorgen die Mitglieder in so einem Team plagen.
Und was man tun muss, um ein solches Team in einer Organisation zu behaupten und welchen Gefahren es ausgesetzt ist.
With Sociocracy Hierarchy becomes Agile by John Buck & Jutta EcksteinJutta Eckstein
Many agile teams suffer from the mismatch of agile and organizational leadership, with the latter being reflected by the organizational hierarchy. Based on self-organization and iterative processes, the agile teams run into trouble with the top-down steering of their environment. Consequently, agile proponents very often believe that a supportive agile organization should be structured without hierarchies, the so called “no managers” approach of “reinvented organizations.” Several companies in the agile field are experimenting with different organizational approaches that don’t use hierarchies. Yet, “no hierarchy” or “no managers” is not an option for many organizations.
In this session we suggest using sociocracy as a solution that leaves the hierarchies in place in an agile way - an option the organization is free to choose. Sociocracy shows how hierarchies can actually be agile and can strongly support (rather than opposing) agile philosophy. It enables managers to become agile leaders. As a participant you will learn how the principles of shared decision making and double-linking are key to enabling self-organization. These principles convert hierarchies from linear to circular so that they support an agile mindset.
Sociocracy is a way for groups and organizations to self-organize. Based on four principles (self-organizing teams, shared decision making based on consent, double-linking, and electing people by consent to functions and tasks), sociocracy provides a path for existing organizations to have empowerment and self-responsibility on all levels. Different than comparable methods, sociocracy allows companies to start where they are – with their existing organizational structures and the like. It seems to be a perfect fit for organizations that need to be truly agile (due to market pressure) beyond their IT departments and software teams.
User Story Mapping: Deliverable slice of valueAngie Doyle
This workshop (with Mark Pearl) was delivered at the Regional Scrum Gathering South Africa and Let's Test South Africa in 2015. It is based on the techniques recommended by Jeff Paton in his book, User Story Mapping.
"Given..When..Then"...a common perception of Behaviour Driven Development focuses on writing and automating SpecFlow-style scenarios. In fact this is just a small part of BDD: the full scope of BDD ranges from requirements discovery and description, through to driving technical design and implementation, helping testers focus their testing efforts more effectively, and even providing reliable, useful and accurate technical documentation. In this talk, you will learn about how much more there is to BDD than just "Given..When..Then"!
Behaviour Driven Development and some of the benefits it offers for developers, customers and testers.
Originally presented at Skills Matter:
http://skillsmatter.com/event/agile-testing/bdd-whats-in-it-for-me
This document outlines an agenda for a entrepreneurship training program run by Founder Centric. The day includes sessions on iterative teaching, workshops and assignments, the design process and goals, getting feedback, and managing risks. Assignments described include developing personal inventories of skills and resources, conducting customer interviews, optimizing an MVP, and launching constrained startup projects over 1-2 weeks. The document emphasizes adapting curriculum flexibly to student needs, using peer support and optional modules, and avoiding common pitfalls like getting stuck on inconsequential details.
Re-uploading my User Story Splitting workshop; it seems to have gone missing.
This is a slide deck I have used for helping people learn various user story splitting techniques.
This document provides an introduction to user experience design. It defines user experience as encompassing all aspects of a user's interaction with a company, service, or product. It describes the role of a user experience designer as involving user research, content creation, coding, user interface design, and competitive analysis. The document outlines techniques for user experience research like usability testing, guerrilla research, and competitive analysis. It discusses how to create personas and problem statements to understand users and design problems. Finally, it provides an activity using a persona and problem statement to demonstrate how to apply this knowledge to design decisions.
Towards FutureOps: Stable, Repeatable environments from Dev to ProdNaresh Jain
Modern human history is a story of humans inventing new tools to do more with less. "Doing more" has allowed most of us to no longer worry about producing our own food, collecting water, planning long journeys, etc. Instead, we’re able to specialize, buy what we need for less, and to some extent explore ourselves a lot more.
We're far from done, and of course humanity is far from perfect. In this talk, Mitchell Hashimoto discusses the role that automations and computers play in building a brighter future.
More details: https://confengine.com/agile-india-2017/proposal/3618/towards-futureops-stable-repeatable-environments-from-dev-to-prod
Mindfulness is a great tool to enhance Emotional Intelligence which is important for Agile mindset - self-organizing, collaborating team members and facilitative leadership.
Traditional business models are failing to keep up with the needs of the modern economy. While business has never been predictable, technological and cultural change is occurring at faster rates than ever before. In this climate, modern enterprises live or die on their ability to adapt – which is where Business Agility comes in. Business Agility provides a context for organisations to embrace change; changing how to think, changing how to work and changing how to interact.
Whether you’ve heard of Holocracy or Teal Organisations; it seems that lean and agile business models are gaining interest across different business sectors. This presentation will provide engaging and enlightening stories of Agile beyond IT; from lean startups to large enterprises. These will be reinforced with practical approaches for the design and leadership of teams, divisions and businesses across 4 key domains;
1. The Structure of an Agile Organisation - Efficient, transparent and collaborative techniques to manage cross-functional, self-organising and potentially self-managing teams.
2. You, the Agile Manager - What makes a good agile manager and how do their responsibilities change?
3. Integrated Customer Engagement - Collaboration and communication techniques to build trust and deliver Customer needs efficiently, with minimal waste, and to everyone’s satisfaction.
4. Work, the Agile Way - Managing all types of business functions, from software, HR, finance to legal, by using Just-In-Time planning and incremental or continuous delivery processes.
Joshua Kerievsky's 2016 keynote speech at Agile2016. Speech abstract follows...
----
Over the past decade, innovative companies, software industry thought leaders and lean/agile pioneers have discovered simpler, sturdier, and more streamlined ways to be agile. While there is timeless wisdom in agile, today's practitioners would do well to bypass outmoded agile practices in favor of modern approaches.
Modern agile methods are defined by four guiding principles
• Make people awesome
• Make safety a prerequisite
• Experience & learn rapidly
• Deliver value continuously
World famous organizations like Google, Amazon, Air BnB, Etsy and others are living proof of the powers of these four principles. However, you don't need to be a name brand company to leverage modern agile wisdom.
In this talk, Josh will explain what he means by modern agility, share real-world modern agile stories, show how modern agile addresses key risks while targeting results over rituals, and reveal how the 2001 agile manifesto can be updated to reflect modern agile's four guiding principles.
All too often we’ve been measuring activity and cost, not outcomes and value. And it’s important to understand that an organisation that plans for growth outcomes (without binding a team to a specific output) can fundamentally adapt to a changing market. By creating clearly defined, non-conflicting, outcomes and common working principles senior management can delegate the “how” to their teams, while retaining ownership of the “what” and “why”.
This interactive presentation will help participants define the real outcomes and associated measures for their work and teams. Participants will come to understand that outcomes can be complex, interdependent and occasionally conflicting. Therefore we will create 3 elements;
1. the profile of the outcome,
2. the relationship between outcomes, and
3. the principles that align work across all outcomes
Technical practices like refactoring and TDD (Test-Driven Development) have become mainstream in software development. However, software developers I met in many companies are either oblivious or have a different interpretation. My interest is to help developers adopt technical practices and being a mentor has played a big part. Through the years I've tried many ways to maximise the effectiveness of mentee's learning and also brings many challenges and discoveries. In this talk, I'll share the experiments I tried and hope it'll inspire you to help others improve their technical practices.
Why don’t we hear as much in the BI space when it comes to Agile? This is probably attributed to the ad-hoc nature of BI projects and fluid nature of End Goals. We over the last few years tried to change this perception and leverage the goodness and effectiveness of being Agile in the BI space. BI is so vast that there are different areas where you can bring in the principles and process of Agile. We are incorporating XP, Scrum and Kanban principles to transform the way we do development and support our businesses. We were also successful in incorporating CI within the BI area using tools such as Jenkins, Stash and Git.
Tis better to be effective than efficientKent McDonald
Better. Faster. Cheaper. Many IT organizations are constantly seeking the "best" practices that will deliver those characteristics, and the fact that they continue to search indicates they haven’t found them yet.
It could be they are looking in the wrong place. Most efforts around achieving better, faster, cheaper center around becoming ultra efficient.
Effectiveness may just be the better target.
Join Kent McDonald to explore the difference between efficiency and effectiveness and learn three simple, yet powerful, techniques that he has found can help teams be more effective. You’ll learn how to:
Build a shared understanding of the problem you are trying to solve
Establish clear guard rails for distributed decision making
Measure progress based on outcome, not output
Along the way he’ll share stories about how he has used these techniques and help you figure out when these techniques may work in your situation.
You may be able to get faster and cheaper with efficiency, but in order to get better outcomes, you need to be effective. Come to this session to learn how.
Agile india 1 day workshop quality in use user experience v5 for sharingIsabel Evans
The document discusses quality in use and user experience. It introduces key concepts like quality, user experience, quality in use, and internal quality. It explains that quality in use looks at how a product influences users' effectiveness, productivity, safety and satisfaction. The document also discusses applying user-centered design principles like creating personas, contexts of use, and quality attributes to design products that meet users' needs.
Continuous Delivery Sounds Great but it Won't Work HereJez Humble
Since the Continuous Delivery book came out in 2010, it's gone from being a controversial idea to a commonplace... until you consider that many people who say they are doing it aren't really, and there are still plenty of places that consider it crazy talk.
In this session Jez will present some of the highlights and lowlights of the past six years listening to people explain why continuous delivery won't work, and what he learned in the process.
This slide deck accompanies a workshop I ran at Agile India in March 2017. The majority of the audience were scrummasters, agile coaches, team managers etc.
It leans on the Heart of Agile meme.
The workshop focused on two activities;
1. thinking about better than best practices so that we can escape the tyranny of other people's patterns.
2. Getting people to reflect on the experience of telling/being told versus collaborating on a problem.
Mythos High Performance Teams - Ein Wunschtraum?Gerrit Beine
Mein Talk von der Agile World 2014:
Sind High Performance Teams ein Mythos?
Ich denke nicht, denn ich hatte das Glück ScrumMaster eines solchen Teams gewesen zu sein.
Wie entsteht so ein Team? Wie erhält man so ein Team?
Und: Wie wird so ein Team noch besser?
Welche Anforderungen stellt ein solches Team an den ScrumMaster und an den Product Owner?
Ich möchte einen Einblick in mein Team geben, wie sie gearbeitet haben, aber auch welche Sorgen die Mitglieder in so einem Team plagen.
Und was man tun muss, um ein solches Team in einer Organisation zu behaupten und welchen Gefahren es ausgesetzt ist.
With Sociocracy Hierarchy becomes Agile by John Buck & Jutta EcksteinJutta Eckstein
Many agile teams suffer from the mismatch of agile and organizational leadership, with the latter being reflected by the organizational hierarchy. Based on self-organization and iterative processes, the agile teams run into trouble with the top-down steering of their environment. Consequently, agile proponents very often believe that a supportive agile organization should be structured without hierarchies, the so called “no managers” approach of “reinvented organizations.” Several companies in the agile field are experimenting with different organizational approaches that don’t use hierarchies. Yet, “no hierarchy” or “no managers” is not an option for many organizations.
In this session we suggest using sociocracy as a solution that leaves the hierarchies in place in an agile way - an option the organization is free to choose. Sociocracy shows how hierarchies can actually be agile and can strongly support (rather than opposing) agile philosophy. It enables managers to become agile leaders. As a participant you will learn how the principles of shared decision making and double-linking are key to enabling self-organization. These principles convert hierarchies from linear to circular so that they support an agile mindset.
Sociocracy is a way for groups and organizations to self-organize. Based on four principles (self-organizing teams, shared decision making based on consent, double-linking, and electing people by consent to functions and tasks), sociocracy provides a path for existing organizations to have empowerment and self-responsibility on all levels. Different than comparable methods, sociocracy allows companies to start where they are – with their existing organizational structures and the like. It seems to be a perfect fit for organizations that need to be truly agile (due to market pressure) beyond their IT departments and software teams.
User Story Mapping: Deliverable slice of valueAngie Doyle
This workshop (with Mark Pearl) was delivered at the Regional Scrum Gathering South Africa and Let's Test South Africa in 2015. It is based on the techniques recommended by Jeff Paton in his book, User Story Mapping.
"Given..When..Then"...a common perception of Behaviour Driven Development focuses on writing and automating SpecFlow-style scenarios. In fact this is just a small part of BDD: the full scope of BDD ranges from requirements discovery and description, through to driving technical design and implementation, helping testers focus their testing efforts more effectively, and even providing reliable, useful and accurate technical documentation. In this talk, you will learn about how much more there is to BDD than just "Given..When..Then"!
Behaviour Driven Development and some of the benefits it offers for developers, customers and testers.
Originally presented at Skills Matter:
http://skillsmatter.com/event/agile-testing/bdd-whats-in-it-for-me
This document outlines an agenda for a entrepreneurship training program run by Founder Centric. The day includes sessions on iterative teaching, workshops and assignments, the design process and goals, getting feedback, and managing risks. Assignments described include developing personal inventories of skills and resources, conducting customer interviews, optimizing an MVP, and launching constrained startup projects over 1-2 weeks. The document emphasizes adapting curriculum flexibly to student needs, using peer support and optional modules, and avoiding common pitfalls like getting stuck on inconsequential details.
Re-uploading my User Story Splitting workshop; it seems to have gone missing.
This is a slide deck I have used for helping people learn various user story splitting techniques.
This document provides an introduction to user experience design. It defines user experience as encompassing all aspects of a user's interaction with a company, service, or product. It describes the role of a user experience designer as involving user research, content creation, coding, user interface design, and competitive analysis. The document outlines techniques for user experience research like usability testing, guerrilla research, and competitive analysis. It discusses how to create personas and problem statements to understand users and design problems. Finally, it provides an activity using a persona and problem statement to demonstrate how to apply this knowledge to design decisions.
Stop spending too much time thinking about the ideas, make it tangible and get feedback quickly. Learn the basic understanding of using rapid physical prototyping made out of aluminium foils and implement it into the design process.
This document provides an overview of a Lean Startup event or workshop. It discusses principles of building iteratively to learn, focusing on learning goals and validating hypotheses through measurement. Key parts of the agenda include lean flow, prioritization, stakeholder analysis, and learning goals. Attendees are encouraged to limit work-in-progress, get early customer feedback, and present their weekly progress and learning goals to get advice from others. The overall message emphasizes rapid prototyping, testing assumptions, and using metrics to guide the business model rather than focusing too much on specific details.
Make thins smart and connect it with internetRanjeet Tayi
This document outlines an agenda for a workshop on designing smart connected things using an Internet of Things approach. The workshop involves a talk on IOT concepts and examples, followed by hands-on design exercises in groups. The exercises involve brainstorming ideas, creating user personas, developing user stories and story maps, sketching designs, validating designs with feedback, and creating a final prototype. The goal is for participants to design an "ultimate personal organizer application" that can run across different devices and mediums.
User Story Mapping for Minimum Lovable ProductsKelley Howell
I gave this presentation at the UX Agile Summit, 2017.
If you have ever sat there staring at your screen or a white board, wondering where to start. If you've ever wondered how you could possibly organize all these user stories into some kind of well-organized plan for iteratively releasing your product, this talk is for you!
In this talk, I will share a way you can generate user stories, organize your backlog, and plan out releases in a way that will ensure that the product is not just minimally viable, but minamally lovable.
The document outlines an agenda for a design workshop day focused on elearning. The workshop will cover conceptualizing elearning design, demonstrations of elearning examples, and a discussion of next steps. During the day, participants will learn about elearning processes and models, how to engage and direct learners, and tips for designing engaging elearning content, such as keeping it light, conversational, and focused on actions. The workshop aims to help participants understand how to design effective and compelling elearning experiences.
Short Introduction on how to use film-like stories as a User Centered Design Method
check out this Storycard Method (used Scrivener in this example) if you're interested in this topic -->
http://www.guerillagirl.de/tools/2011-02/writing-user-scenarios-with-scrivener :)
User Story Mapping for Minimum Lovable Productsuxpin
You'll learn:
How to visualize user needs instead of product features
How to make better decisions when prioritizing a UX backlog
How to align sprints with UX strategy
Chapters 11 and 12 explore cellular automata and their computational abilities. Cellular automata are discrete dynamical systems defined by a regular grid of cells that change state based on a set of rules. Wolfram shows that even simple cellular automata can generate complex behavior and computations. He demonstrates how cellular automata can perform universal computation, emulate Turing machines, and solve computationally hard problems. Overall, these chapters establish cellular automata as a new paradigm for understanding computation and complexity in natural and designed systems.
YC Startup School 2019 How to talk to users frameworkSerge Znu
The document provides guidance on how to conduct effective user interviews for early-stage startups. It outlines common mistakes like talking too much about the idea or hypothetical features rather than listening to learn about user needs. The framework recommends asking open-ended questions to understand problems, past experiences, solutions tried, and dislikes about current options to inform product development and marketing. User interviews are especially important at the idea and prototype stages to gather feedback before reaching product-market fit.
Validate Your Ideas Quickly with Google Design SprintBorrys Hasian
This was presented at Compfest, an annual one-stop IT event held by students of Faculty of Computer Science, University of Indonesia. The deck is about Design Thinking and Google Design Sprint.
Learn how to combine Agile User Stories, Out Side-in Development, and Innovation Games to get the right product built for your customers. Presented to the IIBA 7/8/2007.
The document discusses designing effective eLearning programs. It provides examples of learning models to use such as information and communications models, knowledge and skills models, and behavior and attitude change models. It emphasizes the importance of gaining learner attention, setting direction, using appropriate learning models, summarizing key points, and specifying next steps or actions for learners. The document also discusses best practices for content design such as using scenarios and examples, focusing on learner goals and outcomes, and incorporating different media like video and interactions.
This is the full downloadable "Marczewski" or Gamified UK method workshop. It is the same workshop I delivered at gamification world congress 2014. It has now been changed for a new version, but this should still provide some interesting opportunities in gamification workshops you may wish to run.
http://gamified.uk
The document provides guidance on pitching an idea in under 2 minutes by outlining the key elements needed:
1) Describe the idea by identifying the problem, proposed solution, and target customer.
2) Explain what makes the idea unique or superior to existing alternatives in terms of features, cost, convenience or other benefits.
3) Outline the business model by explaining how money will be made, such as through one-time fees, subscriptions, or societal impact for non-profits. The pitch should cover these core elements in under 2 minutes without slides.
The document discusses design thinking and its application at P&G. It provides:
1) A quote from Steve Jobs emphasizing that design is how something works, not just how it looks.
2) An anecdote from Indira Nooyi about visiting markets weekly as a consumer and seeing clutter, motivating P&G to rethink innovation through design thinking.
3) An overview of design thinking as a creative, iterative process to solve problems and develop solutions through empathy, defining problems correctly, ideating solutions, prototyping, and testing.
The document discusses user stories and how they can be used to improve communication between those building software and those wanting the software. It provides examples of well-structured user stories that include a template, acceptance criteria, and details on how specific and granular stories should be. Technical user stories are also discussed, which focus on non-functional requirements like infrastructure and refactoring rather than end-user functionality. The key benefits of user stories are outlined as being short and modifiable, allowing projects to be broken into small increments, and making effort estimation and development planning easier.
Similar to Be Ready, Be Done: The Art of Slicing Stories (20)
To Deliver, Discover We Must - A value-driven approach to agile planningRaj Indugula
This presentation depicts one organization’s journey from a simplistic Scrum-based planning approach towards a highly disciplined value-driven planning process that follows the precept of progressive elaboration that is repeated systematically at regular intervals, and share ideas, techniques and lessons learned along the way that helped make planning more predictable, and value delivery a priority.
Being Test-Driven: It's not really about testingRaj Indugula
This document discusses test-driven development (TDD) and behavior-driven development (BDD). It describes how BDD uses conversations to discover requirements and build shared understanding. BDD captures conversations as executable specifications expressed in a common language. TDD follows the "Red-Green-Refactor" process of writing a failing test, adding code to pass the test, and refactoring code. TDD drives better design through incremental development guided by tests and prevents overdesign. While TDD can improve design, it also risks overly complex test code and dependencies if not kept simple. The document advocates starting with examples to guide development and testing in a test-driven manner.
Example Mapping provides a structured approach to help teams tease out the essential business rules and examples that clarify a user story and improve shared understanding of story “doneness”
What's Measured Improves: Metrics that matterRaj Indugula
“Every line is the perfect length if you don't measure it.”
- Marty Rubin
So your organization has embarked upon a transformation to be more nimble and responsive by employing the latest tools and thinking in the Agile and DevOps arena. In this transformational context, how do you know that your initiatives are effective? Empirical measurements should provide insights on business value flow and delivery efficiency, allowing teams and organizations to see how they are progressing toward achieving their goals, but all too often we find ourselves mired in measurement traps that don't quite provide the right guidance in steering our efforts.
Rooted in contemporary thinking and tested in practice, this talk explores the principles of good measurement, what to measure, what not to measure, and enumerates some key metrics to help guide and inform our Agile and DevOps efforts. If done right, metrics can present a true picture of performance, and any progression, digression of these metrics can drive learning and improvement.
Gain a deeper understanding of what Exploratory Testing (ET) is, the essential elements of the practice with practical tips and techniques, and finally, ideas for integrating ET into the cadence of an agile process
In just a few years, the Lean Startup movement has gained influence by promoting a powerful but simple agile product management toolset—one that complements agile software development approaches such as Scrum and kanban. This presentation explores the tools and techniques product owners at startup companies and others are employing today for project visioning, experimental design, evaluating new feature impact, prototyping, split testing, and gaining early customer feedback.
Despite the belief that a shared context and collaboration drives quality, too often, software testers and quality professionals struggle to find their place within today's integrated agile teams. This session is a practitioner’s view of testing and testing practices within an iterative/incremental development environment. We will begin with a discussion of some of the challenges of testing within an agile environment and delve into the guiding principles of Agile Testing and key enabling practices. Agile Testing necessitates a change in mindset, and it is as much, if not more, about behavior, as it is about skills and tooling, all of which will be explored.
Effective Testing Practices in an Agile EnvironmentRaj Indugula
This is a practitioner’s view of testing and testing practices within an iterative development environment. We will explore the challenges of testing within such an environment and ways to better integrate the QA professional into what is inherently a developer-centric methodology. If quality is paramount, then we ought to move testing to the front of the line and test early and often. Automation lies at the heart of agility and we will look at how test automation techniques and test-first design philosophy might be applied at multiple-levels to drive quality.
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...Jason Yip
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor IvaniukFwdays
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
12. Useful when…
Initial story describes a
workflow or sequence of
steps
Key Questions
Can you take a thin slice
through the workflow first?
Can you do the beginning
and end of workflow first?
As a learner, I want to
register for a class
and pay for it using a
credit card so that I
am better informed
about Agile
As a learner I
can view
courses
As a customer
I can select the
course I want
to signup for
As a learner I
can review my
registration
As a learner I
can submit my
registration
WORKFLOW STEPS
12
IllustraHon derived from Kent McDonald
13. Useful when…
Initial story encompasses
multiple operations (e.g.
“manage” or “configure”
something)
Key Questions
Can you split the
operations into separate
stories?
Are all these operations
necessary just yet?
As a training
provider, I want
to manage my
course offerings,
so that learners
can view them
…I can
make
upload my
course
catalog
…I can
add a
course
…I can edit
a course
…I can
delete a
course
OPERATIONS
13
14. Useful when…
Initial story impacts
multiple roles and the
impact is different for each
role
Key Questions
Can you identify the
various roles impacted?
Are all roles relevant right
now?
ROLE
As a training
coordinator,
I want to
register a
learner for a
class
As a learner, I
want to register
for a course so
that…
14
As a learner,
I want to
register for
a class
15. Useful when…
Initial story does
something to different
pieces of data
Key Questions
Can you split the story to
process one kind of data
first and enhance with
the other kinds later?
DATA BOUNDARIES
…view
course
name and
description
…view
course
agenda
view course
instructor
qualifications
As a learner, I
want to view
course
information, so
that...
15
16. Useful when…
Initial story has a simple
core functionality that
provides most of the
value
Key Questions
Could you split the story
to do that simple core
first and enhance it with
additional stories later?
SIMPLE FIRST, THEN ENHANCE
As a learner, I want
to see my past
courses, so that…
…see all my
past
courses
…see
courses
completed
on a given
topic
…see
courses
completed
in the past 2
months
16
17. Useful when…
There is significant effort
in doing the first story
even after applying
obvious split
Key Questions
Does it matter which one
we do first?
Can we group the other
stories, given the difficult
first story is done?
MAJOR EFFORT
…pay with
one credit
card type
…pay with all
credit card
types (given
credit card
processing
functionality
is in place)
As a learner, I
want to pay for
my class with
Visa, American
Express, or
MasterCard, so
that…
17
18. Useful when…
Initial story is about
interacting with multiple
instances of something
Key Questions
Does working with nothing
or one thing make it
easier to get started?
Do we really need to deal
with multiple instances
right now?
As an online
shopper, I want to
delete items from
the shopping cart,
so that…
…delete
one item
at a time
…delete
collection
of items
from my
cart
ZERO, ONE, MANY
18
19. Tease out the business rules, and examples that
clarify a user story
Rule Rule Rule
Story
Example
Example
Example
QuesHon
AssumpHon
Example Mapping: Maf Wynne
19
RULES & EXAMPLES
Acceptance
Criteria
Acceptance
Scenarios
20. Useful when…
None of the patterns
seem feasible and team
is still baffled about
splitting the story
Key Questions
What are the key
uncertainties?
SPIKES
Spike:
Investigate
translation
capability
As a learner, I
want to see the
course offerings
in the language
of my choice so
that…
20
21.
22. Zone of Control & Sphere of Influence
Deliverable (I Want…)
CONTROL INFLUENCE
CONTROL INFLUENCE
User Need (So That…)
Good stories
Fake,
Misleading
stories
Not
AcHonable
UnrealisHc
22 Gojko Adzic
24. Of course you can have your cake
and eat it too…
As long as it is a SLICE at a Hme!
24
25. References
Books
• Fifty Quick Ideas to improve your User Stories, Gojko Adzic
• User Story Mapping, Jeff Patton
• User Stories Applied, Mike Kohn
Articles
• http://agileforall.com/wp-content/uploads/2009/10/Story-Splitting-Cheat-Sheet.pdf
• http://www.slideshare.net/arsenalist/splitting-userstories
• http://idiacomputing.com/pub/UserStories.pdf
• http://www.slideshare.net/kentjmcdonald/21-story-splitting-patterns-49940134
• http://blog.jbrains.ca/permalink/how-youll-probably-learn-to-split-features
• https://cucumber.io/blog/2015/12/08/example-mapping-introduction
• http://blog.agilistic.nl/8-useful-strategies-for-splitting-large-user-stories-and-a-cheatsheet/
Ask me for more!
25