A book about building high-quality software solutions via engineering excellence, software architecture, and leadership best practices. * * * "This book is a must-read for both technical and non-technical readers: software engineers, architects, managers and even top-level executives. It will give you the tools you need to become an effective technology leader. The tools provided will apply whether your organization is focused on delivering software to external customers or has the need for internal solutions. The book has a no nonsense approach and provides concrete solutions to common obstacles to delivering a cost-effective and long-lived software solution." -- Dave Black, Solutions & Performance Architect, Black Box Solutions, Inc. * * * "I have been developing software for over 30 years, and based on that experience, I am confident that the modern comprehensive approach laid out in this book will work better than that in any environment I have seen to date. This is the book many of us have been waiting for. It is mostly based on Domain-Driven Design, which may seem counterintuitive to many at first, but the author astutely explains how it saves so much pain in the longer term, which thus maximizes ROI. It is highly relevant that the approach in this book is the product of the author's first-hand experience. There is nothing theoretical about it. It is entirely pragmatic. For example, it recognizes the purpose of profit. In fact, I found it to be more pragmatic than many other industry luminaries. All roles are covered, and in a way that is respectful to all of them. The first three sections are a must-read for non-technical team members, such as product owners. Its style and size make it a quick read with reference links to any deeper dives one may wish to make." -- Jim Hammond, Lead Developer, Kantar * * * "I have found this book to be an all-encompassing eye-opener about all-things software development, starting from requirements analysis through successful releases. As a technology leader, I think it is worth considering techniques demonstrated in the "Effective Software Development for Enterprise" in organizations that want to change and run engineering processes and teams in a more efficient manner that delivers business value and improves morale." -- Lasha Kochoradze, CTO at Nugios Technology * * * "I enjoyed reading the "Effective Software Development for Enterprise" because this is a unique book. Besides presenting techniques to implement Effective Software, the author tries to defeat the status quo and shift our mindset into a "what if" mode. This engraved passion and belief make the book a special one, which I would recommend to executives, architects, and other engineering leaders. I have seen and heard Tengiz succeed with the approaches he presents in this book. If he could do this, why can't anybody else?" -- Nugzar Nebieridze, Entrepreneur, Expert of Cybersecurity, Ex-CIO at Liberty Bank Georgia * * * "This book uncovers fundamental issues that are inherent to many large organizations. Take Agile teams as an example - they need to adapt to changes fast, but a confusing graph of dependencies makes it impossible to deliver features independently; how are they supposed to be agile then? Departments and groups are formed based on managerial preferences rather than the business problems that the company solves. Systems are built based on what is easy to develop rather than what is right to deliver. The "Effective Software Development for Enterprise" fearlessly exposes gaps in organizational structures, processes, and technical systems. Being an Agile practitioner for years, I think this publication is up-and-coming, and I look forward to seeing companies adopting these suggestions and forming more scalable teams, processes, and applications." -- Romana Stasiv, Agile Fellow

Metrics for software development are usually employed ad-hoc and without clear directions for interpreting the numbers and acting on them. Almost every other engineering discipline has clear guidelines for measuring processes and products and making decisions based on quantified evidence. This practical book describes how to integrate processes and metrics to ensure easier and more effective enterprise software development. It crosses the divide between theory and practice and also discusses why essential processes so often fail to deliver quality industrial software. Enterprise Software Development introduces the techniques for building, applying and interpreting metrics for the workflows across the software development life cycle phases of inception, elaboration, construction and transition. It is a must read for software engineering practitioners (architects, application developers, designers and project managers), academics, and students and apprentices of software engineering.

Agile techniques have demonstrated immense potential for developing more effective, higher-quality software. However,scaling these techniques to the enterprise presents many challenges. The solution is to integrate the principles and practices of Lean Software Development with Agile’s ideology and methods. By doing so, software organizations leverage Lean’s powerful capabilities for “optimizing the whole” and managing complex enterprise projects. A combined “Lean-Agile” approach can dramatically improve both developer productivity and the software’s business value.In this book, three expert Lean software consultants draw from their unparalleled experience to gather all the insights, knowledge, and new skills you need to succeed with Lean-Agile development. Lean-Agile Software Development shows how to extend Scrum processes with an Enterprise view based on Lean principles. The authors present crucial technical insight into emergent design, and demonstrate how to apply it to make iterative development more effective. They also identify several common development “anti-patterns” that can work against your goals, and they offer actionable, proven alternatives. Lean-Agile Software Development shows how to Transition to Lean Software Development quickly and successfully Manage the initiation of product enhancements Help project managers work together to manage product portfolios more effectively Manage dependencies across the software development organization and with its partners and colleagues Integrate development and QA roles to improve quality and eliminate waste Determine best practices for different software development teams The book’s companion Web site, www.netobjectives.com/lasd, provides updates, links to related materials, and support for discussions of the book’s content.

