Painless Project Management with FogBugz: Edition 2

Apress
Free sample

Project management is the bane of the team approach to programming. Many programs out there purport to help a development team manage a project; the only trouble is, most of them aren’t very good. World-renowned software guru Joel Spolsky’s company, Fog Creek Software, has created a tool called FogBugz that incorporates all of Joel’s insight into what works and what doesn’t work in project management. FogBugz is based on keeping track of a database of cases. At any given time, every case is assigned to one person who must resolve it or forward it to someone else. Cases can be prioritized, documented, sorted, discussed, edited, assigned, estimated, searched, and tracked. Because FogBugz is web-based, everyone on the team always sees the whole picture. Everything from customer feature requests to high-level design discussions to tiny bug fix details is instantly searchable and trackable.

Painless Project Management with FogBugz, Second Edition, written with the guidance of the whole FogBugz team, completely describes the ins and outs of version 6 of FogBugz.

Read more
Collapse

About the author

Mike Gunderloy is a software consultant, writer, and trainer. He has written more than 30 books, including bestseller Coder to Developer: Tools and Strategies for Delivering Your Software.
Read more
Collapse
Loading...

Additional Information

Publisher
Apress
Read more
Collapse
Published on
Oct 20, 2007
Read more
Collapse
Pages
227
Read more
Collapse
ISBN
9781430204879
Read more
Collapse
Read more
Collapse
Best For
Read more
Collapse
Language
English
Read more
Collapse
Genres
Computers / Information Technology
Computers / Software Development & Engineering / General
Read more
Collapse
Content Protection
This content is DRM protected.
Read more
Collapse

Reading information

Smartphones and Tablets

Install the Google Play Books app for Android and iPad/iPhone. It syncs automatically with your account and allows you to read online or offline wherever you are.

Laptops and Computers

You can read books purchased on Google Play using your computer's web browser.

eReaders and other devices

To read on e-ink devices like the Sony eReader or Barnes & Noble Nook, you'll need to download a file and transfer it to your device. Please follow the detailed Help center instructions to transfer the files to supported eReaders.
See what reviewers at Slashdot.org have to say about this book! Conquer the problems that all professional programmers routinely face, regardless of language, operating system, or platform Improve your ability to deliver solid code, on time and under budget, in even the most uncooperative environments Master the self-defense techniques that you need to shield yourself, your project, and your code from corporate politics, arbitrary management decisions, and marketing-driven deadlines

Unrealistic schedules, unstable releases, continual overtime, and skyrocketing stress levels are legendary in the software development industry. Unlike traditional occupations such as accounting or administration, the software business is populated by programmers who are as creative and passionate about their work as musicians or artists. For most, it is a complete surprise when they enter the business world and find that internal politics, inept management, and unrealistic marketing drive the process rather than a structured and orderly approach based on technical issues and quality.

The Career Programmer explains how the individual programmer or project manager can work within the existing system to solve deadline problems and regain control of the development process. Care is taken to offer proven, practical, and hands-on solutions that are designed to work when confronted with the political and chaotic realities of the business environment. Issues are addressed from the points of view of both the programmer and project manager, and steps are shown in all perspectives, from large-scale teams down to projects with a single developer. For the individual programmer or project manager, the end results are less overtime, less stress, higher-quality software, and a more satisfying career.

Most of the project management books on the market are basically textbooks. They are dry to begin with and don't focus on the practical advice that most people need to run their projects. Lessons in Project Management does not assume you are a project manager building a nuclear reactor or sending a man to the moon. Instead, it focuses on the millions of people who manage normal, medium-to-large projects on an ongoing basis.

Each case study in Lessons in Project Management contains accessible, easy-to-read case studies in real-world project management challenges. Each presentation of the problem is followed by an examination of the solution, written in easy-to-understand language.

The format allows you to relate better to the book since it brings into play a project scenario with practical project management lessons to be learned. You'll also recognize recurring characters that appear in multiple stories and you'll start to develop some empathy and interest for their struggle.

