Author: Scott W. Ambler
Publisher: IBM Press
Release Date: 2012
The authoritative guide to DAD, IBM's disciplined approach to applying agile practices in enterprise scale projects. Integrate enterprise discipline with powerful, widely-used agile practices into a proven solution for the entire software lifecycle. Scale agile strategies for complex development challenges, without compromising agile's advantages.
Introduction to Disciplined Agile Delivery 2nd Edition provides a quick overview of how agile software development works from beginning-to-end. It describes Disciplined Agile Delivery (DAD), the first of four levels of the Disciplined Agile (DA) process decision framework, and works through a case study describing a typical agile team's experiences adopting a DA approach. The book describes how the team develops the first release of a mission-critical application while working in a legacy enterprise environment. It describes their experiences from beginning-to-end, starting with their initial team initiation efforts through construction and finally to deploying the solution into production. It also describes how the team stays together for future releases, overviewing their process improvement efforts from their Scrum-based beginnings through to a lean continuous delivery approach that fits in with their organization's evolving DevOps strategy. The DAD framework is a hybrid of existing methods such as Scrum, Kanban, Agile Modeling, SAFe, Extreme Programming, Agile Data, Unified Process and many others. DAD provides the flexibility to use various approaches and plugs the gaps not addressed by mainstream agile methods. In a nutshell, DAD is "pragmatic agile." DAD describes proven strategies to adapt and scale your agile initiatives to suit the unique realities of your enterprise without having to figure it all out by yourself. Here's an overview of what each chapter covers: Chapter 1: Introduction. This chapter provides a quick overview of the book and a brief history of Disciplined Agile. Chapter 2: Reality over Rhetoric. This chapter explores several common myths about DAD and more importantly disproves them. Chapter 3: Disciplined Agile Delivery in a Nutshell. This chapter provides a brief yet comprehensive overview of DAD. Chapter 4: Introduction to the Case Study. This chapter introduces us to the team, describes the market opportunity that they hope to address, and describes the environment in which they're working. Chapter 5: Inception. The team's initiation effort includes initial requirements modeling and planning with their stakeholders in a streamlined manner, initial architecture modeling, setting up their physical work environment, setting up the start of their tooling infrastructure, initial risk identification, and finally securing stakeholder support and funding for the rest of the first release. Chapters 6 through 10: Construction. These chapters each describe a single Construction iteration, sharing the team's experiences during each of those two-week timeboxes. Chapter 11: Transition. The two-week transition phase focuses on final testing and fixing, training the support/help-desk staff, finishing a few short end-user "how to" videos, and deploying the solution into production. Chapter 12: The Road to Disciplined DevOps. This chapter overviews the team's improvement efforts over the next few releases, describing how they evolve from the agile Scrum-based lifecycle to a leaner approach and eventually to continuous delivery. All of this dovetails into their organization's efforts to implement a Disciplined DevOps strategy. Chapter 13: Closing Thoughts. This chapter overviews the disciplined agile resources that are available to you. Appendix: The Disciplined Agile Framework. This short appendix overviews our ongoing work on the Disciplined Agile framework to address the full scope of an agile business. At 111 pages, you should find this book to be a quick, informative read. What's Different in This Edition: Chapter 3 was completely rewritten to reflect the changes to DAD. Chapter 12 was rewritten to describe how the team evolved into a Disciplined DevOps strategy. Appendix A was rewritten to reflect the latest release of the DA framework. General updates were made throughout the book.
Introduction to Disciplined Agile Delivery provides a quick overview of how agile software development works from beginning-to-end. It describes the Disciplined Agile Delivery (DAD) process decision framework and then works through a case study describing a typical agile team's experiences adopting a disciplined agile approach. The book describes how the team develops the first release of a mission-critical application while working in a legacy enterprise environment. It describes their experiences from beginning-to-end, starting with their initial team initiation efforts through construction and finally to deploying the solution into production. It also describes how the team stays together for future releases, overviewing their process improvement efforts from their Scrum-based beginnings through to a lean continuous delivery approach that fits in with their organization's evolving DevOps strategy. The DAD framework is a hybrid of existing methods such as Scrum, Kanban, Agile Modeling, SAFe, Extreme Programming, Agile Data, Unified Process and many others. DAD provides the flexibility to use various approaches and plugs the gaps not addressed by mainstream agile methods. In a nutshell, DAD is "pragmatic agile." DAD describes proven strategies to adapt and scale your agile initiatives to suit the unique realities of your enterprise without having to figure it all out by yourself. Here's an overview of what each chapter covers: * Chapter 1: Introduction. This chapter provides a quick overview of the book and a brief history of Disciplined Agile. * Chapter 2: Reality over Rhetoric. This chapter explores several common myths about DAD and more importantly disproves them. * Chapter 3: Disciplined Agile Delivery in a Nutshell. This chapter provides a brief yet comprehensive overview of the DAD framework. * Chapter 4: Introduction to the Case Study. This chapter introduces us to the team, describes the market opportunity that they hope to address, and describes the environment in which they're working. * Chapter 5: Inception. The team's initiation effort includes initial requirements modeling and planning with their stakeholders in a streamlined manner, initial architecture modeling, setting up their physical work environment, setting up the start of their tooling infrastructure, initial risk identification, and finally securing stakeholder support and funding for the rest of the first release. * Chapters 6 through 10: Construction. These chapters each describe a single Construction iteration, sharing the team's experiences during each of those two-week timeboxes. * Chapter 11: Transition. The two-week transition phase focuses on final testing and fixing, training the support/help-desk staff, finishing a few short end-user "how to" videos, and deploying the solution into production. * Chapter 12: Future Releases. This chapter overviews the team's improvement efforts over the next few releases, describing how they evolve from the agile Scrum-based lifecycle to a leaner approach and eventually to continuous delivery. * Chapter 13: Closing Thoughts. This chapter overviews the disciplined agile resources that are available to you. * Appendix: The Disciplined Agile IT Department. This short appendix overviews our ongoing work on the Disciplined Agile framework to address the full scope of an IT department. At 102 pages, you should find this book to be a quick, informative read.
The agile community has figured out how to build and then continually improve very high-performance software development teams. This is akin to creating a race car engine and then evolving it to get more power, better fuel efficiency, and greater speed. Sadly in many cases we take these great engines, put them into an organizational tractor, and then complain that we're not winning the race. What we need to do is take our great race car engines (our development teams), put them into a race car (a DevOps ecosystem), have a great pit crew and driver (an effective IT organization), and then provide somewhere to race (an organization that can leverage IT to make money). That's what this book is all about - Moving from optimizing team performance to optimizing the entire enterprise. Business agility - being an adaptive, lean, responsive, and learning organization - is the race that enterprises need to win today. Yet there is no quick fix, no silver bullet, to attain business agility. This is a multi-year journey requiring hard work, experimentation, and most importantly a willingness to improve. The Disciplined Agile framework lowers risks and provides a path to accelerate your journey to business agility. The framework is unique in that it is the only one that puts all the pieces together into a cohesive enterprise roadmap for business agility transformation. This book begins with an overview of the challenges and opportunities that organizations face. We then describe seven principles that provide the underpinnings of the Disciplined Agile framework. Then the book works through Disciplined Agile Delivery (how to build a world-class engine), Disciplined DevOps (the race car), Disciplined Agile IT (the race car and its team), and what it means to be a Disciplined Agile Enterprise (the racing business). The book ends with a plan for starting with an Agile transformation and then evolving into a long-term continuous improvement strategy. Do you have the discipline it takes to win the race to business agility?
This book constitutes the refereed proceedings of the scientific track of the 8th Software Quality Days Conference, SWQD 2016, held in Vienna, Austria, in January 2016. The SWQD conference offers a range of comprehensive and valuable information by presenting new ideas from the latest research papers, keynote speeches by renowned academics and industry leaders, professional lectures, exhibits, and tutorials. The five scientific full papers accepted for SWQD were each peer reviewed by three or more reviewers and selected out of 13 high-quality submissions. Further, nine short papers were also presented and are included in this book. In addition, one keynote paper by Scott Ambler and Mark Lines is also included.
A Thorough Introduction to the Agile Framework and Methodologies That Are Used Worldwide Organizations of all shapes and sizes are embracing Agile methodologies as a way to transform their products, customer satisfaction, and employee engagement. Many people with varying levels of work experience are interested in understanding the architecture and nuances of Agile, but it is difficult to know where to start. Numerous practitioner books are available, but there has never been a single source for unbiased information about Agile methodologies–until now. Introduction to Agile Methods is the place to start for students and professionals who want to understand Agile and become conversant with Agile values, principles, framework, and processes. Authors Sondra Ashmore and Kristin Runyan use academic research and their own experiences with numerous Agile implementations to present a clear description of the essential concepts. They address all key roles and the entire development life cycle, including common roadblocks that must be overcome to be successful. Through the authors’ realistic use cases, practical examples, and thought-provoking interviews with pioneering practitioners, complex concepts are made relatable. No matter what your role or level of experience, this book provides a foundational understanding that can be used to start or enhance any Agile effort. Coverage includes How Agile compares with the Waterfall method and when to use each Why Agile demands a cultural transformation–and how that looks to each participant Comparing various Agile methodologies, including Scrum, Kanban, Extreme Programming (XP), Crystal, Feature Driven Development (FDD), Lean, and DSDM Understanding the roles within Agile and how they work together to create superior results Agile approaches to requirements gathering, planning, estimating, tracking, reporting, testing, quality, and integration Extending Agile beyond IT
Author: Charles G. Cobb
Publisher: John Wiley & Sons
Release Date: 2015-01-05
Genre: Business & Economics
Streamline project workflow with expert agile implementation The Project Management Profession is beginning to go throughrapid and profound transformation due to the widespread adoption ofagile methodologies. Those changes are likely to dramaticallychange the role of project managers in many environments as we haveknown them and raise the bar for the entire project managementprofession; however, we are in the early stages of thattransformation and there is a lot of confusion about the impact ithas on project managers: There are many stereotypes and misconceptions that exist aboutboth Agile and traditional plan-driven project management, Agile and traditional project management principles andpractices are treated as separate and independent domains ofknowledge with little or no integration between the two andsometimes 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-fittheir business and projects to one of those extremes when the rightsolution is to fit the approach to the project It’s no wonder that many Project Managers might beconfused by all of this! This book will help project managersunravel a lot of the confusion that exists; develop a totally newperspective to see Agile and traditional plan-driven projectmanagement principles and practices in a new light as complementaryto each other rather than competitive; and learn to develop anadaptive approach to blend those principles and practices togetherin the right proportions to fit any situation. There are many books on Agile and many books on traditionalproject management but what’s very unique about this book isthat it takes an objective approach to help you understand thestrengths and weaknesses of both of those areas to see how they canwork synergistically to improve project outcomes in anyproject. The book includes discussion topics, real world casestudies, and sample enterprise-level agile frameworks thatfacilitate hands-on learning as well as an in-depth discussion ofthe principles behind both Agile and traditional plan-drivenproject management practices to provide a more thorough level ofunderstanding.
In Scaling Agile: A Lean JumpStart, Sanjiv dives into the challenge of breaking down barriers to enterprise Agile adoption. He provides an essential set of Lean building blocks as a starting foundation for larger Agile scaling frameworks, including the Scaled Agile Framework (SAFe), Large-Scale Scrum (LeSS), and Disciplined Agile Delivery (DAD). Sanjiv provides step-by-step actions, with a keen focus on a few core Lean practices. With this JumpStart approach, the power is in your hands to apply Agile ideas from the team to the top, and to totally transform an organization. See the Ebook @ https: //leanpub.com/scalingagilealeanjumpstart
This book examines agile approaches from a management perspective by focusing on matters of strategy, implementation, organization and people. It examines the turbulence of the marketplace and business environment in order to identify what role agile management has to play in coping with such change and uncertainty. Based on observations, personal experience and extensive research, it clearly identifies the fabric of the agile organization, helping managers to become agile leaders in an uncertain world. The book opens with a broad survey of agile strategies, comparing and contrasting some of the major methodologies selected on the basis of where they lie on a continuum of ceremony and formality, ranging from the minimalist technique-driven and software engineering focused XP, to the pragmatic product-project paradigm that is Scrum and its scaled counterpart SAFe®, to the comparatively project-centric DSDM. Subsequently, the core of the book focuses on DSDM, owing to the method’s comprehensive elaboration of program and project management practices. This work will chiefly be of interest to all those with decision-making authority within their organizations (e.g., senior managers, line managers, program, project and risk managers) and for whom topics such as strategy, finance, quality, governance and risk management constitute a daily aspect of their work. It will, however, also be of interest to those readers in advanced management or business administration courses (e.g., MBA, MSc), who wish to engage in the management of agile organizations and thus need to adapt their skills and knowledge accordingly.
Author: Alan Moran
Publisher: Springer Science & Business Media
Release Date: 2014-03-18
This work is the definitive guide for IT managers and agile practitioners. It elucidates the principles of agile risk management and how these relate to individual projects. Explained in clear and concise terms, this synthesis of project risk management and agile techniques is illustrated using the major methodologies such as XP, Scrum and DSDM. Although the agile community frequently cites risk management, research suggests that risk is often narrowly defined and, at best, implicitly treated, which in turn leads to an inability to make informed decisions concerning risk and reward and a poor understanding of when to engage in risk-related activities. Moreover, the absence of reference to enterprise risk management means that project managers are unable to clearly articulate scope or tailor their projects in line with the wider expectations of the organisation. Yet the agile approach, with its rich toolset of techniques, is very well equipped to effectively and efficiently deal with the risks that arise in projects. Alan Moran addresses the above issues by proposing an agile risk-management process derived from classical risk management but adapted to the circumstances of agile projects. Though his main focus is on the software development process, much of what he describes could be applied to other types of IT projects as well. This book is intended for anyone who is serious about balancing risk and reward in the pursuit of value for their stakeholders, and in particular for those directly involved in agile software development who share a concern for how risk should be managed. Whilst a thorough background in risk management is not presumed, a basic level of familiarity with or exposure to agility is helpful.
Author: Doug Rose
Publisher: John Wiley & Sons
Release Date: 2018-02-28
Genre: Business & Economics
Manage and improve your organization's agile transformation Adopting an enterprise agile framework is a radical organizational change, and this book will help you get there without ever breaking a sweat. In Enterprise Agile For Dummies, you'll discover how to successfully choose and implement the right framework based on your organization's own unique culture. Organizational culture is one of the most overlooked challenges when trying to make a change to enterprise agile, and there are lots of resources out there that claim to have the perfect, one-size-fits-all solution. Luckily, this book takes a neutral stance and covers popular organizational change management techniques that you can implement to suit to your unique needs. Packed with step-by-step instruction and complemented with real-world case studies, this book offers everything you need to know in order to embrace a more agile mindset. Understand the benefits of an agile approach Pick the best enterprise agile framework for your organization Create a successful enterprise change management plan Let Enterprise Agile For Dummies help you optimize your business processes, and watch your productivity soar.
Today, the world is trying to create and educate data scientists because of the phenomenon of Big Data. And everyone is looking deeply into this technology. But no one is looking at the larger architectural picture of how Big Data needs to fit within the existing systems (data warehousing systems). Taking a look at the larger picture into which Big Data fits gives the data scientist the necessary context for how pieces of the puzzle should fit together. Most references on Big Data look at only one tiny part of a much larger whole. Until data gathered can be put into an existing framework or architecture it can’t be used to its full potential. Data Architecture a Primer for the Data Scientist addresses the larger architectural picture of how Big Data fits with the existing information infrastructure, an essential topic for the data scientist. Drawing upon years of practical experience and using numerous examples and an easy to understand framework. W.H. Inmon, and Daniel Linstedt define the importance of data architecture and how it can be used effectively to harness big data within existing systems. You’ll be able to: Turn textual information into a form that can be analyzed by standard tools. Make the connection between analytics and Big Data Understand how Big Data fits within an existing systems environment Conduct analytics on repetitive and non-repetitive data Discusses the value in Big Data that is often overlooked, non-repetitive data, and why there is significant business value in using it Shows how to turn textual information into a form that can be analyzed by standard tools. Explains how Big Data fits within an existing systems environment Presents new opportunities that are afforded by the advent of Big Data Demystifies the murky waters of repetitive and non-repetitive data in Big Data
Author: Paul E McMahon
Publisher: Pem Systems
Release Date: 2016-12-26
#1 Hot New Release Award Winner This book provides true software development stories that may challenge long held thinking. It highlights 26 upside down principles along with upside down principle clarifying thoughts. At the end of each story you will find extended clarifying thoughts in the summary sections. I also highlight 18 coaching tips that can help you get your organization "right side up" with respect to performance. If you are wondering if a book that highlights coaching tips is for you, it is. I believe everyone in an organization should view themselves as a coach. In order to help coaches everywhere, in Part II I have framed the highlighted principles and coaching tips that have materialized from my stories within a framework I like to use called Essence. I find Essence to be a remarkably straightforward medium for communicating software development practices and fostering collaboration, even among non-technical stakeholders. If you have not heard of Essence yet, you have probably heard of the foundation from which it evolved, which I explain further in Part II. I explain in the introduction how Essence relates to my stories and coaching tips. If you choose to read Part II, I think you will agree that Essence is quite useful for capturing and describing these lessons, tips and best practices. Praise for It's All Upside Down... "While reviewing this book, 99% of the time my feedback was either "this is exactly what I advise my clients" or "this is even better than what I've been advising." This book is full of pragmatic, insightful advice from the software process improvement trenches. Thanks Paul!" Scott Ambler Co-author of Disciplined Agile Delivery "Sometimes we're so heads-down focused on following a process or a so-called best practice, we don't stop to ask if it really makes sense. It's easy to forget that process maturity depends upon such organizational introspection. 'It's All Upside Down' challenges the reader to do just that. Reading this book is, well, exactly like having a coffee with a coach and bona fide subject matter expert on the practical matters of software development. Paul's conversational style makes for a comfortable read which you can tackle cover to cover or simply a story or tip at a time - and then reflect on how it informs you with respect to the challenges you confront in your own projects, helping you essentially stand on your head and see a perspective you couldn't see before - because it's all upside down." Michael Callihan President, AEGIS.net ..". Paul gives the reader the right amount of information, at the right time, following a story-telling narrative. Very nice and super informative. I just experienced several months of consulting in 3 hours from the comfort of my chair." John Ryskowski President, JFR Consulting, CMMI High Maturity Lead Appraiser Paul McMahon's latest book, "It's All Upside Down," expresses in words a thought that has been tickling the back of my mind for years; how we traditionally approach development has been acceptable, but there is a better way in many cases on how to practically proceed. Paul nails it with real world scenarios and solutions such that all readers may benefit from. Jim Convery, The Ascendancy Group, Former Director CMMIDEV and CMMI-SVC Maturity Level 3 Organization "There are few things as useful as a variety of perspectives on any given topic. This book does an outstanding job of showing non-traditional perspectives in areas where "herd thinking" and attitudes have excessively narrowed viewpoints. Supported by personal, highly interesting, true stories, the rationale for each of the "upside down" concepts is made clear, and recommendations are made for practical alternative thinking and action." Richard Bechtold, PhD, President, Abridge Technology Certified CMMI Lead Appraiser
Author: Gerard O'Regan
Publisher: Springer Science & Business Media
Release Date: 2010-12-16
This textbook is a systematic guide to the steps in setting up a Capability Maturity Model Integration (CMMI) improvement initiative. Readers will learn the project management practices necessary to deliver high-quality software solutions to the customer on time and on budget. The text also highlights how software process improvement can achieve specific business goals to provide a tangible return on investment. Topics and features: supplies review questions, summaries and key topics for each chapter, as well as a glossary of acronyms; describes the CMMI model thoroughly, detailing the five maturity levels; provides a broad overview of software engineering; reviews the activities and teams required to set up a CMMI improvement initiative; examines in detail the implementation of CMMI in a typical organization at each of the maturity levels; investigates the various tools that support organizations in improving their software engineering maturity; discusses the SCAMPI appraisal methodology.
With the introduction and popularization of Agile methods of software development, existing relationships and working agreements between user experience groups and developers are being disrupted. Agile methods introduce new concepts: the Product Owner, the Customer (but not the user), short iterations, User Stories. Where do UX professionals fit in this new world? Agile methods also bring a new mindset -- no big design, no specifications, minimal planning -- which conflict with the needs of UX design. This lecture discusses the key elements of Agile for the UX community and describes strategies UX people can use to contribute effectively in an Agile team, overcome key weaknesses in Agile methods as typically implemented, and produce a more robust process and more successful designs. We present a process combining the best practices of Contextual Design, a leading approach to user-centered design, with those of Agile development. Table of Contents: Introduction / Common Agile Methods / Agile Culture / Best Practices for Integrating UX with Agile / Structure of a User-Centered Agile Process / Structuring Projects / Conclusion