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.
"In this book, we've collected the personal habits, ideas, and approaches of successful agile software developers and compiled them in a series of short, easy-to-digest tips. For each practice, we expose the evil demon's whisperings - the temptations or shortcuts he's trying to get you to take. And then we explain the agile practices that act as a guardian angel to protect your project and your career."--BOOK JACKET.
Μερικές φορές ένα κορίτσι δέχεται το άγγιγμα της Πολεμόχαρης Μητέρας. Τέτοιο κορίτσι είναι και η Θορν. Πασχίζοντας να πάρει εκδίκηση για τον θάνατο του πατέρα της, ζει μονάχα για να πολεμά. Τώρα, όμως, ο άντρας που τη δίδαξε πώς να σκοτώνει την κατηγορεί για φόνο. Μερικές φορές, μια γυναίκα γίνεται πολεμίστρια. Ξαφνικά βρίσκεται μπλεγμένη στις δολοπλοκίες του Πατέρα Γιάρβι, του πανούργου θεράποντα της Γκέτλαντ. Διασχίζοντας τον μισό κόσμο, αναζητώντας συμμάχους ενάντια στον αδίστακτο Υψηλό Βασιλέα, θα υποστεί μια σκληρή μαθητεία στο αίμα και τον δόλο. Μερικές φορές, μια πολεμίστρια γίνεται όπλο. Στο ταξίδι αυτό, έχει στο πλευρό της τον Μπραντ, έναν πολεμιστή που απεχθάνεται να σκοτώνει –αποτυχημένο τόσο στα δικά της μάτια όσο και στα δικά του–, με μία και μοναδική ευκαιρία να εξιλεωθεί. Τα όπλα υπηρετούν έναν και μόνο σκοπό. Άραγε η Θορν θα παραμείνει σε όλη της τη ζωή έρμαιο των ισχυρών ή θα καταφέρει να χαράξει τον δικό της δρόμο;
A typical characterization of EuroSPI is reflected in a statement made by a c- pany: “. . . the biggest value of EuroSPI lies in its function as a European knowledge and experience exchange mechanism for SPI and innovation. ” Since its beginning in 1994 in Dublin, the EuroSPI initiative has outlined that there is not a single silver bullet to solve SPI issues, but that you need to understand a c- bination of different SPI methods and approaches to achieve concrete benefits. The- fore each proceedings volume covers a variety of different topics, and at the conf- ence we discuss potential synergies and the combined use of such methods and - proaches. These proceedings contain selected research papers for five topics: Section I: SPI Tools Section II: SPI Methods Section III: SPI in SMEs Section IV: Economic Aspects of SPI Section V: The Future of SPI Section I presents studies on SPI tools. The authors provide an insight into new tools which can be used for SPI. Willem Bekkers et al. present a new assessment method and tool for software product management. Ismael Edrei-Espinosa-Curiel et al. illustrate a graphical approach to support the teaching of SPI. Paul Clarke and coworkers deal with an analysis and a tool to help real adoption of standards like ISO 12207 and they focus on SPI implementation and practices. Esparanca Amengual et al. present a new team-based assessment method and tool.
“Collaboration Explained is a deeply pragmatic book that helps agile practitioners understand and manage complex organizational and team dynamics. As an agile coach, I’ve found the combination of straightforward advice and colorful anecdotes to be invaluable in guiding and focusing interactions with my teams. Jean’s wealth of experience is conveyed in a carefully struck balance of reference guides and prose, facilitating just-in-time learning in the agile spirit. All in all, a superb resource for building stronger teams that’s fit for agile veterans and neophytes alike.” —Arlen Bankston, Lean Agile Practice Manager, CC Pace “If Agile is the new ‘what,’ then surely Collaboration is the new ‘how.’ There are many things I really like about Jean’s new book. Right at the top of the list is that I don’t have to make lists of ideas for collaboration and facilitation anymore. Jean has it all. Not only does she have those great ideas for meetings, retrospectives, and team decision-making that I need to remember, but the startling new and thought-provoking ideas are there too. And the stories, the stories, the stories! The best way to transfer wisdom. Thanks, Jean!” —Linda Rising, Independent Consultant The Hands-On Guide to Effective Collaboration in Agile Projects To succeed, an agile project demands outstanding collaboration among all its stakeholders. But great collaboration doesn’t happen by itself; it must be carefully planned and facilitated throughout the entire project lifecycle. Collaboration Explained is the first book to bring together proven, start-to-finish techniques for ensuring effective collaboration in any agile software project. Since the early days of the agile movement, Jean Tabaka has been studying and promoting collaboration in agile environments. Drawing on her unsurpassed experience, she offers clear guidelines and easy-to-use collaboration templates for every significant project event: from iteration and release planning, through project chartering, all the way through post-project retrospectives. Tabaka’s hands-on techniques are applicable to every leading agile methodology, from Extreme Programming and Scrum to Crystal Clear. Above all, they are practical: grounded in a powerful understanding of the technical, business, and human challenges you face as a project manager or development team member. · Build collaborative software development cultures, leaders, and teams · Prepare yourself to collaborate—and prepare your team · Define clear roles for each participant in promoting collaboration · Set your collaborative agenda · Master tools for organizing collaboration more efficiently · Run effective collaborative meetings—including brainstorming sessions · Promote better small-group and pair-programming collaboration · Get better information, and use it to make better decisions · Use non-abusive conflict to drive positive outcomes · Collaborate to estimate projects and schedules more accurately · Strengthen collaboration across distributed, virtual teams · Extend collaboration from individual projects to the entire development organization
Get introduced to the fascinating world inhabited by the professional software developer. Aimed at a non-technical audience, this book aims to de-obfuscate the jargon, explain the various activities that coders undertake, and analyze the specific pressures, priorities, and preoccupations that developers are prone to. In each case it offers pragmatic advice on how to use this knowledge to make effective business decisions and work productively with software teams. Software projects are, all too often, utter nightmares for everyone involved. Depending on which study you read, between 60 and 90 percent of all software projects are completed late, run over budget, or deliver an inferior quality end product. This blight affects everyone from large organizations trying to roll out business change to tiny startups desperately trying to launch their MVP before the money runs out. While there has been much attention devoted to understanding these failings, leading to the development of entire management methodologies aimed at reducing the failure rate, such new processes have had, at best, limited success in delivering better results. Based on a decade spent exploring the world of software, Patrick Gleeson argues that the underlying reason for the high failure rate of software projects is that software development, being a deeply arcane and idiosyncratic process, tends to be thoroughly and disastrously misunderstood by managers and leaders. So long as the people tasked with making decisions about software projects are unaware of these idiosyncrasies and their ramifications, software projects will be delivered late, software products will be unfit for purpose, and relations between software developers and their non-technical colleagues will be strained. Even the most potent modern management tools are ineffective when wielded blindly. To anyone who employs, contracts, manages, or works with software developers, Working with Coders: A Guide to Software Development for the Perplexed Non-Techie delivers the understanding necessary to reduce friction and inefficiencies at the intersection between software development teams and their non-technical colleagues. What You'll Learn Discover why software projects are so commonly delivered late and with an abysmal end product Examine why the relationship between coders and their non-technical colleagues is often strained Understand how the software development process works and how to support it effectively Decipher and use the jargon of software development Keep a team of coders happy and improve the odds of successful software project delivery Who This Book Is For Anyone who employs, contracts, or manages software developers—such as tech startup CEOs, project managers, and clients of digital agencies—and wishes the relationship were easier and more productive. The secondary readership is software developers who want to find ways of working more effectively as part of a team.
Maybe you know FileMaker, and you have used it for years, but need a quick reference, immediately accessible while not interrupting your work on screen. This is the only book on the market expressly focused on describing each calculation formula and how and when to use each! Filled with real-world, concrete examples, this book is an invaluable companion to readers working to develop solutions to their every day software problems. Contains hundreds of calculation functions, script steps, and operations that will appeal to every FileMaker user, new and old.
Author: Capers Jones
Publisher: McGraw Hill Professional
Release Date: 2009-11-05
Proven techniques for software engineering success This in-depth volume examines software engineering topics that are not covered elsewhere: the question of why software engineering has developed more than 2,500 programming languages; problems with traditional definitions of software quality; and problems with common metrics, "lines of code," and "cost per defect" that violate standard economic assumptions. The book notes that a majority of "new" projects are actually replacements for legacy applications, illustrating that data mining for lost requirements should be a standard practice. Difficult social engineering issues are also covered, such as how to minimize harm from layoffs and downsizing. Software Engineering Best Practices explains how to effectively plan, size, schedule, and manage software projects of all types, using solid engineering procedures. It details proven methods, from initial requirements through 20 years of maintenance. Portions of the book have been extensively reviewed by key engineers from top companies, including IBM, Microsoft, Unisys, and Sony. Manage Agile, hierarchical, matrix, and virtual software development teams Optimize software quality using JAD, OFD, TSP, static analysis, inspections, and other methods with proven success records Use high-speed functional metrics to assess productivity and quality levels Plan optimal organization, from small teams through more than 1,000 personnel
Author: Books, LLC
Publisher: Books LLC, Wiki Series
Release Date: 2011-09-04
Please note that the content of this book primarily consists of articles available from Wikipedia or other free sources online. Commentary (books not included). Pages: 53. Chapters: The Art of Computer Programming, Design Patterns, The Mythical Man-Month, In the Beginning... Was the Command Line, Lions' Commentary on UNIX 6th Edition, with Source Code, The Wiki Way, Hackers: Heroes of the Computer Revolution, The Cult of the Amateur, An Army of Davids, The Road Ahead, Jargon File, The Cuckoo's Egg, The C Programming Language, 24 Hours in Cyberspace, Object-Oriented Software Construction, Coders at work, The Soul of a New Machine, Hacking: The Art of Exploitation, Who Controls the Internet?, Communications, Computers, and Networks, The Humane Interface, The Hacker Crackdown, Computer Graphics: Principles and Practice, Core Python Programming, The Ultimate Entrepreneur, Halcyon Days, Head First, Underground, The HTML Sourcebook: The Complete Guide to HTML, Computer: A History of the Information Machine, AntiPatterns, Electronic Life, Reversing: Secrets of Reverse Engineering, Being Digital, Why's Guide to Ruby, De Re Atari, Computers and Typesetting, Open Source for the Enterprise: Managing Risks, Reaping Rewards, Decline and Fall of the American Programmer, Enterprise Integration Patterns, Rise and Resurrection of the American Programmer, The Debian System, The Tao of Programming, The Art of Deception, The Elements of Programming Style, The Unix Programming Environment, Code Complete, Thinking in Java, Agile Web Development with Rails, Peopleware: Productive Projects and Teams, Code Reading, Hitchhiker's Guide to the Internet, Dreaming in Code, The Law of Cyber-Space, Open Sources: Voices from the Open Source Revolution, Literary Machines, Programming Languages: Application and Interpretation, The Pragmatic Programmer, Programming Ruby, C Traps and Pitfalls, The Elements of C Sharp Style, Brute Force: Cracking the Data Encryption Standard, The Oracle J2EE Compani...
See eXtreme Programming (XP) in action at the hands of an XP master—and learn Microsoft .NET and C# programming in the process! In this fast-paced, hands-on exposition, Ron Jeffries—one of the leading voices and practitioners in the XP community—demonstrates that you can write well-designed, resilient code incrementally and safely, while minimizing your investment in speculative up-front design. As Jeffries builds his sample application, you get firsthand insights into what successful XP development looks like, complete with real-world challenges such as the eleventh-hour change order. For further practice and study, you can download all the author's code—including the missteps—so you can see XP and agile concepts in action and assess how they fit into your own work. Pair program with an XP master, discovering how to: Streamline and simplify the software development process Work more effectively as part of an XP development team Reduce missteps by designing, testing, and refining code in increments Receive clearer specifications and feedback from customers Write cleaner, more expressive code—and weed out more bugs Conserve resources by planning and reassessing progress as you go Maintain a sustainable work pace—and avoid burnout Step up delivery dates, shipping the most crucial features first Improve customer satisfaction!