Developer best practices - 23-teilige buchserie (442 Ergebnisse)

Paperback. Zustand: Good. Corporate and commercial software-development teams all want solutions for one important problem?how to get their high-pressure development schedules under control. In RAPID DEVELOPMENT, author Steve McConnell addresses that concern head-on with overall strategies, specific best practices, and valuable tips that help shrink and control development schedules and keep projects moving. Inside, you?ll find: A rapid-development strategy that can be applied to any project and the best practices to make that strategy work Candid discussions of great and not-so-great rapid-development practices?estimation, prototyping, forced overtime, motivation, teamwork, rapid-development languages, risk management, and many others A list of classic mistakes to avoid for rapid-development projects, including creeping requirements, shortchanged quality, and silver-bullet syndrome Case studies that vividly illustrate what can go wrong, what can go right, and how to tell which direction your project is going RAPID DEVELOPMENT is the real-world guide to more efficient applications development.…

Paperback. Zustand: Very Good. 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.…

Paperback. Zustand: Good. 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.…

Paperback. Zustand: Fair. 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.…

Paperback. Zustand: Good. Learn proven, real-world techniques for specifying software requirements with this practical reference. It details 30 requirement ?patterns? offering realistic examples for situation-specific guidance for building effective software requirements. Each pattern explains what a requirement needs to convey, offers potential questions to ask, points out potential pitfalls, suggests extra requirements, and other advice. This book also provides guidance on how to write other kinds of information that belong in a requirements specification, such as assumptions, a glossary, and document history and references, and how to structure a requirements specification. A disturbing proportion of computer systems are judged to be inadequate; many are not even delivered; more are late or over budget. Studies consistently show one of the single biggest causes is poorly defined requirements: not properly defining what a system is for and what it?s supposed to do. Even a modest contribution to improving requirements offers the prospect of saving businesses part of a large sum of wasted investment. This guide emphasizes this important requirement need?determining what a software system needs to do before spending time on development. Expertly written, this book details solutions that have worked in the past, with guidance for modifying patterns to fit individual needs?giving developers the valuable advice they need for building effective software requirements.…

Paperback. Zustand: Fair. Corporate and commercial software-development teams all want solutions for one important problem?how to get their high-pressure development schedules under control. In RAPID DEVELOPMENT, author Steve McConnell addresses that concern head-on with overall strategies, specific best practices, and valuable tips that help shrink and control development schedules and keep projects moving. Inside, you?ll find: A rapid-development strategy that can be applied to any project and the best practices to make that strategy work Candid discussions of great and not-so-great rapid-development practices?estimation, prototyping, forced overtime, motivation, teamwork, rapid-development languages, risk management, and many others A list of classic mistakes to avoid for rapid-development projects, including creeping requirements, shortchanged quality, and silver-bullet syndrome Case studies that vividly illustrate what can go wrong, what can go right, and how to tell which direction your project is going RAPID DEVELOPMENT is the real-world guide to more efficient applications development.…

Paperback. Zustand: Very Good. Learn proven, real-world techniques for specifying software requirements with this practical reference. It details 30 requirement ?patterns? offering realistic examples for situation-specific guidance for building effective software requirements. Each pattern explains what a requirement needs to convey, offers potential questions to ask, points out potential pitfalls, suggests extra requirements, and other advice. This book also provides guidance on how to write other kinds of information that belong in a requirements specification, such as assumptions, a glossary, and document history and references, and how to structure a requirements specification. A disturbing proportion of computer systems are judged to be inadequate; many are not even delivered; more are late or over budget. Studies consistently show one of the single biggest causes is poorly defined requirements: not properly defining what a system is for and what it?s supposed to do. Even a modest contribution to improving requirements offers the prospect of saving businesses part of a large sum of wasted investment. This guide emphasizes this important requirement need?determining what a software system needs to do before spending time on development. Expertly written, this book details solutions that have worked in the past, with guidance for modifying patterns to fit individual needs?giving developers the valuable advice they need for building effective software requirements.…

Zustand: Acceptable. Item in acceptable condition! Textbooks may not include supplemental items i.e. CDs, access codes etc.

