Advertisement
Agile Story Writing Best Practices: Crafting Compelling Narratives in an Iterative World
Author: Amelia Stone, MFA in Creative Writing, Certified ScrumMaster (CSM)
Publisher: Agile Writers Collective, a leading publisher of resources for writers embracing agile methodologies.
Editor: Benjamin Reed, PhD in Literature, experienced editor specializing in technical and creative writing.
Keyword: agile story writing best practices
Abstract: This article delves into the practical application of agile methodologies to enhance the storytelling process. We explore how iterative development, user feedback loops, and collaborative writing can lead to more compelling and engaging narratives. Real-world examples and personal anecdotes illustrate the benefits of adopting these agile story writing best practices.
1. Embracing Iteration: The Agile Heartbeat of Storytelling
Traditional story writing often follows a linear path: outline, first draft, revisions, and finally, publication. This can be rigid and lead to significant rework later in the process. Agile story writing best practices, however, encourage an iterative approach. Think of your story as a software project: you build a minimum viable product (MVP) – a short, core narrative – and then iterate based on feedback.
My first experience with this was during a collaborative fantasy novel project. We initially outlined the main plot points, but rather than writing full chapters, we each focused on a short scene representing a key moment. We then shared these scenes, received feedback, and revised accordingly. This iterative process allowed us to identify plot holes and character inconsistencies early on, saving us considerable time and effort later. It's a perfect example of the effectiveness of agile story writing best practices.
2. User Stories: Finding Your Audience's Voice
In software development, user stories focus on the user's needs and perspective. Applying this principle to agile story writing best practices involves understanding your target audience deeply. Before you begin writing, consider:
Who is your ideal reader? What are their interests, expectations, and preferences?
What problem does your story solve for them? What emotional need does it fulfill?
What are their pain points? What clichés or tropes might they find frustrating?
By crafting user stories – short, concise descriptions of your story from the reader's perspective – you can ensure your narrative resonates with its intended audience. This focus on the reader ensures that agile story writing best practices result in engaging and successful stories.
3. The Power of Sprints: Short, Focused Writing Bursts
Agile methodologies rely heavily on sprints – short, time-boxed periods of intense work. Incorporating sprints into your writing process can dramatically improve productivity and focus. Set realistic goals for each sprint, such as completing a specific scene or achieving a certain word count. This approach combats writer's block and prevents the overwhelming feeling of facing a large, daunting project. The focused effort of sprints is a key component of effective agile story writing best practices.
4. Continuous Feedback: The Crucible of Improvement
Feedback is crucial in agile development, and it's equally important in agile story writing best practices. Regularly share your work with beta readers – friends, writing group members, or even potential readers from your target audience. Their honest feedback can identify weaknesses in your plot, characters, or style, allowing you to make necessary improvements before your story is finalized. This constant feedback loop is a cornerstone of agile story writing best practices.
5. Collaborative Writing: Harnessing Collective Intelligence
Agile methodologies emphasize collaboration. Collaborating on a story, whether with co-authors or through feedback loops, can lead to richer, more compelling narratives. Different perspectives and skillsets can enrich the story significantly. In a case study involving a young adult fantasy novel, a group of writers using agile story writing best practices found that collaborative brainstorming sessions during sprints led to more creative solutions to plot challenges and resulted in a more nuanced and engaging final product.
6. Adaptability: Navigating the Unexpected Turns
The agile approach embraces change. As you write, you may discover that your initial outline needs revision. Perhaps a character arc unexpectedly takes a different direction, or a plot point becomes less relevant. With agile story writing best practices, you’re empowered to adapt your plan, embrace the unexpected, and allow the story to evolve organically. This flexibility prevents writer's block and ensures the final product aligns better with your evolving vision.
7. Measuring Success: Defining Your Story's Metrics
In agile, we define success metrics. What does success look like for your story? Is it completing a first draft within a specific timeframe? Reaching a certain word count? Receiving positive feedback from beta readers? Defining these metrics allows you to track your progress and measure the effectiveness of your agile story writing best practices.
8. Tools and Technologies: Enhancing Your Agile Workflow
Numerous tools can streamline your agile writing process. Project management software like Trello or Asana can help you organize sprints, track progress, and manage feedback. Collaborative writing platforms allow for seamless collaboration with co-authors. Experiment with different tools to find what works best for your workflow and enhances your agile story writing best practices.
Conclusion
Adopting agile story writing best practices can significantly enhance the writing process, leading to more compelling, reader-focused narratives. By embracing iteration, continuous feedback, and collaboration, writers can overcome common obstacles and produce high-quality stories efficiently and effectively. The flexibility and adaptability of this approach empower writers to create truly engaging and impactful work.
FAQs
1. What if my story drastically changes during the iterative process? That's perfectly acceptable within the agile framework. The iterative process allows for adaptation and improvement based on feedback and evolving ideas.
2. How many sprints should I use for a novel-length story? This depends on your personal preference and the scope of your project. Consider breaking down your novel into smaller, manageable chunks, each forming a sprint.
3. How do I find effective beta readers? Join writing groups, connect with fellow writers online, or ask friends and family who fit your target audience profile.
4. What if my beta readers provide conflicting feedback? Analyze the feedback carefully. Consider which feedback aligns with your overall vision and target audience, and prioritize those suggestions.
5. Can agile story writing practices be used for non-fiction writing? Absolutely! The principles of iteration, feedback, and collaboration are valuable for all forms of writing.
6. How can I measure the success of my agile writing sprints? Track your word count, assess the quality of your writing based on feedback, and monitor your overall progress toward completing the story.
7. Are there any specific software programs for agile story writing? While no specific software is dedicated solely to agile story writing, project management tools like Trello, Asana, and even simple spreadsheets can be effective for managing sprints and feedback.
8. Is agile story writing suitable for solo writers? Yes, even solo writers can benefit from the principles of agile writing by employing self-reflection as a form of feedback and breaking down the project into smaller, manageable parts.
9. Can I use agile story writing practices for screenwriting or playwriting? Yes, the principles of agile can be adapted to any form of narrative storytelling. Consider using sprints to write scenes, and get feedback from readers or fellow writers.
Related Articles:
1. "Agile Storyboarding: Visualizing Your Narrative": This article explores the use of storyboarding techniques to plan and visualize your story in an agile manner.
2. "Character Development in Agile Writing: An Iterative Approach": This article focuses on building compelling characters through iterative development and feedback.
3. "Plot Structure and Agile Writing: Embracing Change and Adaptation": This article explores how to adapt your plot structure using agile principles.
4. "Using Agile for Collaborative Novel Writing": This article delves into the specifics of applying agile methodologies to collaborative novel writing projects.
5. "Agile Writing Sprints: Mastering Time Management and Productivity": This article provides practical tips for effectively managing sprints in your writing process.
6. "Gathering and Implementing Feedback in Agile Story Writing": This article provides guidance on receiving and integrating reader feedback effectively.
7. "Overcoming Writer's Block with Agile Methods": This article explores how agile principles can help combat writer's block and maintain momentum.
8. "Agile Writing and Worldbuilding: Creating Consistent and Believable Worlds": This article focuses on building rich and consistent fictional worlds using agile methodologies.
9. "Marketing Your Story Using Agile Principles: Reaching Your Target Audience": This article explores how to use agile principles to market and promote your finished story.
| agile story writing best practices: User Story Mapping Jeff Patton, Peter Economy, 2014-09-05 User story mapping is a valuable tool for software development, once you understand why and how to use it. This insightful book examines how this often misunderstood technique can help your team stay focused on users and their needs without getting lost in the enthusiasm for individual product features. Author Jeff Patton shows you how changeable story maps enable your team to hold better conversations about the project throughout the development process. Your team will learn to come away with a shared understanding of what you’re attempting to build and why. Get a high-level view of story mapping, with an exercise to learn key concepts quickly Understand how stories really work, and how they come to life in Agile and Lean projects Dive into a story’s lifecycle, starting with opportunities and moving deeper into discovery Prepare your stories, pay attention while they’re built, and learn from those you convert to working software |
| agile story writing best practices: User Stories Applied Mike Cohn, 2004-03-01 Thoroughly reviewed and eagerly anticipated by the agile community, User Stories Applied offers a requirements process that saves time, eliminates rework, and leads directly to better software. The best way to build software that meets users' needs is to begin with user stories: simple, clear, brief descriptions of functionality that will be valuable to real users. In User Stories Applied, Mike Cohn provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle. You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather user stories, even when you can't speak with your users. Then, once you've compiled your user stories, Cohn shows how to organize them, prioritize them, and use them for planning, management, and testing. User role modeling: understanding what users have in common, and where they differ Gathering stories: user interviewing, questionnaires, observation, and workshops Working with managers, trainers, salespeople and other proxies Writing user stories for acceptance testing Using stories to prioritize, set schedules, and estimate release costs Includes end-of-chapter practice questions and exercises User Stories Applied will be invaluable to every software developer, tester, analyst, and manager working with any agile method: XP, Scrum... or even your own home-grown approach. |
| agile story writing best practices: Fifty Quick Ideas to Improve Your User Stories Gojko Adzic, David Evans, 2014-10-15 This book will help you write better stories, spot and fix common issues, split stories so that they are smaller but still valuable, and deal with difficult stuff like crosscutting concerns, long-term effects and non-functional requirements. Above all, this book will help you achieve the promise of agile and iterative delivery: to ensure that the right stuff gets delivered through productive discussions between delivery team members and business stakeholders. Who is this book for? This is a book for anyone working in an iterative delivery environment, doing planning with user stories. The ideas in this book are useful both to people relatively new to user stories and those who have been working with them for years. People who work in software delivery, regardless of their role, will find plenty of tips for engaging stakeholders better and structuring iterative plans more effectively. Business stakeholders working with software teams will discover how to provide better information to their delivery groups, how to set better priorities and how to outrun the competition by achieving more with less software. What's inside? Unsurprisingly, the book contains exactly fifty ideas. They are grouped into five major parts: - Creating stories: This part deals with capturing information about stories before they get accepted into the delivery pipeline. You'll find ideas about what kind of information to note down on story cards and how to quickly spot potential problems. - Planning with stories: This part contains ideas that will help you manage the big-picture view, set milestones and organise long-term work. - Discussing stories: User stories are all about effective conversations, and this part contains ideas to improve discussions between delivery teams and business stakeholders. You'll find out how to discover hidden assumptions and how to facilitate effective conversations to ensure shared understanding. - Splitting stories: The ideas in this part will help you deal with large and difficult stories, offering several strategies for dividing them into smaller chunks that will help you learn fast and deliver value quickly. - Managing iterative delivery: This part contains ideas that will help you work with user stories in the short and mid term, manage capacity, prioritise and reduce scope to achieve the most with the least software. About the authors: Gojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. Gojko's book Specification by Example was awarded the #2 spot on the top 100 agile books for 2012 and won the Jolt Award for the best book of 2012. In 2011, he was voted by peers as the most influential agile testing professional, and his blog won the UK agile award for the best online publication in 2010. David Evans is a consultant, coach and trainer specialising in the field of Agile Quality. David helps organisations with strategic process improvement and coaches teams on effective agile practice. He is regularly in demand as a conference speaker and has had several articles published in international journals. |
| agile story writing best practices: The Innovation Mode George Krasadakis, 2020-07-29 This book presents unique insights and advice on defining and managing the innovation transformation journey. Using novel ideas, examples and best practices, it empowers management executives at all levels to drive cultural, technological and organizational changes toward innovation. Covering modern innovation techniques, tools, programs and strategies, it focuses on the role of the latest technologies (e.g., artificial intelligence to discover, handle and manage ideas), methodologies (including Agile Engineering and Rapid Prototyping) and combinations of these (like hackathons or gamification). At the same time, it highlights the importance of culture and provides suggestions on how to build it. In the era of AI and the unprecedented pace of technology evolution, companies need to become truly innovative in order to survive. The transformation toward an innovation-led company is difficult – it requires a strong leadership and culture, advanced technologies and well-designed programs. The book is based on the author’s long-term experience and novel ideas, and reflects two decades of startup, consulting and corporate leadership experience. It is intended for business, technology, and innovation leaders. |
| agile story writing best practices: Agile Product Management with Scrum Roman Pichler, 2010-03-11 The First Guide to Scrum-Based Agile Product Management In Agile Product Management with Scrum, leading Scrum consultant Roman Pichler uses real-world examples to demonstrate how product owners can create successful products with Scrum. He describes a broad range of agile product management practices, including making agile product discovery work, taking advantage of emergent requirements, creating the minimal marketable product, leveraging early customer feedback, and working closely with the development team. Benefitting from Pichler’s extensive experience, you’ll learn how Scrum product ownership differs from traditional product management and how to avoid and overcome the common challenges that Scrum product owners face. Coverage includes Understanding the product owner’s role: what product owners do, how they do it, and the surprising implications Envisioning the product: creating a compelling product vision to galvanize and guide the team and stakeholders Grooming the product backlog: managing the product backlog effectively even for the most complex products Planning the release: bringing clarity to scheduling, budgeting, and functionality decisions Collaborating in sprint meetings: understanding the product owner’s role in sprint meetings, including the dos and don’ts Transitioning into product ownership: succeeding as a product owner and establishing the role in the enterprise This book is an indispensable resource for anyone who works as a product owner, or expects to do so, as well as executives and coaches interested in establishing agile product management. |
| agile story writing best practices: The Art of Agile Development James Shore, Shane Warden, 2008 For those considering Extreme Programming, this book provides no-nonsense advice on agile planning, development, delivery, and management taken from the authors' many years of experience. While plenty of books address the what and why of agile development, very few offer the information users can apply directly. |
| agile story writing best practices: Writing Effective User Stories Thomas and Angela Hathaway, 2013-07-29 WHAT IS THIS BOOK ABOUT? This Book Is About the “Card” (User Story: Card, Criteria, Conversation) User Stories are a great method for expressing stakeholder requirements, whether your projects follow an Agile, Iterative, or a Waterfall methodology. They are the basis for developers to deliver a suitable information technology (IT) app or application. Well-structured user stories express a single action to achieve a specific goal from the perspective of a single role. When writing user stories, stakeholders knowledgeable about the role should focus on the business result that the IT solution will enable while leaving technology decisions up to the developers. Good user stories are relevant to the project, unambiguous, and understandable to knowledge peers. The best user stories also contain crucial non-functional (quality) requirements, which are the best weapon in the war against unsatisfactory performance in IT solutions. This book presents two common user story structures to help you ensure that your user stories have all the required components and that they express the true business need as succinctly as possible. It offers five simple rules to ensure that your user stories are the best that they can be. That, in turn, will reduce the amount of time needed in user story elaboration and discussion with the development team. This book targets business professionals who are involved with an IT project, Product Owners in charge of managing a backlog, or Business Analysts working with an Agile team. Author’s Note The term “User Story” is a relative new addition to our language and its definition is evolving. In today’s parlance, a complete User Story has three primary components, namely the “Card”, the “Conversation”, and the “Criteria”. Different roles are responsible for creating each component. The “Card” expresses a business need. A representative of the business community is responsible for expressing the business need. Historically (and for practical reasons) the “Card” is the User Story from the perspective of the business community. Since we wrote this book specifically to address that audience, we use the term “User Story” in that context throughout. The “Conversation” is an ongoing discussion between a developer responsible for creating software that meets the business need and the domain expert(s) who defined it (e.g., the original author of the “Card”). The developer initiates the “Conversation” with the domain expert(s) to define the “Criteria” and any additional information the developer needs to create the application. There is much to be written about both the “Conversation” and the “Criteria”, but neither component is dealt with in any detail in this publication. A well-written User Story (“Card”) can drastically reduce the time needed for the “Conversation”. It reduces misinterpretations, misunderstandings, and false starts, thereby paving the way for faster delivery of working software. We chose to limit the content of this publication to the “User Story” as understood by the business community to keep the book focused and address the widest possible audience. WHO WILL BENEFIT FROM READING THIS BOOK? How organizations develop and deliver working software has changed significantly in recent years. Because the change was greatest in the developer community, many books and courses justifiably target that group. There is, however, an overlooked group of people essential to the development of software-as-an-asset that have been neglected. Many distinct roles or job titles in the business community perform business needs analysis for digital solutions. They include: - Product Owners - Business Analysts - Requirements Engineers - Test Developers - Business- and Customer-side Team Members - Agile Team Members - Subject Matter Experts (SME) - Project Leaders and Managers - Systems Analysts and Designers - AND “anyone wearing the business analysis hat”, meaning anyone responsible for defining a future IT solution TOM AND ANGELA’S (the authors) STORY Like all good IT stories, theirs started on a project many years ago. Tom was the super techie, Angela the super SME. They fought their way through the 3-year development of a new policy maintenance system for an insurance company. They vehemently disagreed on many aspects, but in the process discovered a fundamental truth about IT projects. The business community (Angela) should decide on the business needs while the technical team’s (Tom)’s job was to make the technology deliver what the business needed. Talk about a revolutionary idea! All that was left was learning how to communicate with each other without bloodshed to make the project a resounding success. Mission accomplished. They decided this epiphany was so important that the world needed to know about it. As a result, they made it their mission (and their passion) to share this ground-breaking concept with the rest of the world. To achieve that lofty goal, they married and began the mission that still defines their life. After over 30 years of living and working together 24x7x365, they are still wildly enthusiastic about helping the victims of technology learn how to ask for and get the digital (IT) solutions they need to do their jobs better. More importantly, they are more enthusiastically in love with each other than ever before! |
| agile story writing best practices: Succeeding with Agile Mike Cohn, 2010 Proven, 100% Practical Guidance for Making Scrum and Agile Work in Any Organization This is the definitive, realistic, actionable guide to starting fast with Scrum and agile-and then succeeding over the long haul. Leading agile consultant and practitioner Mike Cohn presents detailed recommendations, powerful tips, and real-world case studies drawn from his unparalleled experience helping hundreds of software organizations make Scrum and agile work. Succeeding with Agile is for pragmatic software professionals who want real answers to the most difficult challenges they face in implementing Scrum. Cohn covers every facet of the transition: getting started, helping individuals transition to new roles, structuring teams, scaling up, working with a distributed team, and finally, implementing effective metrics and continuous improvement. Throughout, Cohn presents Things to Try Now sections based on his most successful advice. Complementary Objection sections reproduce typical conversations with those resisting change and offer practical guidance for addressing their concerns. Coverage includes Practical ways to get started immediately-and get good fast Overcoming individual resistance to the changes Scrum requires Staffing Scrum projects and building effective teams Establishing improvement communities of people who are passionate about driving change Choosing which agile technical practices to use or experiment with Leading self-organizing teams Making the most of Scrum sprints, planning, and quality techniques Scaling Scrum to distributed, multiteam projects Using Scrum on projects with complex sequential processes or challenging compliance and governance requirements Understanding Scrum's impact on HR, facilities, and project management Whether you've completed a few sprints or multiple agile projects and whatever your role-manager, developer, coach, ScrumMaster, product owner, analyst, team lead, or project lead-this book will help you succeed with your very next project. Then, it will help you go much further: It will help you transform your entire development organization. |
| agile story writing best practices: Getting Results the Agile Way J. D. Meier, 2010 A guide to the Agile Results system, a systematic way to achieve both short- and long-term results that can be applied to all aspects of life. |
| agile story writing best practices: Agile Estimating and Planning Mike Cohn, 2005-11-01 Agile Estimating and Planning is the definitive, practical guide to estimating and planning agile projects. In this book, Agile Alliance cofounder Mike Cohn discusses the philosophy of agile estimating and planning and shows you exactly how to get the job done, with real-world examples and case studies. Concepts are clearly illustrated and readers are guided, step by step, toward how to answer the following questions: What will we build? How big will it be? When must it be done? How much can I really complete by then? You will first learn what makes a good plan-and then what makes it agile. Using the techniques in Agile Estimating and Planning, you can stay agile from start to finish, saving time, conserving resources, and accomplishing more. Highlights include: Why conventional prescriptive planning fails and why agile planning works How to estimate feature size using story points and ideal days–and when to use each How and when to re-estimate How to prioritize features using both financial and nonfinancial approaches How to split large features into smaller, more manageable ones How to plan iterations and predict your team's initial rate of progress How to schedule projects that have unusually high uncertainty or schedule-related risk How to estimate projects that will be worked on by multiple teams Agile Estimating and Planning supports any agile, semiagile, or iterative process, including Scrum, XP, Feature-Driven Development, Crystal, Adaptive Software Development, DSDM, Unified Process, and many more. It will be an indispensable resource for every development manager, team leader, and team member. |
| agile story writing best practices: Essential Scrum Kenneth S. Rubin, 2012 This is a comprehensive guide to Scrum for all (team members, managers, and executives). If you want to use Scrum to develop innovative products and services that delight your customers, this is the complete, single-source reference you've been searching for. This book provides a common understanding of Scrum, a shared vocabulary that can be used in applying it, and practical knowledge for deriving maximum value from it. |
| agile story writing best practices: Driving Digital Isaac Sacolick, 2017-08-24 Every organization makes plans for updating products, technologies, and business processes. But that’s not enough anymore for the twenty-first-century company. The race is now on for everyone to become a digital enterprise. For those individuals who have been charged with leading their company’s technology-driven change, the pressure is intense while the correct path forward unclear. Help has arrived! In Driving Digital, author Isaac Sacolick shares the lessons he’s learned over the years as he has successfully spearheaded multiple transformations and helped shape digital-business best practices. Readers no longer have to blindly trek through the mine field of their company’s digital transformation. In this thoroughly researched one-stop manual, learn how to: • Formulate a digital strategy • Transform business and IT practices • Align development and operations • Drive culture change • Bolster digital talent • Capture and track ROI • Develop innovative digital practices • Pilot emerging technologies • And more! Your company cannot avoid the digital disruption heading its way. The choice is yours: Will this mean the beginning of the end for your business, or will your digital practices be what catapults you into next-level success? |
| agile story writing best practices: Writing Effective Use Cases Alistair Cockburn, 2001 This guide will help readers learn how to employ the significant power of use cases to their software development efforts. It provides a practical methodology, presenting key use case concepts. |
| agile story writing best practices: Agile Software Requirements Dean Leffingwell, 2010-12-27 “We need better approaches to understanding and managing software requirements, and Dean provides them in this book. He draws ideas from three very useful intellectual pools: classical management practices, Agile methods, and lean product development. By combining the strengths of these three approaches, he has produced something that works better than any one in isolation.” –From the Foreword by Don Reinertsen, President of Reinertsen & Associates; author of Managing the Design Factory; and leading expert on rapid product development Effective requirements discovery and analysis is a critical best practice for serious application development. Until now, however, requirements and Agile methods have rarely coexisted peacefully. For many enterprises considering Agile approaches, the absence of effective and scalable Agile requirements processes has been a showstopper for Agile adoption. In Agile Software Requirements, Dean Leffingwell shows exactly how to create effective requirements in Agile environments. Part I presents the “big picture” of Agile requirements in the enterprise, and describes an overall process model for Agile requirements at the project team, program, and portfolio levels Part II describes a simple and lightweight, yet comprehensive model that Agile project teams can use to manage requirements Part III shows how to develop Agile requirements for complex systems that require the cooperation of multiple teams Part IV guides enterprises in developing Agile requirements for ever-larger “systems of systems,” application suites, and product portfolios This book will help you leverage the benefits of Agile without sacrificing the value of effective requirements discovery and analysis. You’ll find proven solutions you can apply right now–whether you’re a software developer or tester, executive, project/program manager, architect, or team leader. |
| agile story writing best practices: Large-Scale Scrum Craig Larman, Bas Vodde, 2016-09-30 The Go-To Resource for Large-Scale Organizations to Be Agile Rather than asking, “How can we do agile at scale in our big complex organization?” a different and deeper question is, “How can we have the same simple structure that Scrum offers for the organization, and be agile at scale rather than do agile?” This profound insight is at the heart of LeSS (Large-Scale Scrum). In Large-Scale Scrum: More with LeSS, Craig Larman and Bas Vodde have distilled over a decade of experience in large-scale LeSS adoptions towards a simpler organization that delivers more flexibility with less complexity, more value with less waste, and more purpose with less prescription. Targeted to anyone involved in large-scale development, Large-Scale Scrum: More with LeSS, offers straight-to-the-point guides for how to be agile at scale, with LeSS. It will clearly guide you to Adopt LeSS Structure a large development organization for customer value Clarify the role of management and Scrum Master Define what your product is, and why Be a great Product Owner Work with multiple whole-product focused feature teams in one Sprint that produces a shippable product Coordinate and integrate between teams Work with multi-site teams |
| agile story writing best practices: How to Lead in Product Management: Practices to Align Stakeholders, Guide Development Teams, and Create Value Together Roman Pichler, 2020-03-10 This book will help you become a better product leader. Benefitting from Roman Pichler's extensive experience, you will learn how to align stakeholders and guide development teams even in challenging circumstances, avoid common leadership mistakes, and grow as a leader. Written in an engaging and easily accessible style, How to Lead in Product Management offers a wealth of practical tips and strategies. Through helpful examples, the book illustrates how you can directly apply the techniques to your work. Coverage includes: * Choosing the right leadership style * Cultivating empathy, building trust, and influencing others * Increasing your authority and empowering others * Directing stakeholders and development teams through common goals * Making decisions that people will support and follow through * Successfully resolving disputes and conflicts even with senior stakeholders * Listening deeply to discover and address hidden needs and interests * Practising mindfulness and embracing a growth mindset to develop as a leader Praise for How to Lead in Product Management: Roman has done it again, delivering a practical book for the product management community that appeals to both heart and mind. How to Lead in Product Management is packed with concise, direct, and practical advice that addresses the deeper, personal aspects of the product leadership. Roman's book shares wisdom on topics including goals, healthy interactions with stakeholders, handling conflict, effective conversations, decision-making, having a growth mindset, and self-care. It is a must read for both new and experienced product people. ~Ellen Gottesdiener, Product Coach at EBG Consulting Being a great product manager is tough. It requires domain knowledge, industry knowledge, technical skills, but also the skills to lead and inspire a team. Roman Pichler's How to Lead in Product Management is the best book I've read for equipping product managers to lead their teams. ~Mike Cohn, Author of Succeeding with Agile, Agile Estimating and Planning, and User Stories Applied This is the book that has been missing for product people. Roman has created another masterpiece, a fast read with lots of value. It's a must read for every aspiring product manager. ~Magnus Billgren, CEO of Tolpagorni Product Management How Lead in Product Management is for everyone who manages a product or drives important business decisions. Roman lays out the key challenges of product leadership and shows us ways of thoughtfully working with team members, stakeholders, partners, and the inevitable conflicts. ~Rich Mironov, CEO of Mironov Consulting and Smokejumper Head of Product |
| agile story writing best practices: Scaling Software Agility Dean Leffingwell, 2007-02-26 “Companies have been implementing large agile projects for a number of years, but the ‘stigma’ of ‘agile only works for small projects’ continues to be a frequent barrier for newcomers and a rallying cry for agile critics. What has been missing from the agile literature is a solid, practical book on the specifics of developing large projects in an agile way. Dean Leffingwell’s book Scaling Software Agility fills this gap admirably. It offers a practical guide to large project issues such as architecture, requirements development, multi-level release planning, and team organization. Leffingwell’s book is a necessary guide for large projects and large organizations making the transition to agile development.” —Jim Highsmith, director, Agile Practice, Cutter Consortium, author of Agile Project Management “There’s tension between building software fast and delivering software that lasts, between being ultra-responsive to changes in the market and maintaining a degree of stability. In his latest work, Scaling Software Agility, Dean Leffingwell shows how to achieve a pragmatic balance among these forces. Leffingwell’s observations of the problem, his advice on the solution, and his description of the resulting best practices come from experience: he’s been there, done that, and has seen what’s worked.” —Grady Booch, IBM Fellow Agile development practices, while still controversial in some circles, offer undeniable benefits: faster time to market, better responsiveness to changing customer requirements, and higher quality. However, agile practices have been defined and recommended primarily to small teams. In Scaling Software Agility, Dean Leffingwell describes how agile methods can be applied to enterprise-class development. Part I provides an overview of the most common and effective agile methods. Part II describes seven best practices of agility that natively scale to the enterprise level. Part III describes an additional set of seven organizational capabilities that companies can master to achieve the full benefits of software agility on an enterprise scale. This book is invaluable to software developers, testers and QA personnel, managers and team leads, as well as to executives of software organizations whose objective is to increase the quality and productivity of the software development process but who are faced with all the challenges of developing software on an enterprise scale. |
| agile story writing best practices: Getting and Writing IT Requirements in a Lean and Agile World Thomas and Angela Hathaway, 2019-07-15 WHAT IS THIS BOOK ABOUT? Communicate Business Needs in an Agile (e.g. Scrum) or Lean (e.g. Kanban) Environment Problem solvers are in demand in every organization, large and small, from a Mom and Pop shop to the federal government. Increase your confidence and your value to organizations by improving your ability to analyze, extract, express, and discuss business needs in formats supported by Agile, Lean, and DevOps. The single largest challenge facing organizations around the world is how to leverage their Information Technology to gain competitive advantage. This is not about how to program the devices; it is figuring out what the devices should do. The skills needed to identify and define the best IT solutions are invaluable for every role in the organization. These skills can propel you from the mail room to the boardroom by making your organization more effective and more profitable. Whether you: - are tasked with defining business needs for a product or existing software, - need to prove that a digital solution works, - want to expand your User Story and requirements discovery toolkit, or - are interested in becoming a Business Analyst, this book presents invaluable ideas that you can steal. The future looks bright for those who embrace Lean concepts and are prepared to engage with the business community to ensure the success of Agile initiatives. WHAT YOU WILL LEARN Learn Step by Step When and How to Define Lean / Agile Requirements Agile, Lean, DevOps, and Continuous Delivery do not change the need for good business analysis. In this book, you will learn how the new software development philosophies influence the discovery, expression, and analysis of business needs. We will cover User Stories, Features, and Quality Requirements (a.k.a. Non-functional Requirements – NFR). User Story Splitting and Feature Drill-down transform business needs into technology solutions. Acceptance Tests (Scenarios, Scenario Outlines, and Examples) have become a critical part of many Lean development approaches. To support this new testing paradigm, you will also learn how to identify and optimize Scenarios, Scenario Outlines, and Examples in GIVEN-WHEN-THEN format (Gherkin) that are the bases for Acceptance Test Driven Development (ATDD) and Behavior Driven Development (BDD). This book presents concrete approaches that take you from day one of a change initiative to the ongoing acceptance testing in a continuous delivery environment. The authors introduce novel and innovative ideas that augment tried-and-true techniques for: - discovering and capturing what your stakeholders need, - writing and refining the needs as the work progresses, and - developing scenarios to verify that the software does what it should. Approaches that proved their value in conventional settings have been redefined to ferret out and eliminate waste (a pillar of the Lean philosophy). Those approaches are fine-tuned and perfected to support the Lean and Agile movement that defines current software development. In addition, the book is chock-full of examples and exercises that allow you to confirm your understanding of the presented ideas. WHO WILL BENEFIT FROM READING THIS BOOK? How organizations develop and deliver working software has changed significantly in recent years. Because the change was greatest in the developer community, many books and courses justifiably target that group. There is, however, an overlooked group of people essential to the development of software-as-an-asset that have been neglected. Many distinct roles or job titles in the business community perform business needs analysis for digital solutions. They include: - Product Owners - Business Analysts - Requirements Engineers - Test Developers - Business- and Customer-side Team Members - Agile Team Members - Subject Matter Experts (SME) - Project Leaders and Managers - Systems Analysts and Designers - AND “anyone wearing the business analysis hat”, meaning anyone responsible for defining a future IT solution TOM AND ANGELA’S (the authors) STORY Like all good IT stories, theirs started on a project many years ago. Tom was the super techie, Angela the super SME. They fought their way through the 3-year development of a new policy maintenance system for an insurance company. They vehemently disagreed on many aspects, but in the process discovered a fundamental truth about IT projects. The business community (Angela) should decide on the business needs while the technical team’s (Tom)’s job was to make the technology deliver what the business needed. Talk about a revolutionary idea! All that was left was learning how to communicate with each other without bloodshed to make the project a resounding success. Mission accomplished. They decided this epiphany was so important that the world needed to know about it. As a result, they made it their mission (and their passion) to share this ground-breaking concept with the rest of the world. To achieve that lofty goal, they married and began the mission that still defines their life. After over 30 years of living and working together 24x7x365, they are still wildly enthusiastic about helping the victims of technology learn how to ask for and get the IT solutions they need to do their jobs better. More importantly, they are more enthusiastically in love with each other than ever before! |
| agile story writing best practices: Lean Software Development Mary Poppendieck, Tom Poppendieck, 2003-05-08 Lean Software Development: An Agile Toolkit Adapting agile practices to your development organization Uncovering and eradicating waste throughout the software development lifecycle Practical techniques for every development manager, project manager, and technical leader Lean software development: applying agile principles to your organization In Lean Software Development, Mary and Tom Poppendieck identify seven fundamental lean principles, adapt them for the world of software development, and show how they can serve as the foundation for agile development approaches that work. Along the way, they introduce 22 thinking tools that can help you customize the right agile practices for any environment. Better, cheaper, faster software development. You can have all three–if you adopt the same lean principles that have already revolutionized manufacturing, logistics and product development. Iterating towards excellence: software development as an exercise in discovery Managing uncertainty: decide as late as possible by building change into the system. Compressing the value stream: rapid development, feedback, and improvement Empowering teams and individuals without compromising coordination Software with integrity: promoting coherence, usability, fitness, maintainability, and adaptability How to see the whole–even when your developers are scattered across multiple locations and contractors Simply put, Lean Software Development helps you refocus development on value, flow, and people–so you can achieve breakthrough quality, savings, speed, and business alignment. |
| agile story writing best practices: Extreme Programming Explored William C. Wake, 2002 You know what XP is, how to get it up and running, and how to plan projects using it. Now it's time to expand your use of Extreme Programming and learn the best practices of this popular discipline. In Extreme Programming Explored, you can read about best practices as learned from the concrete experience of successful XP developers. Author and programmer Bill Wake provides answers to practical questions about XP implementation. Using hands-on examples--including code samples written in the Java programming language--this book demonstrates the day-to-day mechanics of working on an XP team and shows well-defined methods for carrying out a successful XP project. The book is divided into three parts: Part 1, Programming--programming incrementally, test-first, and refactoring. Part 2, Team Practices--code ownership, integration, overtime, and pair programming; how XP approaches system architecture; and how a system metaphor shapes a common vision, a shared vocabulary, and the architecture. Part 3, Processes--how to write stories to plan a release; how to plan iterations; and the activities in a typical day for the customer, the programmer, and the manager of an XP project. To demonstrate how an XP team uses frequent testing, you'll learn how to develop the core of a library search system by unit testing in small increments. To show how to make code ready for major design changes, the author teaches you how to refactor a Java program that generates a Web page. To see how a system metaphor influences the shape of a system, you'll learn about the effects of different metaphors on customer service and word processing applications. To show how customers and programmers participate in release planning, the book demonstrates writing and estimating stories, and shows how the customer plans a release. 0201733978B07052001 |
| agile story writing best practices: The Project Manager's Guide to Mastering Agile Charles G. Cobb, 2015-01-05 Streamline project workflow with expert agile implementation The Project Management Profession is beginning to go through rapid and profound transformation due to the widespread adoption of agile methodologies. Those changes are likely to dramatically change the role of project managers in many environments as we have known them and raise the bar for the entire project management profession; however, we are in the early stages of that transformation and there is a lot of confusion about the impact it has on project managers: There are many stereotypes and misconceptions that exist about both Agile and traditional plan-driven project management, Agile and traditional project management principles and practices are treated as separate and independent domains of knowledge with little or no integration between the two and sometimes seen as in conflict with each other Agile and Waterfall are thought of as two binary, mutually-exclusive choices and companies sometimes try to force-fit their business and projects to one of those extremes when the right solution is to fit the approach to the project It’s no wonder that many Project Managers might be confused by all of this! This book will help project managers unravel a lot of the confusion that exists; develop a totally new perspective to see Agile and traditional plan-driven project management principles and practices in a new light as complementary to each other rather than competitive; and learn to develop an adaptive approach to blend those principles and practices together in the right proportions to fit any situation. There are many books on Agile and many books on traditional project management but what’s very unique about this book is that it takes an objective approach to help you understand the strengths and weaknesses of both of those areas to see how they can work synergistically to improve project outcomes in any project. The book includes discussion topics, real world case studies, and sample enterprise-level agile frameworks that facilitate hands-on learning as well as an in-depth discussion of the principles behind both Agile and traditional plan-driven project management practices to provide a more thorough level of understanding. |
| agile story writing best practices: ADKAR Jeff Hiatt, 2006 In his first complete text on the ADKAR model, Jeff Hiatt explains the origin of the model and explores what drives each building block of ADKAR. Learn how to build awareness, create desire, develop knowledge, foster ability and reinforce changes in your organization. The ADKAR Model is changing how we think about managing the people side of change, and provides a powerful foundation to help you succeed at change. |
| agile story writing best practices: The Fourth Industrial Revolution Klaus Schwab, 2017-01-03 World-renowned economist Klaus Schwab, Founder and Executive Chairman of the World Economic Forum, explains that we have an opportunity to shape the fourth industrial revolution, which will fundamentally alter how we live and work. Schwab argues that this revolution is different in scale, scope and complexity from any that have come before. Characterized by a range of new technologies that are fusing the physical, digital and biological worlds, the developments are affecting all disciplines, economies, industries and governments, and even challenging ideas about what it means to be human. Artificial intelligence is already all around us, from supercomputers, drones and virtual assistants to 3D printing, DNA sequencing, smart thermostats, wearable sensors and microchips smaller than a grain of sand. But this is just the beginning: nanomaterials 200 times stronger than steel and a million times thinner than a strand of hair and the first transplant of a 3D printed liver are already in development. Imagine “smart factories” in which global systems of manufacturing are coordinated virtually, or implantable mobile phones made of biosynthetic materials. The fourth industrial revolution, says Schwab, is more significant, and its ramifications more profound, than in any prior period of human history. He outlines the key technologies driving this revolution and discusses the major impacts expected on government, business, civil society and individuals. Schwab also offers bold ideas on how to harness these changes and shape a better future—one in which technology empowers people rather than replaces them; progress serves society rather than disrupts it; and in which innovators respect moral and ethical boundaries rather than cross them. We all have the opportunity to contribute to developing new frameworks that advance progress. |
| agile story writing best practices: Coaching Agile Teams Lyssa Adkins, 2010-05-18 The Provocative and Practical Guide to Coaching Agile Teams As an agile coach, you can help project teams become outstanding at agile, creating products that make them proud and helping organizations reap the powerful benefits of teams that deliver both innovation and excellence. More and more frequently, ScrumMasters and project managers are being asked to coach agile teams. But it’s a challenging role. It requires new skills—as well as a subtle understanding of when to step in and when to step back. Migrating from “command and control” to agile coaching requires a whole new mind-set. In Coaching Agile Teams, Lyssa Adkins gives agile coaches the insights they need to adopt this new mind-set and to guide teams to extraordinary performance in a re-energized work environment. You’ll gain a deep view into the role of the agile coach, discover what works and what doesn’t, and learn how to adapt powerful skills from many allied disciplines, including the fields of professional coaching and mentoring. Coverage includes Understanding what it takes to be a great agile coach Mastering all of the agile coach’s roles: teacher, mentor, problem solver, conflict navigator, and performance coach Creating an environment where self-organized, high-performance teams can emerge Coaching teams past cooperation and into full collaboration Evolving your leadership style as your team grows and changes Staying actively engaged without dominating your team and stunting its growth Recognizing failure, recovery, and success modes in your coaching Getting the most out of your own personal agile coaching journey Whether you’re an agile coach, leader, trainer, mentor, facilitator, ScrumMaster, project manager, product owner, or team member, this book will help you become skilled at helping others become truly great. What could possibly be more rewarding? |
| agile story writing best practices: Agile Software Development Ecosystems James A. Highsmith, 2002 Traditional software development methods struggle to keep pace with the accelerated pace and rapid change of Internet-era development. Several agile methodologies have been developed in response -- and these approaches to software development are showing exceptional promise. In this book, Jim Highsmith covers them all -- showing what they have in common, where they differ, and how to choose and customize the best agile approach for your needs.KEY TOPICS:Highsmith begins by introducing the values and principles shared by virtually all agile software development methods. He presents detailed case studies from organizations that have used them, as well as interviews with each method's principal authors or leading practitioners. Next, he takes a closer look at the key features and techniques associated with each major Agile approach: Extreme Programming (XP), Crystal Methods, Scrum, Dynamic Systems Development Method (DSDM), Lean Development, Adaptive Software Development (ASD), and Feature-Driven Development (FDD). In Part III, Highsmith offers practical advice on customizing the optimal agile discipline for your own organization.MARKET:For all software developers, project managers, and other IT professionals seeking more flexible, effective approaches to developing software. |
| agile story writing best practices: Agile Testing Lisa Crispin, Janet Gregory, 2009 Crispin and Gregory define agile testing and illustrate the tester's role with examples from real agile teams. They teach you how to use the agile testing quadrants to identify what testing is needed, who should do it, and what tools might help. The book chronicles an agile software development iteration from the viewpoint of a tester and explains the seven key success factors of agile testing. |
| agile story writing best practices: The Great Mental Models, Volume 1 Shane Parrish, Rhiannon Beaubien, 2024-10-15 Discover the essential thinking tools you’ve been missing with The Great Mental Models series by Shane Parrish, New York Times bestselling author and the mind behind the acclaimed Farnam Street blog and “The Knowledge Project” podcast. This first book in the series is your guide to learning the crucial thinking tools nobody ever taught you. Time and time again, great thinkers such as Charlie Munger and Warren Buffett have credited their success to mental models–representations of how something works that can scale onto other fields. Mastering a small number of mental models enables you to rapidly grasp new information, identify patterns others miss, and avoid the common mistakes that hold people back. The Great Mental Models: Volume 1, General Thinking Concepts shows you how making a few tiny changes in the way you think can deliver big results. Drawing on examples from history, business, art, and science, this book details nine of the most versatile, all-purpose mental models you can use right away to improve your decision making and productivity. This book will teach you how to: Avoid blind spots when looking at problems. Find non-obvious solutions. Anticipate and achieve desired outcomes. Play to your strengths, avoid your weaknesses, … and more. The Great Mental Models series demystifies once elusive concepts and illuminates rich knowledge that traditional education overlooks. This series is the most comprehensive and accessible guide on using mental models to better understand our world, solve problems, and gain an advantage. |
| agile story writing best practices: Agile Project Management with Scrum Ken Schwaber, 2004-02-11 The rules and practices for Scrum—a simple process for managing complex projects—are few, straightforward, and easy to learn. But Scrum’s simplicity itself—its lack of prescription—can be disarming, and new practitioners often find themselves reverting to old project management habits and tools and yielding lesser results. In this illuminating series of case studies, Scrum co-creator and evangelist Ken Schwaber identifies the real-world lessons—the successes and failures—culled from his years of experience coaching companies in agile project management. Through them, you’ll understand how to use Scrum to solve complex problems and drive better results—delivering more valuable software faster. Gain the foundation in Scrum theory—and practice—you need to: Rein in even the most complex, unwieldy projects Effectively manage unknown or changing product requirements Simplify the chain of command with self-managing development teams Receive clearer specifications—and feedback—from customers Greatly reduce project planning time and required tools Build—and release—products in 30-day cycles so clients get deliverables earlier Avoid missteps by regularly inspecting, reporting on, and fine-tuning projects Support multiple teams working on a large-scale project from many geographic locations Maximize return on investment! |
| agile story writing best practices: Clean Agile Robert C. Martin, 2019-09-12 Agile Values and Principles for a New Generation “In the journey to all things Agile, Uncle Bob has been there, done that, and has the both the t-shirt and the scars to show for it. This delightful book is part history, part personal stories, and all wisdom. If you want to understand what Agile is and how it came to be, this is the book for you.” –Grady Booch “Bob’s frustration colors every sentence of Clean Agile, but it’s a justified frustration. What is in the world of Agile development is nothing compared to what could be. This book is Bob’s perspective on what to focus on to get to that ‘what could be.’ And he’s been there, so it’s worth listening.” –Kent Beck “It’s good to read Uncle Bob’s take on Agile. Whether just beginning, or a seasoned Agilista, you would do well to read this book. I agree with almost all of it. It’s just some of the parts make me realize my own shortcomings, dammit. It made me double-check our code coverage (85.09%).” –Jon Kern Nearly twenty years after the Agile Manifesto was first presented, the legendary Robert C. Martin (“Uncle Bob”) reintroduces Agile values and principles for a new generation–programmers and nonprogrammers alike. Martin, author of Clean Code and other highly influential software development guides, was there at Agile’s founding. Now, in Clean Agile: Back to Basics, he strips away misunderstandings and distractions that over the years have made it harder to use Agile than was originally intended. Martin describes what Agile is in no uncertain terms: a small discipline that helps small teams manage small projects . . . with huge implications because every big project is comprised of many small projects. Drawing on his fifty years’ experience with projects of every conceivable type, he shows how Agile can help you bring true professionalism to software development. Get back to the basics–what Agile is, was, and should always be Understand the origins, and proper practice, of SCRUM Master essential business-facing Agile practices, from small releases and acceptance tests to whole-team communication Explore Agile team members’ relationships with each other, and with their product Rediscover indispensable Agile technical practices: TDD, refactoring, simple design, and pair programming Understand the central roles values and craftsmanship play in your Agile team’s success If you want Agile’s true benefits, there are no shortcuts: You need to do Agile right. Clean Agile: Back to Basics will show you how, whether you’re a developer, tester, manager, project manager, or customer. Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details. |
| agile story writing best practices: Agile Analytics Ken Collier, 2012 Using Agile methods, you can bring far greater innovation, value, and quality to any data warehousing (DW), business intelligence (BI), or analytics project. However, conventional Agile methods must be carefully adapted to address the unique characteristics of DW/BI projects. In Agile Analytics, Agile pioneer Ken Collier shows how to do just that. Collier introduces platform-agnostic Agile solutions for integrating infrastructures consisting of diverse operational, legacy, and specialty systems that mix commercial and custom code. Using working examples, he shows how to manage analytics development teams with widely diverse skill sets and how to support enormous and fast-growing data volumes. Collier's techniques offer optimal value whether your projects involve back-end data management, front-end business analysis, or both. Part I focuses on Agile project management techniques and delivery team coordination, introducing core practices that shape the way your Agile DW/BI project community can collaborate toward success Part II presents technical methods for enabling continuous delivery of business value at production-quality levels, including evolving superior designs; test-driven DW development; version control; and project automation Collier brings together proven solutions you can apply right now--whether you're an IT decision-maker, data warehouse professional, database administrator, business intelligence specialist, or database developer. With his help, you can mitigate project risk, improve business alignment, achieve better results--and have fun along the way. |
| agile story writing best practices: Mindset Carol S. Dweck, 2007-12-26 From the renowned psychologist who introduced the world to “growth mindset” comes this updated edition of the million-copy bestseller—featuring transformative insights into redefining success, building lifelong resilience, and supercharging self-improvement. “Through clever research studies and engaging writing, Dweck illuminates how our beliefs about our capabilities exert tremendous influence on how we learn and which paths we take in life.”—Bill Gates, GatesNotes “It’s not always the people who start out the smartest who end up the smartest.” After decades of research, world-renowned Stanford University psychologist Carol S. Dweck, Ph.D., discovered a simple but groundbreaking idea: the power of mindset. In this brilliant book, she shows how success in school, work, sports, the arts, and almost every area of human endeavor can be dramatically influenced by how we think about our talents and abilities. People with a fixed mindset—those who believe that abilities are fixed—are less likely to flourish than those with a growth mindset—those who believe that abilities can be developed. Mindset reveals how great parents, teachers, managers, and athletes can put this idea to use to foster outstanding accomplishment. In this edition, Dweck offers new insights into her now famous and broadly embraced concept. She introduces a phenomenon she calls false growth mindset and guides people toward adopting a deeper, truer growth mindset. She also expands the mindset concept beyond the individual, applying it to the cultures of groups and organizations. With the right mindset, you can motivate those you lead, teach, and love—to transform their lives and your own. |
| agile story writing best practices: The Software Craftsman Sandro Mancuso, 2014-12-14 In The Software Craftsman, Sandro Mancuso explains what craftsmanship means to the developer and his or her organization, and shows how to live it every day in your real-world development environment. Mancuso shows how software craftsmanship fits with and helps students improve upon best-practice technical disciplines such as agile and lean, taking all development projects to the next level. Readers will learn how to change the disastrous perception that software developers are the same as factory workers, and that software projects can be run like factories. |
| agile story writing best practices: The Surprising Power of Liberating Structures Henri Lipmanowicz, Keith McCandless, 2014-10-28 Smart leaders know that they would greatly increase productivity and innovation if only they could get everyone fully engaged. So do professors, facilitators and all changemakers. The challenge is how. Liberating Structures are novel, practical and no-nonsense methods to help you accomplish this goal with groups of any size. Prepare to be surprised by how simple and easy they are for anyone to use. This book shows you how with detailed descriptions for putting them into practice plus tips on how to get started and traps to avoid. It takes the design and facilitation methods experts use and puts them within reach of anyone in any organization or initiative, from the frontline to the C-suite. Part One: The Hidden Structure of Engagement will ground you with the conceptual framework and vocabulary of Liberating Structures. It contrasts Liberating Structures with conventional methods and shows the benefits of using them to transform the way people collaborate, learn, and discover solutions together. Part Two: Getting Started and Beyond offers guidelines for experimenting in a wide range of applications from small group interactions to system-wide initiatives: meetings, projects, problem solving, change initiatives, product launches, strategy development, etc. Part Three: Stories from the Field illustrates the endless possibilities Liberating Structures offer with stories from users around the world, in all types of organizations -- from healthcare to academic to military to global business enterprises, from judicial and legislative environments to R&D. Part Four: The Field Guide for Including, Engaging, and Unleashing Everyone describes how to use each of the 33 Liberating Structures with step-by-step explanations of what to do and what to expect. Discover today what Liberating Structures can do for you, without expensive investments, complicated training, or difficult restructuring. Liberate everyone's contributions -- all it takes is the determination to experiment. |
| agile story writing best practices: The Treaty of Waitangi Claudia Orange, 2015-12-21 The Treaty of Waitangi was signed in 1840 by over 500 chiefs, and by William Hobson, representing the British Crown. To the British it was the means by which they gained sovereignty over New Zealand. But to Maori people it had a very different significance, and they are still affected by the terms of the Treaty, often adversely.The Treaty of Waitangi, the first comprehensive study of the Treaty, deals with its place in New Zealand history from its making to the present day. The story covers the several Treaty signings and the substantial differences between Maori and English texts; the debate over interpretation of land rights and the actions of settler governments determined to circumvent Treaty guarantees; the wars of sovereignty in the 1860s and the longstanding Maori struggle to secure a degree of autonomy and control over resources. --Publisher. |
| agile story writing best practices: Implementing Lean Software Development Mary Poppendieck, Thomas David Poppendieck, Tom Poppendieck, 2007 |
| agile story writing best practices: Strategize: Product Strategy and Product Roadmap Practices for the Digital Age Roman Pichler, 2022-09-07 Create a winning game plan for your digital products with Strategize: Product Strategy and Product Roadmap Practices for the Digital Age, 2nd edition. Using a wide range of proven techniques and tools, product management expert Roman Pichler explains how to create a winning product strategy and actionable roadmap. Comprehensive and insightful, the book will enable you to make the right strategic decisions in today’s dynamic digital age. If you work as a product manager, Scrum product owner, product portfolio manager, head of product, or product coach, then this book is for you. What you will learn: * Create an inspiring vision for your product. * Develop a product strategy that maximises the chances of launching a winning product. * Successfully adapt the strategy across the product life cycle to achieve sustained product success. * Measure the value your product creates using the right key performance indicators (KPIs). * Build an actionable outcome-based product roadmap that aligns stakeholders and directs the product backlog. * Regularly review the product strategy and roadmap and keep them up-to-date. Written in an engaging and easily accessible style, Strategize offers practical advice and valuable examples so that you can apply the practices directly to your products. This second, revised, and extended edition offers new concepts, more tools, and additional tips and examples. Praise for Strategize: Strategize offers a comprehensive approach to product strategy using the latest practices geared specifically to digital products. Not just theory, the book is chock-full of real-world examples, making it easier to apply the principles to your company and products. Strategize is essential reading for everyone in charge of products: product executives, product managers, and product owners. Steve Johnson, Founder at Under10 Consulting. Whether you are new to product management or an experienced practitioner, Strategize is a must read. You are guaranteed to get new ideas about how to develop or improve your product strategy and how to execute it successfully. It’s an essential addition to every product manager’s reading list. Marc Abraham, Senior Group Product Manager at Intercom. |
| agile story writing best practices: Turn Ideas Into Products Steve Johnson, 2017-04-02 We've all heard stories of amazing product successes: the brilliant college kid who started a business in his dorm room; the team who built a business from the back of a napkin with just a few friends and sold it for millions. Yet for every amazing success story, there are thousands of stories of products that went nowhere. Most of us aren't looking at billion-dollar valuations; we're not looking for an exit. Instead we have a few ideas -- some innovative, some not -- and we're trying to determine which to pursue. Likely, you're working for a company today and you need a step-by-step approach to turn ideas, regardless of their source, into businesses. In Turn Ideas into Products, author Steve Johnson introduces a nimble idea-to-market process with strong emphasis on personal experience with customers. From business planning to product launch, this approach for managing products empowers your product team to work smarter and collaborate better with colleagues and customers. |
| agile story writing best practices: White Awareness Judy H. Katz, 1978 Stage 1. |
| agile story writing best practices: Jobs to Be Done Anthony W. Ulwick, 2016-10-25 Why do some innovation projects succeed where others fail? The book reveals the business implications of Jobs Theory and explains how to put Jobs Theory into practice using Outcome-Driven Innovation. |
| agile story writing best practices: Train Thoughts Jay Sigler, 2018-04-04 When the person you love most in the world dies, it stays with you for the rest of your life. When that person is brutally murdered with no explanation, it fundamentally changes who you are at your core. The loneliness, confusion, and anger fuel your nightmares and consume your being. With nothing else to lose, how far would you descend into the twisted pit of madness and despair to uncover the truth? |
什么是 Agile Software Development（敏捷软件开发）？ - 知乎
Apr 16, 2014 · 既然题主问的是“Agile Methodology”,那么便应该比限定在“软件开发”领域要更加宽泛。本回答从“敏捷开发”出发，尝试解读究竟什么才是“敏捷”。 一、从“敏捷开发”说起 “敏捷” …
什么是芯片领域的“敏捷设计（Agile Development - 知乎
什么是芯片领域的“敏捷设计（Agile Development）”？ 引用矽说公众号对DARPA资助项目的解说；也有提到RISCV，CHISEL等字眼。 敏捷设计与超高效计算芯片，DARPA为未来半导体发 …
请问路由器双频合一开了好还是不开好？ - 知乎
说实在的。。。这个问题要看具体场景，没什么确定性的答案。就我自己而言，一般都是开着的。除非是我自己这边设备很多，要做隔离优化网络的时候，否则不会手动去把双频分开来。 双 …
什么是 Agile Software Development（敏捷软件开发）？ - 知乎
Apr 16, 2014 · 既然题主问的是“Agile Methodology”,那么便应该比限定在“软件开发”领域要更加宽泛。本回答从“敏捷开发”出发，尝试解读究竟什么才是“敏捷”。 一、从“敏捷开发”说起 “敏捷” …
什么是芯片领域的“敏捷设计（Agile Development - 知乎
什么是芯片领域的“敏捷设计（Agile Development）”？ 引用矽说公众号对DARPA资助项目的解说；也有提到RISCV，CHISEL等字眼。 敏捷设计与超高效计算芯片，DARPA为未来半导体发 …
请问路由器双频合一开了好还是不开好？ - 知乎
说实在的。。。这个问题要看具体场景，没什么确定性的答案。就我自己而言，一般都是开着的。除非是我自己这边设备很多，要做隔离优化网络的时候，否则不会手动去把双频分开来。 双 …