"Just the understanding and insights you will pick up about how people encounter and cope with combinations of technical, social, political, and economic opportunities and challenges make the book a joy to read and worth much more than the price of it alone." --Barry Boehm, from the Foreword This practical handbook shows you how to build an effective business case when you need to justify--and persuade management to accept--software change or improvement. Based on real-world scenarios, the book covers the most common situations in which business case analyses are required and explains specific techniques that have proved successful in practice. Drawing on years of experience in winning the "battle of the budget," the author shows you how to use commonly accepted engineering economic arguments to make your numbers "sing" to management. The book provides examples of successful business cases; along the way, tables, tools, facts, figures, and metrics guide you through the entire analytic process. Writing in a concise and witty style, the author makes this valuable guidance accessible to every software engineer, manager, and IT professional. Highlights include: How and where business case analyses fit into the software and IT life cycle process Explanations of the most common tools for business case analysis, such as present-value, return-on-investment, break-even, and cost/benefit calculation Tying the business process to the software development life cycle Packaging the business case for management consumption Frameworks and guidelines for justifying IT productivity, quality, and delivery cycle improvement strategies Case studies for applying appropriate decision situations to software process improvement Strategic guidelines for various business case analyses With this book in hand, you will find the facts, examples, hard data, and case studies needed for preparing your own winning business cases in today's complex software environment.

Enterprise-Scale Agile Software Development is the collective sum of knowledge accumulated during the full-scale transition of a 1400-person organization to agile development-considered the largest implementation of agile development and Scrum ever attempted anywhere in the world. Now James Schiel, a certified Scrum trainer and member of the Scrum

"Outside-in thinking complements any approach your teams may be taking to the actual implementation of software, but it changes how you measure success. A successful outside-in team does a lot of learning and not much speculation." —Tom Poppendieck Build Software That Delivers Maximum Business Value to Every Key Stakeholder Imagine your ideal development project. It will deliver exactly what your clients need. It will achieve broad, rapid, enthusiastic adoption. And it will be designed and built by a productive, high-morale team of expert software professionals. Using this book's breakthrough "outside-in" approach to software development, your next project can be that ideal project. In Outside-in Software Development, two of IBM's most respected software leaders, Carl Kessler and John Sweitzer, show you how to identify the stakeholders who'll determine your project's real value, shape every decision around their real needs, and deliver software that achieves broad, rapid, enthusiastic adoption. The authors present an end-to-end framework and practical implementation techniques any development team can quickly benefit from, regardless of project type or scope. Using their proven approach, you can improve the effectiveness of every client conversation, define priorities with greater visibility and clarity, and make sure all your code delivers maximum business value. Coverage includes Understanding your stakeholders and the organizational and business context they operate in Clarifying the short- and long-term stakeholder goals your project will satisfy More effectively mapping project expectations to outcomes Building more "consumable" software: systems that are easier to deploy, use, and support Continuously enhancing alignment with stakeholder goals Helping stakeholders manage ongoing change long after you've delivered your product Mastering the leadership techniques needed to drive outside-in development

Why another book on software project management? For some time, the fields of project management, computer science, and software development have been growing rapidly and concurrently. Effective support for the enterprise demands the merging of these efforts into a coordinated discipline, one that incorporates best practices from both systems development and project management life cycles. Robert K. Wysocki creates that discipline in this book--a ready reference for professionals and consultants as well as a textbook for students of computer information systems and project management. By their very nature, software projects defy a "one size fits all" approach. In these pages you will learn to apply best-practice principles while maintaining the flexibility that's essential for successful software development. Learn how to make the planning process fit the need * Understand how and why software development must be planned on a certainty-to-uncertainty continuum * Categorize your projects on a four-quadrant model * Learn when to use each of the five SDPM strategies--Linear, Incremental, Iterative, Adaptive, and Extreme * Explore the benefits of each strategic model and what types of projects it supports best * Recognize the activities that go into the Scoping, Planning, Launching, Monitoring/Controlling, and Closing phases of each strategy * Apply this knowledge to the specific projects you manage * Get a clear picture of where you are and how to get where you want to go

“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.

This book addresses how best to make build vs. buy decisions, and what effect such decisions have on the software development life cycle (SDLC). Offering an integrated approach that includes important management and decision practices, the text explains how to create successful solutions that fit user and customer needs, by mixing different SDLC methodologies. Features: provides concrete examples and effective case studies; focuses on the skills and insights that distinguish successful software implementations; covers management issues as well as technical considerations, including how to deal with political and cultural realities in organizations; identifies many new alternatives for how to manage and model a system using sophisticated analysis tools and advanced management practices; emphasizes how and when professionals can best apply these tools and practices, and what benefits can be derived from their application; discusses searching for vendor solutions, and vendor contract considerations.