Zustand: Good. Item in good condition. Textbooks may not include supplemental items i.e. CDs, access codes etc.

Paperback. Zustand: Very Good. Corporate and commercial software-development teams all want solutions for one important problem?how to get their high-pressure development schedules under control. In RAPID DEVELOPMENT, author Steve McConnell addresses that concern head-on with overall strategies, specific best practices, and valuable tips that help shrink and control development schedules and keep projects moving. Inside, you?ll find: A rapid-development strategy that can be applied to any project and the best practices to make that strategy work Candid discussions of great and not-so-great rapid-development practices?estimation, prototyping, forced overtime, motivation, teamwork, rapid-development languages, risk management, and many others A list of classic mistakes to avoid for rapid-development projects, including creeping requirements, shortchanged quality, and silver-bullet syndrome Case studies that vividly illustrate what can go wrong, what can go right, and how to tell which direction your project is going RAPID DEVELOPMENT is the real-world guide to more efficient applications development. …

Paperback. Zustand: Fair. Often referred to as the ?black art? because of its complexity and uncertainty, software estimation is not as difficult or puzzling as people think. In fact, generating accurate estimates is straightforward?once you understand the art of creating them. In his highly anticipated book, acclaimed author Steve McConnell unravels the mystery to successful software estimation?distilling academic information and real-world experience into a practical guide for working software professionals. Instead of arcane treatises and rigid modeling techniques, this guide highlights a proven set of procedures, understandable formulas, and heuristics that individuals and development teams can apply to their projects to help achieve estimation proficiency. Discover how to: Estimate schedule and cost?or estimate the functionality that can be delivered within a given time frame Avoid common software estimation mistakes Learn estimation techniques for you, your team, and your organization * Estimate specific project activities?including development, management, and defect correction Apply estimation approaches to any type of project?small or large, agile or traditional Navigate the shark-infested political waters that surround project estimates When many corporate software projects are failing, McConnell shows you what works for successful software estimation.…

Paperback. Zustand: Good. Often referred to as the ?black art? because of its complexity and uncertainty, software estimation is not as difficult or puzzling as people think. In fact, generating accurate estimates is straightforward?once you understand the art of creating them. In his highly anticipated book, acclaimed author Steve McConnell unravels the mystery to successful software estimation?distilling academic information and real-world experience into a practical guide for working software professionals. Instead of arcane treatises and rigid modeling techniques, this guide highlights a proven set of procedures, understandable formulas, and heuristics that individuals and development teams can apply to their projects to help achieve estimation proficiency. Discover how to: Estimate schedule and cost?or estimate the functionality that can be delivered within a given time frame Avoid common software estimation mistakes Learn estimation techniques for you, your team, and your organization * Estimate specific project activities?including development, management, and defect correction Apply estimation approaches to any type of project?small or large, agile or traditional Navigate the shark-infested political waters that surround project estimates When many corporate software projects are failing, McConnell shows you what works for successful software estimation.…

Paperback. Zustand: Fair. No matter how much instruction you?ve had on managing software requirements, there?s no substitute for experience. Too often, lessons about requirements engineering processes lack the no-nonsense guidance that supports real-world solutions. Complementing the best practices presented in his book, Software Requirements, Second Edition, requirements engineering authority Karl Wiegers tackles even more of the real issues head-on in this book. With straightforward, professional advice and practical solutions based on actual project experiences, this book answers many of the tough questions raised by industry professionals. From strategies for estimating and working with customers to the nuts and bolts of documenting requirements, this essential companion gives developers, analysts, and managers the cosmic truths that apply to virtually every software development project. Discover how to: ? Make the business case for investing in better requirements practices ? Generate estimates using three specific techniques ? Conduct inquiries to elicit meaningful business and user requirements ? Clearly document project scope ? Implement use cases, scenarios, and user stories effectively ? Improve inspections and peer reviews ? Write requirements that avoid ambiguity.…

