Because without a deeper understanding of the thinking tools and profound organizational redesign needed, it is as though casting seeds on to an infertile field. Now, drawing on their long experience leading and guiding large-scale lean and agile adoptions for large, multisite, and offshore product development, and drawing on the best research for great team-based agile organizations, internationally recognized consultant and best-selling author Craig Larman and former leader of the agile transformation at Nokia Networks Bas Vodde share the key thinking and organizational tools needed to plant the seeds of product development success in a fertile lean and agile enterprise.
Coverage includes Lean thinking and development combined with agile practices and methods Systems thinking Queuing theory and large-scale development processes Moving from single-function and component teams to stable cross-functional cross-component Scrum feature teams with end-to-end responsibility for features Organizational redesign to a lean and agile enterprise that delivers value fast Large-scale Scrum for multi-hundred-person product groups In a competitive environment that demands ever-faster cycle times and greater innovation, applied lean thinking and agile principles are becoming an urgent priority.
Founders at Work: Stories of Startups' Early Days is a collection of interviews with founders of famous technology companies about what happened in the very earliest days. These people are celebrities now. What was it like when they were just a couple friends with an idea?
Where did they get the ideas that made them rich? How did they convince investors to back them? What went wrong, and how did they recover? Nearly all technical people have thought of one day starting or working for a startup.
For them, this book is the closest you can come to being a fly on the wall at a successful startup, to learn how it's done. But ultimately these interviews are required reading for anyone who wants to understand business, because startups are business reduced to its essence. The reason their founders become rich is that startups do what businesses do—create value—more intensively than almost any other part of the economy.
What are the secrets that make successful startups so insanely productive? Read this book, and let the founders themselves tell you. Yet managerial support is often the biggest impediment to successfully adopting Agile, and limiting your Agile efforts to those of the development teams while doing the same old-style management will dramatically limit the ability of your organization to reach the next Agile level.
If you are a manager, team leader, evangelist, change agent or whatever nice title and if you want to push Agile further in your organization, then this is your book. You will read how to change the paradigm of what management is about: it is not about arbitrary decisions, constant supervision and progress control, and the negotiation of changing requirements. We live in a different world than the one that most management experts of the 20th century describe, and companies that strive for success and excellence will need a new kind of manager — Agile managers.
Learn to dump old habits that made sense on mainframes, and pick up the tools you need to use this evolved and aggressively simple language. A series of essays written by some of the leading minds in software testing, How to Reduce the Cost of Software Testing provides tips, tactics, and techniques to help readers accelerate the testing process, improve the performance of the test teams, and lower costs.
The distinguished team of contributors—that includes corporate test leaders, best paper authors, and keynote speakers from leading software testing conferences—supply concrete suggestions on how to find cost savings without sacrificing outcome.
Detailing strategies that testers can immediately put to use to reduce costs, the book explains how to make testing nimble, how to remove bottlenecks in the testing process, and how to locate and track defects efficiently and effectively. Written in language accessible to non-technical executives, as well as those doing the testing, the book considers the latest advances in test automation, ideology, and technology.
About this book Introduction Frustrated by the lack of well-written essays on software engineering, Joel Spolsky of www.
About the authors Joel Spolsky is a globally recognized expert on the software development process. His web site Joel on Software JoelonSoftware. Joel has worked at Microsoft, where he designed Visual Basic for Applications as a member of the Excel team, and at Juno Online Services, developing an Internet client used by millions.
Joel holds a bachelor's of science degree in computer science from Yale University. Before college, he served in the Israeli Defense Forces as a paratrooper, and he was one of the founders of Kibbutz Hanaton. Buy options. To view the log, use the OmniAudit Log Viewer, which provides a variety of filtering mechanisms.
You can narrow the displayed log entries by a particular table or column, a specific user, a date range, or the type of operation performed. The filtering choices are a bit limiting—you can't filter on more than one table, column, or user, for instance—but they will probably be quite sufficient for most users' needs.
Best of all, the Log Viewer requires no knowledge of SQL, so managers and other non-technical resources can review the audit log. Why do so many software projects fail? What 12 factors can you use to quickly rate the likelihood of success for a team of developers? What are the best ways to educate and train people in the art of software development, and how does that compare to what is being taught in university programs today?
These are the sorts of topics addressed by Joel Spolsky on his blog, Joel on Software. In , he cofounded FogCreek Software, which makes FogBugz, a popular project management application. As Joel explains it, "Management's first responsibility is to create an abstraction layer for developers: to create the infrastructure so that programmers really just have to program.
Management's task is to find smart and motivated developers, keep distractions to a minimum, and place the team in an environment to succeed.
Of course, a team of happy and focused programmers does not guarantee a successful software project, but it is an important ingredient. There are other operational and personnel factors that contribute to the ultimate success or failure of a project, which Joel has distilled to 12 checkpoints. While much of Joel on Software is a high-level look at the software industry at large, there is plenty of content for developers, too.
Joel has lots to say about user interface design, testing, and deployment. We've actually seen that in the curve. Whereas, in the early days, Don't assume that you can manage software developers without minimally understanding the nature of the systems they are building.
Even a minimal true interest in the But how to do that? James McLurkin's research focuses on developing distributed algorithms for multi-robot systems, which is software that produces complex group Joel is also author of More Joel on Software , a collection of essays published by Apress. A noted blogger and author of Joel on Software explains how companies can find and hire the best programmers available, offers practical suggestions and tips on how to identify great developers, sort resumes, interview candidates In this brilliantly readable book, author Joel Spolsky proposes simple, logical rules that can be applied without any artistic talent to improve any user interface, from traditional GUI applications to websites to consumer electronics.
One of the most common interaction points short of email, more on that later surely is the meeting. The name alone gives some of us goose bumps because it suggests. I was learning the hard way about how to be a publisher and probably spending way too much time looking at web sites and programming than I should have in response to that. Anyway, one day I came across this web site called , which was run by a guy with strong opinions and an unusual, clever writing style, along with a willingness to take on the conventional wisdom.
And I, like many, was hooked both by the series and the occasional random essay that Joel wrote. And then I had this epiphany: I'm a publisher, I like reading his stuff, why not turn it into a book?
Read the complete Foreword — Gary Cornell, Cofounder, Apress Since the release of the bestselling title Joel on Software in , requests for a sequel have been relentless. So, we went back to the famed JoelonSoftware. With Joel's newest book, More Joel on Software, you'll get an even better not to mention updated feast of Joel's opinions and impressions on software development, software design, running a software business, and so much more. Joel Spolsky started his weblog in March in order to offer his insights, based on years of experience, on how to improve the world of programming.
Spolsky's extraordinary writing skills, technical knowledge, and caustic wit have made him a programming guru. With the success of Joel on Software, there has been a strong demand for additional gems and advice, and this book is the answer to those requests. Containing a collection of all—new articles from the original, More Joel on Software has even more of an edge than the original, and the tips for running a business or managing people have far broader application than the software industry.
We feel it is safe to say that this is the most useful book you will buy this year. This concise book introduces codermetrics, a clear and objective way to identify, analyze, and discuss the successes and failures of software engineers—not as part of a performance review, but as a way to make the team a more cohesive and productive unit.
0コメント