Table of Contents Understand the Characteristics of a Project Make Sure You Always Have an Identified and Committed Sponsor and Client Organization Report Status on All Projects (There Are Many Alternatives to the Format and Delivery) Focus on Deadline Dates First When Managing a Project Apply Some Level of Project Management Discipline— Even on Small Projects Define and Plan the Work First to Ensure Better Project Execution Don’t “Microbuild” or Micromanage the Workplan Manage Documents Properly to Avoid Confusion and Mix-Ups Define the Many Aspects of What Is in Scope and out of Scope Use the “Big Three” Documents—Project Definition, Project Workplan, and Requirements—As the Foundation for Your Project Use Scope Change Management to Allow the Sponsor to Make the Final Decision (Many Times the Sponsor Will Say “No”) Collect Metrics to Evaluate How Well You (and Your Project) Are Performing Save Knowledge for Future Projects, Leverage Knowledge from Prior Projects Ensure Issues Management Is Everyone’s Responsibility Shorten Long Meetings to Sharpen the Focus Identify the Root Cause of Problems, Especially If They Are Reoccurring Use Quality Assurance Techniques to Validate the Status of a Project Cancel Projects That Lose Business Support, Relevance, and Focus Use Risk Management to Respond to Problems Before They Occur Focus Your Quality Management on Processes, Not People Don’t Use Your Estimating Contingency for Scope Changes Develop a Communication Plan to Address Complex Communication Requirements Scale Your Project Management Processes Based on the Size of the Project Define and Plan the Project, Even If You Have to Start the Work at the Same Time Understand the Critical Path on Your Project and How This Path Drives the Deadline Date Change the Underlying Assumptions to Revise a Well-Prepared Estimate Don’t Shortchange Face-to-Face Communication on Your Project Make Sure Quality Is a Mindset and an Ongoing Process on Your Project Batch Small Scope Change Requests Together for Sponsor Approval Define the Overall Project Approach Before Building the Detailed Workplan Look for Risks Inherent to Your Project Before You Begin Get Sponsor Approval Before Investigating Large Scope Change Requests Make Sure the Cost of Collecting Metrics Does Not Exceed Their Value Use One or More Formal Techniques to Estimate Project Work Effort Keep Your Workplan Up to Date Throughout the Project Use Issues Management to Help Choose the Best of Bad Alternatives Collect Metrics That Can Lead to Fundamental Improvements Evaluate All Risk Response Options in the Risk Plan Gain a Common Understanding First to Effectively Manage Client Expectations Use Milestones in the Workplan to Track Overall Progress Establish Processes to Catch Errors As Early in the Project As Possible Gain Sponsor Approval for Scope Changes Requiring Budget and Deadline Changes Be Proactive in Applying Techniques to Accelerate the Project Schedule Use the Work Breakdown Structure Technique to Identify All the Work Required for a Project Write Your Status Reports with the Readers’ Interest in Mind Update Your Risk Plan Periodically Throughout the Project Don’t Practice Goldplating—Delivering More Than the Client Requested Make Sure One Person Is Responsible for Each Activity in the Workplan Focus on Your Deadline Date to Keep Your Project from Wandering Collect Metrics, but Gain Agreement on Their Significance Ahead of Time
WINNER of Computing Reviews 20th Annual Best Review in the category Management

“Tyler’s book is concise, reasonable, and full of interesting practices, including some curious ones you might consider adopting yourself if you become a software engineering manager.” —Fernando Berzal, CR, 10/23/2015


“Josh Tyler crafts a concise, no-nonsense, intensely focused guide for building the workhouse of Silicon Valley—the high-functioning software team.” —Gordon Rios, Summer Book Recommendations from the Smartest People We Know—Summer 2016


Building Great Software Engineering Teams provides engineering leaders, startup founders, and CTOs concrete, industry-proven guidance and techniques for recruiting, hiring, and managing software engineers in a fast-paced, competitive environment.

With so much at stake, the challenge of scaling up a team can be intimidating. Engineering leaders in growing companies of all sizes need to know how to find great candidates, create effective interviewing and hiring processes, bring out the best in people and their work, provide meaningful career development, learn to spot warning signs in their team, and manage their people for long-term success.

Author Josh Tyler has spent nearly a decade building teams in high-growth startups, experimenting with every aspect of the task to see what works best. He draws on this experience to outline specific, detailed solutions augmented by instructive stories from his own experience. In this book you’ll learn how to build your team, starting with your first hire and continuing through the stages of development as you manage your team for growth and success. Organized to cover each step of the process in the order you’ll likely face them, and highlighted by stories of success and failure, it provides an easy-to-understand recipe for creating your high-powered engineering team.
Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn’t have to be that way.

Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship . Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code “on the fly” into a book that will instill within you the values of a software craftsman and make you a better programmer–but only if you work at it.

What kind of work will you be doing? You’ll be reading code–lots of code. And you will be challenged to think about what’s right about that code, and what’s wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft.

Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code–of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and “smells” gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code.

Readers will come away from this book understanding
How to tell the difference between good and bad code How to write good code and how to transform bad code into good code How to create good names, good functions, good objects, and good classes How to format code for maximum readability How to implement complete error handling without obscuring code logic How to unit test and practice test-driven development This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.
Practical Software Architecture Solutions from the Legendary Robert C. Martin (“Uncle Bob”)

By applying universal rules of software architecture, you can dramatically improve developer productivity throughout the life of any software system. Now, building upon the success of his best-selling books Clean Code and The Clean Coder, legendary software craftsman Robert C. Martin (“Uncle Bob”) reveals those rules and helps you apply them.

Martin’s Clean Architecture doesn’t merely present options. Drawing on over a half-century of experience in software environments of every imaginable type, Martin tells you what choices to make and why they are critical to your success. As you’ve come to expect from Uncle Bob, this book is packed with direct, no-nonsense solutions for the real challenges you’ll face–the ones that will make or break your projects.

Learn what software architects need to achieve–and core disciplines and practices for achieving it Master essential software design principles for addressing function, component separation, and data management See how programming paradigms impose discipline by restricting what developers can do Understand what’s critically important and what’s merely a “detail” Implement optimal, high-level structures for web, database, thick-client, console, and embedded applications Define appropriate boundaries and layers, and organize components and services See why designs and architectures go wrong, and how to prevent (or fix) these failures

Clean Architecture is essential reading for every current or aspiring software architect, systems analyst, system designer, and software manager–and for every programmer who must execute someone else’s designs.


Register your product for convenient access to downloads, updates, and/or corrections as they become available.

©2019 GoogleSite Terms of ServicePrivacyDevelopersArtistsAbout Google|Location: United StatesLanguage: English (United States)
By purchasing this item, you are transacting with Google Payments and agreeing to the Google Payments Terms of Service and Privacy Notice.