Paperback. Zustand: Good. No matter how much instruction you?ve had on managing software requirements, there?s no substitute for experience. Too often, lessons about requirements engineering processes lack the no-nonsense guidance that supports real-world solutions. Complementing the best practices presented in his book, Software Requirements, Second Edition, requirements engineering authority Karl Wiegers tackles even more of the real issues head-on in this book. With straightforward, professional advice and practical solutions based on actual project experiences, this book answers many of the tough questions raised by industry professionals. From strategies for estimating and working with customers to the nuts and bolts of documenting requirements, this essential companion gives developers, analysts, and managers the cosmic truths that apply to virtually every software development project. Discover how to: ? Make the business case for investing in better requirements practices ? Generate estimates using three specific techniques ? Conduct inquiries to elicit meaningful business and user requirements ? Clearly document project scope ? Implement use cases, scenarios, and user stories effectively ? Improve inspections and peer reviews ? Write requirements that avoid ambiguity.…

Paperback. Zustand: Very Good. No matter how much instruction you?ve had on managing software requirements, there?s no substitute for experience. Too often, lessons about requirements engineering processes lack the no-nonsense guidance that supports real-world solutions. Complementing the best practices presented in his book, Software Requirements, Second Edition, requirements engineering authority Karl Wiegers tackles even more of the real issues head-on in this book. With straightforward, professional advice and practical solutions based on actual project experiences, this book answers many of the tough questions raised by industry professionals. From strategies for estimating and working with customers to the nuts and bolts of documenting requirements, this essential companion gives developers, analysts, and managers the cosmic truths that apply to virtually every software development project. Discover how to: ? Make the business case for investing in better requirements practices ? Generate estimates using three specific techniques ? Conduct inquiries to elicit meaningful business and user requirements ? Clearly document project scope ? Implement use cases, scenarios, and user stories effectively ? Improve inspections and peer reviews ? Write requirements that avoid ambiguity.…

Paperback. Zustand: Very Good. Agile development processes foster better collaboration, innovation, and results. So why limit their use to software projects?when you can transform your entire business? Written by agile-mentoring expert Jochen Krebs, this book illuminates the opportunities?and rewards?of applying agile processes to your overall IT portfolio. Whether project manager, business analyst, or executive?you?ll understand the business drivers behind agile portfolio management. And learn best practices for optimizing results. Use agile processes to align IT and business strategy Adapt and extend core agile processes Orchestrate the collaboration between IT and business vision Eliminate wish-list driven requirements, and manage expectations instead Optimize the balance of projects, resources, and assets in your portfolio Use metrics to communicate project status, quality, even team morale Create a portfolio strategy consistent with the goals of the organization Achieve organizational and process transparency Manage your business with agility?and help maximize the returns.…

Paperback. Zustand: Good. Agile development processes foster better collaboration, innovation, and results. So why limit their use to software projects?when you can transform your entire business? Written by agile-mentoring expert Jochen Krebs, this book illuminates the opportunities?and rewards?of applying agile processes to your overall IT portfolio. Whether project manager, business analyst, or executive?you?ll understand the business drivers behind agile portfolio management. And learn best practices for optimizing results. Use agile processes to align IT and business strategy Adapt and extend core agile processes Orchestrate the collaboration between IT and business vision Eliminate wish-list driven requirements, and manage expectations instead Optimize the balance of projects, resources, and assets in your portfolio Use metrics to communicate project status, quality, even team morale Create a portfolio strategy consistent with the goals of the organization Achieve organizational and process transparency Manage your business with agility?and help maximize the returns.…

Paperback. Zustand: Very Good. 1. It's a well-cared-for item that has seen limited use. The item may show minor signs of wear. All the text is legible, with all pages included. It may have slight markings and/or highlighting.

Paperback. Zustand: Very Good. Whether you're a new developer seeking a sound introduction to the practice of software development or a veteran exploring strategic new approaches to problem solving, you'll find a wealth of practical suggestions and methods for strengthening your skills.

Paperback. Zustand: Good. Whether you're a new developer seeking a sound introduction to the practice of software development or a veteran exploring strategic new approaches to problem solving, you'll find a wealth of practical suggestions and methods for strengthening your skills.

