Apress Working With Coders
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 wereeasier and more productive. The secondary readership is software developers who want to find ways of working more effectively as part of a team.
Price now:
From
£4.45
To
£62.90
Price History:
Details:Apress Working With Coders
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 wereeasier and more productive. The secondary readership is software developers who want to find ways of working more effectively as part of a team.
Price now:
From
£4.45
To
£62.90
This site contains affiliate links for which we may be compensated.
eBay
Used
£4.73
eBay
Used
£9.99
Debenhams
0.00% (~ £0.00)
New
£48.17
eBay
New
£62.90
Product Description
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 wereeasier and more productive. The secondary readership is software developers who want to find ways of working more effectively as part of a team.
Product Specifications
General | |
|---|---|
format | trade paperback |
Language | english |
type | textbook |
artist | not specified |
Size | large |
Brand | Apress |
Color | multicolor |
Gender | unisex |
Delivery, Returns & Refunds
Delivery
Sellers offer a range of delivery options, so you can choose the one that’s most convenient for you. Many sellers offer free delivery. You can always find the postage cost and estimated delivery date in a seller’s listing. You'll then be able to see a full list of delivery options during checkout. These can include: Express delivery, Standard delivery, Economy delivery, Click & Collect, Free local collection from seller.
Returns
Your options for returning an item vary depending on what you want to return, why you want to return it, and the seller's return policy. If the item is damaged or doesn't match the listing description, you can return it even if the seller's returns policy says they don't accept returns. If you've changed your mind and no longer want an item, you can still request a return, but the seller doesn't have to accept it. If the buyer changes their mind about a purchase and wants to return an item, they may need to pay return postage costs, depending on the seller's return policy. Sellers can provide a return postage address and additional return postage information for the buyer. Sellers pay for return postage if there's a problem with the item. For example, if the item doesn't match the listing description, is damaged or defective or is counterfeit. By law, customers in the European Union also have the right to cancel the purchase of an item within 14 days beginning from the day you receive, or a third party indicated by you (other than the carrier) receives, the last good ordered by you (if delivered separately). This applies to all products except for digital items (e.g. Digital Music) that are provided immediately to you with your acknowledgement, and other items such as video, DVD, audio, video games, Sex and Sensuality products and software products where the item has been unsealed.
Refunds
Sellers have to offer a refund for certain items only if they are faulty, such as: Personalised items and custom-made items, Perishable items, Newspapers and magazines, Unwrapped CDs DVDs and computer software. If you used your PayPal balance or bank account to fund the original payment, the refunded money will go back to your PayPal account balance. If you used a credit or debit card to fund the original payment, the refunded money will go back to your card. The seller will effect the refund within three working days but it may take up to 30 days for Paypal to process the transfer. For payments funded partially by a card and partially by your balance/bank, the money taken from your card will go back to your card and the remainder will return to your PayPal balance.