As for the latter, are you a programmer and curious about being your own boss? Where do you turn for information? Until now, online and traditional literature havent caught up with the reality of the post-dot com bust.Micro-ISV: From Vision to Reality explains what works and why in today's emerging micro-ISV sector. Currently, thousands of programmers build and deliver great solutions ISV-style, earning success and revenues much larger than you might guess. Written by and for micro-ISVs, with help from some of the leaders of the field, this book takes you beyond just daydreaming to running your own business. It thoroughly explores how it is indeed possible to launch and maintain a small and successful ISV business, and is an ideal read if you're interested in getting started.

    Is this Scrum? Can you share some tactics to do effective Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and Product Backlog Refinement? My designation is development manager. Does this mean I have no role in Scrum? How is Scrum Empirical? Can Scrum Master and Product Owner be the same person? We don’t have a Scrum Master. Are we still practicing Scrum? What does Self-Organization really mean? How does Scrum embrace the four values and twelve principles of the Agile Manifesto? Please share a case study on Scrum based product development? Recommendations for the book from the Scrum champions Take advantage of Hiren’s vast experience and avoid making the common errors people make as they begin their journey. This book contains a wealth of practical information that will be useful to readers as they work to implement the basic theory found in The Scrum Guide—Steve Porter, team member, Scrum.org In his book Scrum Insights for Practitioners, Hiren has extended the core rules of The Scrum Guide with practices he has found useful. Hiren answers questions regarding Scrum that potentially remain unanswered even after one reads The Scrum Guide. Hiren dismantles common misconceptions about Scrum, regardless of the source of such misconceptions. Hiren elaborates on basic information provided in The Scrum Guide, as well as on the principles underlying Scrum—Gunther Verheyen, Author of “Scrum — A Pocket Guide, a Smart Travel Companion” Hiren Doshi has written a fine companion to The Scrum Guide, filling in some of the intentional gaps left in the Scrum framework. Using this companion along with The Scrum Guide will undoubtedly improve the outlook for those teams that internalize its teachings.”—Charles Bradley, ScrumCrazy.com This book will help you understand the nuances of Scrum. It takes a very practical approach toward implementing Scrum without compromising on its values and principles. A useful and handy reference for Scrum practitioners!— Gopinath R, Agile coach and practitioner

    How do I deal with it? Well, that’s easy. You have three options:1. Ignore it. Changing organizations is hard work. If you don’t have the stamina to learn how to be a good change agent, then stop complaining about what’s bad. Accept that the organization is what it is, and enjoy the good parts of your work.2. Quit your job. The only reason there are bad organizations is that people don’t quit their jobs. Do the world a favor and find a better place to work. Help bad organizations out of their misery by not working for them.3. Learn about change management. Most people are terrible at influencing other people and changing organizations. But, if you’re serious about it, you can learn how to be a more effective change agent.It’s take it, leave it, or change it...This book is for those who choose option 3.

     Instead of playing career roulette, you invest in deepening relationships and developing your skills. Instead of networking to get something, you lead with generosity. To further improve your odds, you make your work visible and frame it as a contribution. Combined, these elements form a powerful approach to work and life. In Working Out Loud, you’ll learn about research supporting this approach and read stories of people who’ve changed their lives by adopting it. Then you’ll go through a twelve-week mastery program to put the approach into practice yourself and turn that practice into a sustainable habit.

    In Overcoming the Five Dysfunctions of a Team, Lencioni offers more specific, practical guidance for overcoming the Five Dysfunctions--using tools, exercises, assessments, and real-world examples. He examines questions that all teams must ask themselves: Are we really a team? How are we currently performing? Are we prepared to invest the time and energy required to be a great team? Written concisely and to the point, this guide gives leaders, line managers, and consultants alike the tools they need to get their teams up and running quickly and effectively.

    Vaughn Vernon couples guided approaches to implementation with modern architectures, highlighting the importance and value of focusing on the business domain while balancing technical considerations.Building on Eric Evans’ seminal book, Domain-Driven Design, the author presents practical DDD techniques through examples from familiar domains. Each principle is backed up by realistic Java examples–all applicable to C# developers–and all content is tied together by a single case study: the delivery of a large-scale Scrum-based SaaS system for a multitenant environment.The author takes you far beyond “DDD-lite” approaches that embrace DDD solely as a technical toolset, and shows you how to fully leverage DDD’s “strategic design patterns” using Bounded Context, Context Maps, and the Ubiquitous Language. Using these techniques and examples, you can reduce time to market and improve quality, as you build software that is more flexible, more scalable, and more tightly aligned to business goals.

    This manual is aimed at everyone who works on interactive products in a design and development environment. It contains all of the basic information required for getting started with the project management method Scrum, but also offers a number of in-depth chapters looking at topics which even the most experienced Scrummers have trouble with on a daily basis. If you are experienced, you will find the advanced tips and tricks useful. If you are just considering Scrum, this book will most certainly get you enthusiastic.

    The key, as the authors show, is to integrate regularly and often using continuous integration (CI) practices and techniques. The authors first examine the concept of CI and its practices from the ground up and then move on to explore other effective processes performed by CI systems, such as database integration, testing, inspection, deployment, and feedback. Through more than forty CI-related practices using application examples in different languages, readers learn that CI leads to more rapid software development, produces deployable software at every step in the development lifecycle, and reduces the time between defect introduction and detection, saving time and lowering costs. With successful implementation of CI, developers reduce risks and repetitive manual processes, and teams receive better project visibility. The book covers How to make integration a "non-event" on your software development projects How to reduce the amount of repetitive processes you perform when building your software Practices and techniques for using CI effectively with your teams Reducing the risks of late defect discovery, low-quality software, lack of visibility, and lack of deployable software Assessments of different CI servers and related tools on the market The book's companion Web site, www.integratebutton.com, provides updates and code examples

    As the first act of flight, a rocket launch requires an entire set of systems to lift the vehicle into orbit-not just the vehicle itself, but all the systems needed for smoothly moving off the ground into space. Likewise, your project needs its entire set of supporting systems in place to begin a successful journey to delivery. Whatever you call it (project kickoff, bootcamp, inception, or jump start), liftoff gives your team its trajectory, and launches your project. This critical practice informs, inspires, and aligns everyone to a singular purpose: the successful delivery of software. This success is in your hands! Agile veterans Diana Larsen and Ainsley Nies teach you how to organize and conduct liftoffs, hold team activities to discover what's most important, and offer a working framework for effective and lightweight agile chartering.

    You’ll explore how four different teams used Kanban to make paradigm-changing improvements in software development. These teams were struggling with overwork, unclear priorities, and lack of direction. As you discover what worked for them, you’ll understand how to make significant changes in real situations.The four case studies in this book explain how to:Improve the full value chain by using Enterprise KanbanBoost engagement, teamwork, and flow in change management and operationsSave a derailing project with KanbanHelp an office team outside IT keep up with growth using KanbanWhat seems easy in theory can become tangled in practice. Discover why “improving IT” can make you miss your biggest improvement opportunities, and why you should focus on fixing quality and front-end operations before IT. Discover how to keep long-term focus and improve across department borders while dealing with everyday challenges. Find out what happened when using Kanban to find better ways to do work in a well-established company, including running multi-team development without a project office.You’ll inspire your team and engage management to make it easier to develop better products.

    I wrote this book for three major reasons: (1) to help move business and technology planning from a systems and process-level view to a more strategy-driven enterprise-level view, (2) to promote and explain the emerging profession of EA, and (3) to provide the first textbook on the subject of EA, which is suitable for graduate and undergraduate levels of study. To date, other books on EA have been practitioner books not specifically oriented toward a student who may be learning the subject with little to no previous exposure. Therefore, this book contains references to related academic research and industry best practices, as well as my own observations about potential future practices and the direction of this emerging profession.

    This book demystifies agile methodologies: why they’re designed the way they are, what problems they address, and the values, principles, and ideas they embody.Learning Agile helps you recognize the principles that apply to development problems specific to your team, company, and projects. You’ll discover how to use that information to guide your choice of methodologies and practices.With this book you’ll learn:Values that effective software teams possessThe methodologies that embody those valuesThe practices that make up those methodologiesAnd principles that help you bring those values, methodologies, and practices to your team and your company

    To grow professionally, you also need soft skills and effective learning techniques. Honing those skills is what this book is all about. Authors Dave Hoover and Adewale Oshineye have cataloged dozens of behavior patterns to help you perfect essential aspects of your craft. Compiled from years of research, many interviews, and feedback from O'Reilly's online forum, these patterns address difficult situations that programmers, administrators, and DBAs face every day. And it's not just about financial success. Apprenticeship Patterns also approaches software development as a means to personal fulfillment. Discover how this book can help you make the best of both your life and your career. Solutions to some common obstacles that this book explores in-depth include:Burned out at work? "Nurture Your Passion" by finding a pet project to rediscover the joy of problem solving.Feeling overwhelmed by new information? Re-explore familiar territory by building something you've built before, then use "Retreat into Competence" to move forward again.Stuck in your learning? Seek a team of experienced and talented developers with whom you can "Be the Worst" for a while. "Brilliant stuff! Reading this book was like being in a time machine that pulled me back to those key learning moments in my career as a professional software developer and, instead of having to learn best practices the hard way, I had a guru sitting on my shoulder guiding me every step towards master craftsmanship. I'll certainly be recommending this book to clients. I wish I had this book 14 years ago!" -Russ Miles, CEO, OpenCredo

    This one's a keeper." --Robert C. Martin "If you want to be an expert in the state of the art in TDD, you need to understand the ideas in this book."--Michael Feathers Test-Driven Development (TDD) is now an established technique for delivering better software faster. TDD is based on a simple idea: Write tests for your code before you write the code itself. However, this simple idea takes skill and judgment to do well. Now there's a practical guide to TDD that takes you beyond the basic concepts. Drawing on a decade of experience building real-world systems, two TDD pioneers show how to let tests guide your development and "grow" software that is coherent, reliable, and maintainable. Steve Freeman and Nat Pryce describe the processes they use, the design principles they strive to achieve, and some of the tools that help them get the job done. Through an extended worked example, you'll learn how TDD works at multiple levels, using tests to drive the features and the object-oriented structure of the code, and using Mock Objects to discover and then describe relationships between objects. Along the way, the book systematically addresses challenges that development teams encounter with TDD--from integrating TDD into your processes to testing your most difficult features. Coverage includes - Implementing TDD effectively: getting started, and maintaining your momentum throughout the project - Creating cleaner, more expressive, more sustainable code - Using tests to stay relentlessly focused on sustaining quality - Understanding how TDD, Mock Objects, and Object-Oriented Design come together in the context of a real software development project - Using Mock Objects to guide object-oriented designs - Succeeding where TDD is difficult: managing complex test data, and testing persistence and concurrency

    It describes the roles, teams, values, intentions, habits, activities, policies and work products of a small software development team forwhom time-to-market and development costs are critical considerations.Alistair Cockburn is one of the founders of the Agile software developmentmovement. He spells out proven best practices based on his extensiveexperience helping organizations build software quickly and with less cost. Theauthor understands that small teams cannot be burdened by process-heavysoftware methodologies. By advocating that developers stay close together andremain in steady, good-will communication with customers and users, thisbook teaches the reader how to develop software that not only does what it issupposed to do, but also gets completed on time and within budget.