Paperback. Zustand: Fair. Whether you're a new developer seeking a sound introduction to the practice of software development or a veteran exploring strategic new approaches to problem solving, you'll find a wealth of practical suggestions and methods for strengthening your skills.

Paperback. Zustand: Very Good. It?s time to extend the benefits of Scrum?greater agility, higher-quality products, and lower costs?from individual teams to your entire enterprise. However, with Scrum?s lack of prescribed rules, the friction of change can be challenging as people struggle to break from old project management habits. In this book, agile-process revolution leader Ken Schwaber takes you through change management?for your organizational and interpersonal processes?explaining how to successfully adopt Scrum across your entire organization. A cofounder of Scrum, Ken draws from decades of experience, answering your questions through case studies of proven practices and processes. With them, you?ll learn how to adopt?and adapt?Scrum in the enterprise. And gain profound levels of transparency into your development processes. Discover how to: Evaluate the benefits of adopting Scrum in any size organization Initiate an enterprise transition project Implement a single, prioritized Product Backlog Organize effective Scrum teams using a top-down approach Adapt and apply solutions for integrating engineering practices across multiple teams Shorten release times by managing high-value increments Refine your Scrum practices and help reduce the length of Sprints.…

Paperback. Zustand: Good. It?s time to extend the benefits of Scrum?greater agility, higher-quality products, and lower costs?from individual teams to your entire enterprise. However, with Scrum?s lack of prescribed rules, the friction of change can be challenging as people struggle to break from old project management habits. In this book, agile-process revolution leader Ken Schwaber takes you through change management?for your organizational and interpersonal processes?explaining how to successfully adopt Scrum across your entire organization. A cofounder of Scrum, Ken draws from decades of experience, answering your questions through case studies of proven practices and processes. With them, you?ll learn how to adopt?and adapt?Scrum in the enterprise. And gain profound levels of transparency into your development processes. Discover how to: Evaluate the benefits of adopting Scrum in any size organization Initiate an enterprise transition project Implement a single, prioritized Product Backlog Organize effective Scrum teams using a top-down approach Adapt and apply solutions for integrating engineering practices across multiple teams Shorten release times by managing high-value increments Refine your Scrum practices and help reduce the length of Sprints.…

Paperback. Zustand: Very Good. 1. It's a well-cared-for item that has seen limited use. The item may show minor signs of wear. All the text is legible, with all pages included. It may have slight markings and/or highlighting.

Paperback. Zustand: Very Good. 1. It's a well-cared-for item that has seen limited use. The item may show minor signs of wear. All the text is legible, with all pages included. It may have slight markings and/or highlighting.

Paperback. Zustand: Very Good. 1. It's a well-cared-for item that has seen limited use. The item may show minor signs of wear. All the text is legible, with all pages included. It may have slight markings and/or highlighting.

Paperback. Zustand: Good. Dismantle the overwhelming complexity in your IT projects with strategies and real-world examples from a leading expert on enterprise architecture. This guide describes best practices for creating an efficient IT organization that consistently delivers on time, on budget, and in line with business needs. IT systems have become too complex?and too expensive. Complexity can create delays, cost overruns, and outcomes that do not meet business requirements. The resulting losses can impact your entire company. This guide demonstrates that, contrary to popular belief, complex problems demand simple solutions. The author believes that 50 percent of the complexity of a typical IT project can and should be eliminated?and he shows you how to do it. You?ll learn a model for understanding complexity, the three tenets of complexity control, and how to apply specific techniques such as checking architectures for validity. Find out how the author?s methodology could have saved a real-world IT project that went off track, and ways to implement his solutions in a variety of situations. …

Paperback. Zustand: Fair. 1. The item might be beaten up but readable. May contain markings or highlighting, as well as stains, bent corners, or any other major defect, but the text is not obscured in any way.

Paperback. Zustand: Very Good. 1. It's a well-cared-for item that has seen limited use. The item may show minor signs of wear. All the text is legible, with all pages included. It may have slight markings and/or highlighting.

Paperback. Zustand: Fair. 1. The item might be beaten up but readable. May contain markings or highlighting, as well as stains, bent corners, or any other major defect, but the text is not obscured in any way.