What do you think?
Rate this book
Guide to Software Projects for Business People
In the fast-paced business world of today, as IT moves out from back stage to center stage, business professionals can no longer afford to just leave all that techie stuff to the pros. To optimize the chances of success, core business decisions and software development need to go hand in hand right from the start of any software project.
More and more business people are now reaping the rewards from gaining the essential knowledge of software development to collaborate more closely with IT teams and make better informed choices during a project.
Seasoned IT consultant Jonathan Crosby draws from his knowledge and experience in all kinds of technical challenges across a variety of industries for over 20 years. Emphasizing the power of good communication and effective teamwork, he advocates bringing business into development, and development into business.
This book will act as your guide, explaining the stages of a software project in simple terms. By using metaphors and hand-crafted illustrations, the technical topics become clear and easy to follow.
More and more business people are now reaping the rewards from gaining the essential knowledge of software development to collaborate more closely with IT teams and make better informed choices during a project.
Seasoned IT consultant Jonathan Crosby draws from his knowledge and experience in all kinds of technical challenges across a variety of industries for over 20 years. Emphasizing the power of good communication and effective teamwork, he advocates bringing business into development, and development into business.
This book will act as your guide, explaining the stages of a software project in simple terms. By using metaphors and hand-crafted illustrations, the technical topics become clear and easy to follow.
323 pages, Paperback
Published December 12, 2018
12 people are currently reading
22 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 30 of 37 reviews
January 12, 2022
As someone always looking to expand my knowledge, the IT world is vast and full of things I really don't understand but wish I did. I like to have things broken down into individual pieces so that by putting the whole puzzle together I can gain a more intimate understanding of how a thing/process/etc. works. If you're like me and looking to learn about software and how it can positively impact the business world, this is an excellent place to start.
The author has years of experience in this field and somehow manages to break down all the years of knowledge into 300 pages for someone like me to digest at my own pace. But it's not all technical jargon and sloughing through pages of dense reference material; this book is written in a way that engages the reader by using metaphors and a non condescending voice akin to a "For Dummies" book. The tone throughout the book is conversational and that makes it SO much easier to read. I appreciated that.
This is not your one-stop shop for knowledge of business software, and you most certainly won't be able to say you learned everything you needed to know by reading it, BUT this read will give you a much better understanding how all the 'parts' work and will serve as a reference of sorts for years to come. Awesome building block and foundation for your brain!
The author has years of experience in this field and somehow manages to break down all the years of knowledge into 300 pages for someone like me to digest at my own pace. But it's not all technical jargon and sloughing through pages of dense reference material; this book is written in a way that engages the reader by using metaphors and a non condescending voice akin to a "For Dummies" book. The tone throughout the book is conversational and that makes it SO much easier to read. I appreciated that.
This is not your one-stop shop for knowledge of business software, and you most certainly won't be able to say you learned everything you needed to know by reading it, BUT this read will give you a much better understanding how all the 'parts' work and will serve as a reference of sorts for years to come. Awesome building block and foundation for your brain!
March 26, 2019
This book does not discuss specific software projects that businesses should consider undertaking, as I mistakenly expected for some reason. Instead, it is so much better! It discusses, thoroughly and in an easy-to-follow manner, all of the universal aspects of software development projects that the non-developer team members should understand. The book is quite comprehensive but yet doesn't feel overwhelming at all.
He explains the process of building software through ample use of analogy to physical construction (e.g. foundations, plumbing, blueprints) but unlike in some cases where an analogy gets tired, in this case it's extremely helpful. It's funny how much of the information seems like common sense...after he's told you. But unless you're involved in this kind of work you wouldn't necessarily think about a lot of these elements yourself. This is a testament to the quality of his writing or perhaps more precisely, his teaching style.
I won't get into specifics about what he says because, well, that's his job, isn't it? But I can say that before reading this book, I would've found the prospect of participating in a software development project daunting. I would've felt out of my element and not sure that I could be very useful to the team. But after having read this book, I would confidently walk into a team meeting about software development at any time now. I feel I would understand: what the tech people would need from me in my particular position and what the overall process entails (not just the part where I put in my two cents). I could now carry on a conversation on this topic and sound reasonably informed for a person who is not trained in or expected to understand the technical aspects of coding, but simply the process of development and how the steps, and team members, fit together.
This is worth reading even if you're not expecting to be put in this position right away. You never know, being able to converse with even this level of confidence and fluency about the software development process might land you a leadership role when a project eventually comes up.
He explains the process of building software through ample use of analogy to physical construction (e.g. foundations, plumbing, blueprints) but unlike in some cases where an analogy gets tired, in this case it's extremely helpful. It's funny how much of the information seems like common sense...after he's told you. But unless you're involved in this kind of work you wouldn't necessarily think about a lot of these elements yourself. This is a testament to the quality of his writing or perhaps more precisely, his teaching style.
I won't get into specifics about what he says because, well, that's his job, isn't it? But I can say that before reading this book, I would've found the prospect of participating in a software development project daunting. I would've felt out of my element and not sure that I could be very useful to the team. But after having read this book, I would confidently walk into a team meeting about software development at any time now. I feel I would understand: what the tech people would need from me in my particular position and what the overall process entails (not just the part where I put in my two cents). I could now carry on a conversation on this topic and sound reasonably informed for a person who is not trained in or expected to understand the technical aspects of coding, but simply the process of development and how the steps, and team members, fit together.
This is worth reading even if you're not expecting to be put in this position right away. You never know, being able to converse with even this level of confidence and fluency about the software development process might land you a leadership role when a project eventually comes up.
April 27, 2019
Review Software Projects
Having been an IT professional for over 30 years, mainly working in a support role, I purposely sought out this manual as an aid to moving back into project management. My Prince2 Practitioner qualification expired 5 years ago and I needed a refresh into current best practice.
I was not disappointed.
The first section takes the reader through a ‘Conceptual guide’ using construction – building a house as a metaphor for building a software project. Symbols and practical illustrations are used to reinforce the message – key to which – is that clear lines of communication between all stakeholders is vital throughout every stage of a project lifecycle. This section reads to me like a primer for someone new to the industry and the jargon-free style is deceptively simple and very easy to follow.
Section 2 ‘Practical guide’ focuses on the nitty-gritty hands on elements – the why’s and the how’s of building a successful project, with a holistic approach that identifies all the technical resources required to deliver a successful project. This was the most useful section for me as a business professional – it was the refresh that I needed to help articulate the latest best practices. I’ve worked in Prince and ITIL environments which I’ve found to be somewhat unbending in following strict methodology. The latest flavours appear to be Agile and Waterfall methodology, both new to me. Each looks like a much more practical and flexible approach to software project management.
The final section ‘Techncial guide’ digs deeper and makes use of more technical terminology in highlighting the concepts required for delivering a software project. The Glossary at the end of the manual is an easy to read translation of the terminology used.
Overall, the use of metaphors, analogies, symbols and diagrams is excellent.
Johnathan P. Crosby is a gifted writer that can translate complex issues into everyman language.
I’d recommend that every software house made it compulsive reading for all members of staff - new and experienced. 5 Stars from me.
Having been an IT professional for over 30 years, mainly working in a support role, I purposely sought out this manual as an aid to moving back into project management. My Prince2 Practitioner qualification expired 5 years ago and I needed a refresh into current best practice.
I was not disappointed.
The first section takes the reader through a ‘Conceptual guide’ using construction – building a house as a metaphor for building a software project. Symbols and practical illustrations are used to reinforce the message – key to which – is that clear lines of communication between all stakeholders is vital throughout every stage of a project lifecycle. This section reads to me like a primer for someone new to the industry and the jargon-free style is deceptively simple and very easy to follow.
Section 2 ‘Practical guide’ focuses on the nitty-gritty hands on elements – the why’s and the how’s of building a successful project, with a holistic approach that identifies all the technical resources required to deliver a successful project. This was the most useful section for me as a business professional – it was the refresh that I needed to help articulate the latest best practices. I’ve worked in Prince and ITIL environments which I’ve found to be somewhat unbending in following strict methodology. The latest flavours appear to be Agile and Waterfall methodology, both new to me. Each looks like a much more practical and flexible approach to software project management.
The final section ‘Techncial guide’ digs deeper and makes use of more technical terminology in highlighting the concepts required for delivering a software project. The Glossary at the end of the manual is an easy to read translation of the terminology used.
Overall, the use of metaphors, analogies, symbols and diagrams is excellent.
Johnathan P. Crosby is a gifted writer that can translate complex issues into everyman language.
I’d recommend that every software house made it compulsive reading for all members of staff - new and experienced. 5 Stars from me.
April 29, 2019
When it comes to small and large businesses, software creation is important. In this day and age, the more technology you're dipping your feet into the more people you're going to reach and win over. Even if you feel like software creation is beyond you, this book can help you learn what you need to do, how to do it, and it won't bring on that fear of technology many such guides do.
This book uses basic concept descriptions to help you understand all of the terms that come with software development. Once you're through the section on conceptual design, you'll get to the practical guide where you'll find models, methods, and more.
My favorite parts of the book are the thought-provoking symbols. I found that, as a complete novice in software development, these questions helped me understand a bit more about what I was reading. The author was very creative using metaphors to help with understanding, but it also seemed a little confusing at time, so the extra sections helped.
This book uses basic concept descriptions to help you understand all of the terms that come with software development. Once you're through the section on conceptual design, you'll get to the practical guide where you'll find models, methods, and more.
My favorite parts of the book are the thought-provoking symbols. I found that, as a complete novice in software development, these questions helped me understand a bit more about what I was reading. The author was very creative using metaphors to help with understanding, but it also seemed a little confusing at time, so the extra sections helped.
May 3, 2020
Jonathan P. Crosby's book is a universal IT explainer for non-developers. It is a comprehensive and easily navigated guide to how software development works without any of the jargon.
"Helping teams to achieve higher success rates in software projects is one of the main goals of this book," wrote Crosby. "The key is to establish common ground on software project concepts amongst all the stakeholders in your project. When creating software, some poor judgments are made that would never be made when building or renovating a house."
Crosby breaks the book down into three sections with conceptual, practical, and technical guides. As an IT professional with 20 years experience, he knows how important it is for teams to understand software and communicate effectively. He advises that when people (from small business owners to corporate leaders) understand software, they will be able to be more involved. Companies may even perform better over time.
"Helping teams to achieve higher success rates in software projects is one of the main goals of this book," wrote Crosby. "The key is to establish common ground on software project concepts amongst all the stakeholders in your project. When creating software, some poor judgments are made that would never be made when building or renovating a house."
Crosby breaks the book down into three sections with conceptual, practical, and technical guides. As an IT professional with 20 years experience, he knows how important it is for teams to understand software and communicate effectively. He advises that when people (from small business owners to corporate leaders) understand software, they will be able to be more involved. Companies may even perform better over time.
October 30, 2020
I loved this book so much. Being from the tech field myself, I often find myself working with people coming from two different worlds : both on the top of their fields, both thinking the other is “dumb since they don’t understand software” (I’ve heard this, verbatim, more than once”.
I always wanted a book or a seminar or something that will help bridge the gap between the tech team and The business team. Enter this book. this book does does just that.
It is written so beautifully and perfectly that even people with no tech background at all can easily understand it the author has definitely been in a position where they have Work with people who did not understand why the software was costing so much, why the maintenance was so much why can’t we do this “one thing extra”, in short, why does this have to cost so much money?
This happens because people sitting at the top of businesses, even people sitting in small businesses didn’t go to school to learn software and it’s always considered as one of these things that you cannot easily learn but that is not true and this book bridges that up.
The author explains the entire terminology and all the concepts of the software engineering class from like two semesters or even three semesters in very easy to understand language using so many mad force that makes people understand it easily no matter what background you are from you will understand the metaphors and comparisons. everybody understands how a house is built everybody knows about house maintenance everybody knows about the importance of having a strong foundation.
My absolutely favorite quote from the book is “they expect a the hogwarts castle on the budget of an igloo”.
It is so important to understand the concept of technical debt sometimes it is easier to build something from scratch than year after year maintain edge which will cost so much more money. It is so important to document everything so the handoff can be easier and this book explains everything in detail
. The author goes into the details by not going into the details which are bore people but keeps it where it’s so easy to grasp.
I would recommend this book to everybody. You could be a software developer, in high school, in college, working in the industry, are you could be the business person or you could be a small business owner this book is for everybody who wants to understand how technology works and how a software is built.
I think it will help you appreciate the tech team is a little bit more and also bridge the gap between the two teams to the point where they actually might start liking each other because they understand both sides of the story.
I always wanted a book or a seminar or something that will help bridge the gap between the tech team and The business team. Enter this book. this book does does just that.
It is written so beautifully and perfectly that even people with no tech background at all can easily understand it the author has definitely been in a position where they have Work with people who did not understand why the software was costing so much, why the maintenance was so much why can’t we do this “one thing extra”, in short, why does this have to cost so much money?
This happens because people sitting at the top of businesses, even people sitting in small businesses didn’t go to school to learn software and it’s always considered as one of these things that you cannot easily learn but that is not true and this book bridges that up.
The author explains the entire terminology and all the concepts of the software engineering class from like two semesters or even three semesters in very easy to understand language using so many mad force that makes people understand it easily no matter what background you are from you will understand the metaphors and comparisons. everybody understands how a house is built everybody knows about house maintenance everybody knows about the importance of having a strong foundation.
My absolutely favorite quote from the book is “they expect a the hogwarts castle on the budget of an igloo”.
It is so important to understand the concept of technical debt sometimes it is easier to build something from scratch than year after year maintain edge which will cost so much more money. It is so important to document everything so the handoff can be easier and this book explains everything in detail
. The author goes into the details by not going into the details which are bore people but keeps it where it’s so easy to grasp.
I would recommend this book to everybody. You could be a software developer, in high school, in college, working in the industry, are you could be the business person or you could be a small business owner this book is for everybody who wants to understand how technology works and how a software is built.
I think it will help you appreciate the tech team is a little bit more and also bridge the gap between the two teams to the point where they actually might start liking each other because they understand both sides of the story.
January 5, 2022
Jonathan Crosby has exceeded all expectations with his guide for business people. As an enthusiastic yet time-restricted businesswoman, I very much appreciated the anecdotal style and real-world scenarios with which Software issues are explained. The narration of the audiobook version was captivating, easy to follow, and never faltered. While it is often the case that either the narrator or the author takes the spotlight one over the other, this is not so with this guide. Both the narrator and the author work seamlessly together, resulting in an undemanding experience for the listener. The flow is pleasant, with the movement between chapters clear and concise. There was never a sense of feeling disconnected throughout the listening.
Metaphors and analogies play an integral role in the content which succeeds in demystifying what might otherwise be inconceivable to those tech-retards among us. Regardless, the content is not at all too dumbed down for even the software developers dipping a toe in the depths of the IT world. What a brilliant idea to explain the building of software in terms of the physical construction of a house or building. Since I can understand the concepts of architecture, this means of explanation certainly helped me to understand software development even though it has always been an enigma to me. The use of quotes throughout the audiobook lends a certain distinct edge to the listening, breaking the narration into varying styles which I found appealing, and which held my interest.
The book is divided into 3 main parts (Conceptual, Practical, and Technical guides) which proves invaluable for the non-IT-business person who is not au fait with software development. The structure first introduces core concepts of software projects before delving into the more practical side, and then more in-depth still into the technical aspects.
No matter the role-player in a business, how the content is delivered will be invaluable as a guide to the creation of software. There is a certain appreciation too for the concise references and further reading sections which suggest resources of potential interest to the listener.
Metaphors and analogies play an integral role in the content which succeeds in demystifying what might otherwise be inconceivable to those tech-retards among us. Regardless, the content is not at all too dumbed down for even the software developers dipping a toe in the depths of the IT world. What a brilliant idea to explain the building of software in terms of the physical construction of a house or building. Since I can understand the concepts of architecture, this means of explanation certainly helped me to understand software development even though it has always been an enigma to me. The use of quotes throughout the audiobook lends a certain distinct edge to the listening, breaking the narration into varying styles which I found appealing, and which held my interest.
The book is divided into 3 main parts (Conceptual, Practical, and Technical guides) which proves invaluable for the non-IT-business person who is not au fait with software development. The structure first introduces core concepts of software projects before delving into the more practical side, and then more in-depth still into the technical aspects.
No matter the role-player in a business, how the content is delivered will be invaluable as a guide to the creation of software. There is a certain appreciation too for the concise references and further reading sections which suggest resources of potential interest to the listener.
January 11, 2022
Jonathan Crosby gets 5 stars from me as he certainly proves that he knows his tech stuff inside and out. I was impressed in how he makes everything easy to understand and you can tell he has had lots of experience with software development. This book is not meant to teach businesspeople how to program but gives an easy-to-understand guidebook with an overview of what’s involved in creating and maintaining software. He divides the book into three parts with a conceptual guide, the practical guide, and then the technical side.
I love the way Crosby uses metaphors from the construction industry to explain the elements needed when developing software. He emphasizes that mistakes will happen but if everyone works together to find solutions with good and effective communication between all parties involved, things will go much better. He even devotes a couple of chapters to the importance of effective communication. He also explains some of the mistakes made during the project preparation stage to help you avoid them as well as how to fix problems later and the importance of training. I like how he places little symbols to summarize important points throughout the book that are meant to encourage consideration of how a topic is handled or show important advice to help keep a project on the right track. I loved all his other metaphors such as the deep entangled roots of a tree being like the many features built into software over the years that can still be relevant and replacing such an interwoven system would not be easy.
Crosby goes into how the project team should sit with users to see how they engage with the software. He does a great job of explaining terms and aspects in developing and maintaining a software system as well as many coding and testing terms. I appreciated how he outlines what coding and software engineering work entails as my son is a web developer and this helps me understand what he does as well as why he needs to work long hours at times.
The Appendices also have lots of great information on how to improve on communications, meetings, giving presentations, sharing knowledge, and more. Methodology and tools that work for large internet enterprises like Amazon or Facebook might not work for a smaller company, but your website can run just as smooth as theirs if you read this book.
I love the way Crosby uses metaphors from the construction industry to explain the elements needed when developing software. He emphasizes that mistakes will happen but if everyone works together to find solutions with good and effective communication between all parties involved, things will go much better. He even devotes a couple of chapters to the importance of effective communication. He also explains some of the mistakes made during the project preparation stage to help you avoid them as well as how to fix problems later and the importance of training. I like how he places little symbols to summarize important points throughout the book that are meant to encourage consideration of how a topic is handled or show important advice to help keep a project on the right track. I loved all his other metaphors such as the deep entangled roots of a tree being like the many features built into software over the years that can still be relevant and replacing such an interwoven system would not be easy.
Crosby goes into how the project team should sit with users to see how they engage with the software. He does a great job of explaining terms and aspects in developing and maintaining a software system as well as many coding and testing terms. I appreciated how he outlines what coding and software engineering work entails as my son is a web developer and this helps me understand what he does as well as why he needs to work long hours at times.
The Appendices also have lots of great information on how to improve on communications, meetings, giving presentations, sharing knowledge, and more. Methodology and tools that work for large internet enterprises like Amazon or Facebook might not work for a smaller company, but your website can run just as smooth as theirs if you read this book.
January 12, 2022
It is frustrating when a person in charge of a team or organisation has no inkling about the basics of what they are managing. I see this happen in education, medicine, and finance with people in senior positions making crucial calls about what they know little or nothing about. This book is about fixing that, especially in the world of IT.
Guide to Software Projects for Business People is a technical book written for non-specialists working in the world of software development. As the title suggests, this is a book written for people who are responsible for decision-making within the field but do not possess the specialist knowledge needed to manage such projects.
WHAT I LIKE IN THIS BOOK
The primacy of words over images is very much rooted in Western civilization. Fortunately, there are now people realising that this philosophy is very much flawed. Many are waking up to the fact that art is actually an elevated form of communication, and if wielded correctly, can transform a subject. Guide to Software Projects for Business People is a book that embraces this ethos. The use of several illustrations to explain some of the themes in the book brings so much light and understanding to the topics, especially for some of those who have little to no idea about key ideas in the world of software projects.
Also, the utilisation of metaphors in this book work in the same way as the images - it simplifies, yet illuminates complex topics in a way that makes any novice able to understand them quickly as well as able to articulate what they have learned. Just like the illustrations, metaphors paint a vivid picture in our minds, linking new knowledge with what we already know.
DISLIKES
I don't like to admit it, but I find no issues to raise here.
WHO IS IT FOR
In my opinion, I think this is a book that is mainly for decision-makers (business and IT people) in the world of software development, especially those with inadequate knowledge about the inner workings of the discipline. Topics like outsourcing, different methods of software development and the ideal situation to use them, software development planning, etc are all covered here and would benefit such individuals.
Highly recommended.
Guide to Software Projects for Business People is a technical book written for non-specialists working in the world of software development. As the title suggests, this is a book written for people who are responsible for decision-making within the field but do not possess the specialist knowledge needed to manage such projects.
WHAT I LIKE IN THIS BOOK
The primacy of words over images is very much rooted in Western civilization. Fortunately, there are now people realising that this philosophy is very much flawed. Many are waking up to the fact that art is actually an elevated form of communication, and if wielded correctly, can transform a subject. Guide to Software Projects for Business People is a book that embraces this ethos. The use of several illustrations to explain some of the themes in the book brings so much light and understanding to the topics, especially for some of those who have little to no idea about key ideas in the world of software projects.
Also, the utilisation of metaphors in this book work in the same way as the images - it simplifies, yet illuminates complex topics in a way that makes any novice able to understand them quickly as well as able to articulate what they have learned. Just like the illustrations, metaphors paint a vivid picture in our minds, linking new knowledge with what we already know.
DISLIKES
I don't like to admit it, but I find no issues to raise here.
WHO IS IT FOR
In my opinion, I think this is a book that is mainly for decision-makers (business and IT people) in the world of software development, especially those with inadequate knowledge about the inner workings of the discipline. Topics like outsourcing, different methods of software development and the ideal situation to use them, software development planning, etc are all covered here and would benefit such individuals.
Highly recommended.
January 8, 2022
All projects need planning and so is creating a good prototype. This, however, doesn't guarantee a mistake-free environment but it saves a software developer a lot more avoidable problems.
This book guides us through the fundamentals for a good employer-employee relationship. The author, through an intriguing narrator, takes us through the basics of software development and how to ensure the success of a project through metaphors.
The metaphors are so relatable that the IT concepts become easy to swallow.
This book is insightful, not only to people in IT but generally for business people.
Communication and conflict resolution are talked about. The effectiveness of a good talk between people in the same organization could yield unexpectedly good results.
Teamwork and team building are also themes in this insightful business guide.
I felt the narrator teaching me in a friendly tone. There was never a dull moment.
Quotes from different persons (ranging from Steve Jobs to anonymous) are also incorporated, and they kickstart each chapter on a high note: My favorite being,
a man in debt is a man in chains.
I was enlightened on new technologies and the challenges that come in handy. This book also aroused my interest in coding and building and construction.
The points that hit home were; prioritizing projects, being more innovative, and reacting quickly to stay on top.
I'd recommend this read to anyone in business, also to managers and team leaders.
This book guides us through the fundamentals for a good employer-employee relationship. The author, through an intriguing narrator, takes us through the basics of software development and how to ensure the success of a project through metaphors.
The metaphors are so relatable that the IT concepts become easy to swallow.
This book is insightful, not only to people in IT but generally for business people.
Communication and conflict resolution are talked about. The effectiveness of a good talk between people in the same organization could yield unexpectedly good results.
Teamwork and team building are also themes in this insightful business guide.
I felt the narrator teaching me in a friendly tone. There was never a dull moment.
Quotes from different persons (ranging from Steve Jobs to anonymous) are also incorporated, and they kickstart each chapter on a high note: My favorite being,
a man in debt is a man in chains.
I was enlightened on new technologies and the challenges that come in handy. This book also aroused my interest in coding and building and construction.
The points that hit home were; prioritizing projects, being more innovative, and reacting quickly to stay on top.
I'd recommend this read to anyone in business, also to managers and team leaders.
January 12, 2022
Although the book title says it is for business people, I think it is highly useful for IT professionals as well because software development pitfalls are relevant to both types of personnel.
Being a non-technical person, I have found this book very informative; in fact, it has provided me with a comprehensive view of software development.
Specifically, the book gives the reader a perspective of the whole process, and by “perspective”, I don’t mean the knowledge of the number of steps involved but the actual picture of how these steps are taken by software development teams and where precisely the problems arise which affect the successful development and implementation of the software package.
The reader can easily acquire this understanding because of the engaging writing style of Jonathan. Especially, I liked the use of metaphors and analogies throughout the book that made it a lot easier to comprehend the actual process. In fact, I started to believe that software development is just like a construction project until Jonathan highlighted the main differences. So, I would definitely say that he has made an extensive effort in keeping the reader informed and his understanding correct.
I will also appreciate the excellent use of illustrations and learning checks that significantly increased my engagement level every time I thought the text was becoming boring. Also, the book has very insightful references that I have saved for my later use to increase my technical understanding.
However, apart from these positive factors, I noticed poor craft at a few places that made the reading annoying to some extent. Sometimes the sentences are too short or repetitive, making it hard to get the real meaning out of them.
Apart from this, the book is a definite read for business and IT professionals to develop a shared understanding and successfully lead the software development.
Five stars, obviously!
Being a non-technical person, I have found this book very informative; in fact, it has provided me with a comprehensive view of software development.
Specifically, the book gives the reader a perspective of the whole process, and by “perspective”, I don’t mean the knowledge of the number of steps involved but the actual picture of how these steps are taken by software development teams and where precisely the problems arise which affect the successful development and implementation of the software package.
The reader can easily acquire this understanding because of the engaging writing style of Jonathan. Especially, I liked the use of metaphors and analogies throughout the book that made it a lot easier to comprehend the actual process. In fact, I started to believe that software development is just like a construction project until Jonathan highlighted the main differences. So, I would definitely say that he has made an extensive effort in keeping the reader informed and his understanding correct.
I will also appreciate the excellent use of illustrations and learning checks that significantly increased my engagement level every time I thought the text was becoming boring. Also, the book has very insightful references that I have saved for my later use to increase my technical understanding.
However, apart from these positive factors, I noticed poor craft at a few places that made the reading annoying to some extent. Sometimes the sentences are too short or repetitive, making it hard to get the real meaning out of them.
Apart from this, the book is a definite read for business and IT professionals to develop a shared understanding and successfully lead the software development.
Five stars, obviously!
November 20, 2021
I would recommend - Guide to Software Projects for Business People by Jonathan P. Crosby to all people. This book is must for all non-tech people to learn not just different phases of the Software Project Life Cycle but golden opportunity to understands the technical terms , problems and get to know the challenges since inception of the project till Post Production maintenance activities after successful deployment.
I really enjoyed reading all 3 parts of the Books - Conceptual Guide , Practical Guide and Technical Guide.
Frankly , I would appreciate the efforts put by author to make the technical subjects so simple for business people in easy language without using any code blocks.
Every chapter starts with quotes and many metaphors and analogies are used to help describe the technical concepts in clear and interesting way. Appendix , Glossary and references and further reading sections at end of the book are also available and explain the technical stuff in easy language.
Sketches are neat and self explanatory in nature. Author emphasize the importance of communication in each stage of the project lifecycle.
Nowadays buzzword is Digital Transformation and I do concur with the quote mentioned by Jonathan that 'Digital Transformation is not an IT Project , It is about changing the whole organisation culture.' Reading this book will help you become more confident , knowledgeable if your interest is in Software Projects and you are from non-technical background. So , it all depends on your current role and interests.
I would congrats Jonathan for bringing awesome title for everyone viz. Students , Business Practitioners and people who don't have any formal education in technical computer science subjects.You won't feel boredom even after rereading the book.
I really enjoyed reading all 3 parts of the Books - Conceptual Guide , Practical Guide and Technical Guide.
Frankly , I would appreciate the efforts put by author to make the technical subjects so simple for business people in easy language without using any code blocks.
Every chapter starts with quotes and many metaphors and analogies are used to help describe the technical concepts in clear and interesting way. Appendix , Glossary and references and further reading sections at end of the book are also available and explain the technical stuff in easy language.
Sketches are neat and self explanatory in nature. Author emphasize the importance of communication in each stage of the project lifecycle.
Nowadays buzzword is Digital Transformation and I do concur with the quote mentioned by Jonathan that 'Digital Transformation is not an IT Project , It is about changing the whole organisation culture.' Reading this book will help you become more confident , knowledgeable if your interest is in Software Projects and you are from non-technical background. So , it all depends on your current role and interests.
I would congrats Jonathan for bringing awesome title for everyone viz. Students , Business Practitioners and people who don't have any formal education in technical computer science subjects.You won't feel boredom even after rereading the book.
January 17, 2022
The book title does not mislead. This is, without question, a Guide to Software Projects for Business People.
I consider myself someone who knows a great deal about websites, apps, etc., and can understand a lot of the “backend” work that goes into programming and web development as a whole. That being said, even I learned quite a bit from reading this book. I won’t give away any spoilers, but the analogies and the quotes throughout the book brought a lot into perspective. I actually bookmarked several pages and highlighted several more.
Business people (Owners, CEOs, Non-Profit project managers— everyone delegating tech work to programmers) would absolutely benefit from reading this. I’ve referred this book to friends who are programmers and web designers/developers so they can suggest it to the higher ups within the organizations they work in. I firmly believe a lot of money, stress and time would be saved on website/app/programming costs if at least one higher up read this book.
The only downside is that it could be considered a long read for someone who a) has a short attention span, or b) finds reading comforting and begins to drift off. The latter may not be a con for most 😉
This book gets 5 stars from me!
I consider myself someone who knows a great deal about websites, apps, etc., and can understand a lot of the “backend” work that goes into programming and web development as a whole. That being said, even I learned quite a bit from reading this book. I won’t give away any spoilers, but the analogies and the quotes throughout the book brought a lot into perspective. I actually bookmarked several pages and highlighted several more.
Business people (Owners, CEOs, Non-Profit project managers— everyone delegating tech work to programmers) would absolutely benefit from reading this. I’ve referred this book to friends who are programmers and web designers/developers so they can suggest it to the higher ups within the organizations they work in. I firmly believe a lot of money, stress and time would be saved on website/app/programming costs if at least one higher up read this book.
The only downside is that it could be considered a long read for someone who a) has a short attention span, or b) finds reading comforting and begins to drift off. The latter may not be a con for most 😉
This book gets 5 stars from me!
January 12, 2022
Ok, can we just pause for a moment and give a high five to the author? WOW!
My brother who is an IT genius, was extremely impressed by the author’s ability to not just convey a message to non-developers, but also IT professionals.
Well, I’m no IT professional (actually I know nothing about software development), and I found this book humorous, and packed with valuable information.
This book by Jonathan P. Crosby is a universal IT explanation for non-developers -and apparently, IT genuises like my brother. It is a detailed and easy-to-use tutorial that guides the reader on how software development works without giving you a headache.
It’s ideal for individuals and teams who want to succeed in software projects. The author has more than 20 years of experience in the IT field, and it shows. Additionally, he gives great advice on communication and teamwork.
The book is divided into three parts; a conceptual guide, a practical guide, and the technical guide. Crosby’s best practices advice and red flag warnings may save businesses time, money, and energy. This book would benefit anybody embarking on a software project of any scale.
What did I like the most about this book? Crosby’s ability to explain complex IT terms in the simplest ways by using metaphors. Literally, anyone would be able to understand the metaphors.
I loved how he compared software construction to building/house construction. All the planning that goes into building a house is similar to software construction. He also explains how crucial planning is, how to avoid/deal with mistakes, how to change some features of the “house” and how to maintain your “house”
Crosby used excellent references throughout the book- which is a bonus since I like double-checking statements. Lastly, the technical terms at the end of the book made reading IT talk a walk in the park.
I highly recommend this book, after reading this I am eager to learn even more.
My brother who is an IT genius, was extremely impressed by the author’s ability to not just convey a message to non-developers, but also IT professionals.
Well, I’m no IT professional (actually I know nothing about software development), and I found this book humorous, and packed with valuable information.
This book by Jonathan P. Crosby is a universal IT explanation for non-developers -and apparently, IT genuises like my brother. It is a detailed and easy-to-use tutorial that guides the reader on how software development works without giving you a headache.
It’s ideal for individuals and teams who want to succeed in software projects. The author has more than 20 years of experience in the IT field, and it shows. Additionally, he gives great advice on communication and teamwork.
The book is divided into three parts; a conceptual guide, a practical guide, and the technical guide. Crosby’s best practices advice and red flag warnings may save businesses time, money, and energy. This book would benefit anybody embarking on a software project of any scale.
What did I like the most about this book? Crosby’s ability to explain complex IT terms in the simplest ways by using metaphors. Literally, anyone would be able to understand the metaphors.
I loved how he compared software construction to building/house construction. All the planning that goes into building a house is similar to software construction. He also explains how crucial planning is, how to avoid/deal with mistakes, how to change some features of the “house” and how to maintain your “house”
Crosby used excellent references throughout the book- which is a bonus since I like double-checking statements. Lastly, the technical terms at the end of the book made reading IT talk a walk in the park.
I highly recommend this book, after reading this I am eager to learn even more.
January 11, 2022
What’s that one factor that deters success in software projects? Of course, there are many, but a key component is the business team. In today’s era where business and technology are linked together completely, getting the business team involved can bring in great success.
Businesses need to gain knowledge on software development and collaborate with IT teams. Business teams can no longer afford to stay away leaving all that is technical to the tech team. They need to work together in unison to see results.
IT consultant Jonathan Crosby brings in his expertise and experience of working for over 20 years in this book. He lays bare his knowledge and the technical challenges faced. From planning to the power of good communication to effective teamwork he advocates how business and software development must merge their borders to together deliver results.
With the book you can:
Take better decisions for your team members as well as for the business. Understand core concepts of software projects easily. Dwell into the practical side of projects.
Make a positive impact on your current or future project with a sound understanding of the processes.
Businesses need to gain knowledge on software development and collaborate with IT teams. Business teams can no longer afford to stay away leaving all that is technical to the tech team. They need to work together in unison to see results.
IT consultant Jonathan Crosby brings in his expertise and experience of working for over 20 years in this book. He lays bare his knowledge and the technical challenges faced. From planning to the power of good communication to effective teamwork he advocates how business and software development must merge their borders to together deliver results.
With the book you can:
Take better decisions for your team members as well as for the business. Understand core concepts of software projects easily. Dwell into the practical side of projects.
Make a positive impact on your current or future project with a sound understanding of the processes.
January 8, 2022
Read my full review here: https://savoryourreads.com/2022/01/gu...
September 23, 2020
Amazing. Simply wow! One of the most thorough books I have ever read.
Jonathan demystifies this topic like none I have ever read or heard about in my 30+ years of tech and business adventures. His use of metaphors throughout is consistent and spot on. Then, at the end of the book he explains metaphors, similes, and analogies. In fact a whole chapter’s worth!
Consider 21 occurrences of the word “Waterfall” — an outdated software development methodology still in use while most organizations have moved on to various Agile oriented approaches. Here, an example of the writing style [and the graceful, relaxed tenor] of the author:
“Currently, the dominant Agile software methodology is Scrum, which is a framework for organizing the people, the product, the communication and the work, using time-boxed sprints.”
Did I mention the tons of quotes and references of leaders in the fields of technology, computer science, and business? Thought leaders like Dr. Eli Goldratt, Ben Horowitz, and Scott Hanselman. In fact, I learned a few terms I didn’t know existed. Like “technical debt” for example:
“Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice.”
Have you picked up on the fact you should read this book regardless your experiences? Great. My work here is done.
Enjoy
Jonathan demystifies this topic like none I have ever read or heard about in my 30+ years of tech and business adventures. His use of metaphors throughout is consistent and spot on. Then, at the end of the book he explains metaphors, similes, and analogies. In fact a whole chapter’s worth!
Consider 21 occurrences of the word “Waterfall” — an outdated software development methodology still in use while most organizations have moved on to various Agile oriented approaches. Here, an example of the writing style [and the graceful, relaxed tenor] of the author:
“Currently, the dominant Agile software methodology is Scrum, which is a framework for organizing the people, the product, the communication and the work, using time-boxed sprints.”
Did I mention the tons of quotes and references of leaders in the fields of technology, computer science, and business? Thought leaders like Dr. Eli Goldratt, Ben Horowitz, and Scott Hanselman. In fact, I learned a few terms I didn’t know existed. Like “technical debt” for example:
“Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice.”
Have you picked up on the fact you should read this book regardless your experiences? Great. My work here is done.
Enjoy
July 1, 2019
As someone who owns my own business, I’ve read a few technical how-to manuals that are supposed to enlighten me with some practical information about topics like software, accounting, and SEO—but even the best intentioned works often come across as War and Peace-sized epics filled with confusing jargon and a bombardment of directions.
What they’re all lacking is what fills the pages of Jonathan Crosby’s Guide to Software Projects for Business People: metaphors.
Using simple daily objects and concepts we can all relate to, Crosby breaks down the invisible world of IT in digestible terms. This book will allow you to have smoother conversations with and more reasonable expectations of your IT people. It can also serve as a decent starting point for your own dabbling in the backend of software.
What they’re all lacking is what fills the pages of Jonathan Crosby’s Guide to Software Projects for Business People: metaphors.
Using simple daily objects and concepts we can all relate to, Crosby breaks down the invisible world of IT in digestible terms. This book will allow you to have smoother conversations with and more reasonable expectations of your IT people. It can also serve as a decent starting point for your own dabbling in the backend of software.
March 15, 2020
Great book for small business owners!
Excellent book for those who do not identify with being “tech-savvy.” Initially, I (self-proclaimed, partial Luddite) thought this book was a how-to book for small business owners. However, I was mistaken—it is much more! This book explains in great detail and easy-to-understand explanations of terms and sequencing of steps for building, maintaining, and understanding the logistics and creation for software. I do plan to read this book a second time—much I didn’t fully grasp the first read.
Jonathan P. Crosby certainly has a talent for writing succinctly and clearly about software and can explain complex concepts to those with little to no prior knowledge about software. Also, this book is not only for small business owners—an excellent resource for those wanting to learn more about software engineering and development!
Excellent book for those who do not identify with being “tech-savvy.” Initially, I (self-proclaimed, partial Luddite) thought this book was a how-to book for small business owners. However, I was mistaken—it is much more! This book explains in great detail and easy-to-understand explanations of terms and sequencing of steps for building, maintaining, and understanding the logistics and creation for software. I do plan to read this book a second time—much I didn’t fully grasp the first read.
Jonathan P. Crosby certainly has a talent for writing succinctly and clearly about software and can explain complex concepts to those with little to no prior knowledge about software. Also, this book is not only for small business owners—an excellent resource for those wanting to learn more about software engineering and development!
May 13, 2019
This book is a crash course to help guide you through everything a software project entails in todays world. It touches the good, bad, ugly and what the business stakeholders need to know in order to deliver a successful and efficient project. I have a Masters in Computer Science and i was surprised to see that the author pretty much gave a real world practical overview of what I studied for years in the university. His construction analogies makes it so simple and easy to understand the software pitfalls without all the IT tech buzz words. I highly recommend this book to business stakeholder and architects who try to create a product without understanding how software works.
August 16, 2020
The heavy name on the book had me dreading to read the book but since I was trying to get more information about technical know how and converse better with my engineer friend, this book was a life saver.
Dispelling all my apprehension, this book is easy to read and very much made for non technical people like me. I could easily understand the stuff written and actually gave me ammo to have meaningful conversations with my friends without sounding like a fool.
It’s a must read for people getting in to software projects without a technical background.
Dispelling all my apprehension, this book is easy to read and very much made for non technical people like me. I could easily understand the stuff written and actually gave me ammo to have meaningful conversations with my friends without sounding like a fool.
It’s a must read for people getting in to software projects without a technical background.
May 28, 2019
Crosby does a good job here of addressing the needs of anyone who has a business but lacks the information technology (IT) savvy to be able to learn how to do IT projects for their business on their own. For the cost of this book, it could drastically cut down on the expenses that a businessperson, even a small businessperson has for their IT department by learning some IT projects that will help to improve their profits and their overall revenue. Indie Reviewers does not pay their writers.
February 26, 2020
The book is articulate and intelligently written. The subject matter creates an understanding far beyond what is initially configured. A software project is best handled by people who know their jobs. A self owned code is far more important than getting fast tracked by buying into pre written snippets or even buying the whole software.
January 6, 2022
Jonathan P. Crosby’s Guide to Software Projects for Business People: digital transformation is a book that gives insight into the nature and descriptions of software projects as well as certain steps programmers or techies undertake to bring a project or feature to fruition. Based on the experiences and knowledge of the author, he recommended certain rules or practices to adopt in peculiar circumstances, while listing their pros and cons. The author divided the book into three parts; the conceptual, practical, and technical guide. Incorporated in these parts are various headings dedicated to relevant concepts.
The role of technology in giving businesses a competitive advantage and selling their products or services reflects the need to leverage technology by businesses in the 21st century. Most enterprises, if not all, in the United States and other countries, have recognized this. However, adopting technology is not as easy as it seems, and requires expertise, knowledge, and precision. Thus, technology can only aid business when it is leveraged well. Furthermore, a lesson that stood out for me in this book is that businesses and programmers (or techies) must work together for the successful and effective utilisation of technology. Overall, this book contains tips for achieving successful software projects.
This is a technology-related book and understanding or flowing with it may be the concern of non-techie readers. However, the author employed many strategies to ensure that readers understand and appreciate this book to a large extent. My favourite topic under the “Conceptual Guide” is “Conceptual Mistakes.” This is because Crosby used real-life events to explain them. This made for an easy understanding and appreciation of the topic. Under that heading, the author wrote about mistakes that can occur at the initial stage of a project, which can have consequences. An event that happened in London Heathrow Airport was used to illustrate the point. Furthermore, the use of quotes and the author’s work experiences created a vivid picture in my mind, aiding in my understanding of the concepts. Ordinarily, repetitions could be tedious to read. However, I found the ones in this book to be relevant for emphasis and for a better understanding of crucial points. To allow readers to unravel all the education and insightful comments in this book, I would not want to reveal any more details. Furthermore, this book was excellently edited, and you will not be distracted by errors.
I, however, have a grouse about this book. It is quite an extensive and deep read, and as a result, there were so many headings and subheadings. However, asides from the headings (and parts) at the beginning of chapters, several subheadings were not numbered. Due to the nature of the book, I felt numbering them will aid readers in flowing with it. As a result, I felt a bit overwhelmed, and it was a tad difficult to flow constantly with the book.
Considering the importance of this book in the business/technology world today, I will rate this book four out of five stars. I deducted one star because of my complaint about it. Other than that, this book is worth every bit of your time. Therefore, I am recommending it to all business persons or even software developers working or aspiring to work with enterprises. This is because the lessons and information contained in it will be helpful in their professional relationship.
The role of technology in giving businesses a competitive advantage and selling their products or services reflects the need to leverage technology by businesses in the 21st century. Most enterprises, if not all, in the United States and other countries, have recognized this. However, adopting technology is not as easy as it seems, and requires expertise, knowledge, and precision. Thus, technology can only aid business when it is leveraged well. Furthermore, a lesson that stood out for me in this book is that businesses and programmers (or techies) must work together for the successful and effective utilisation of technology. Overall, this book contains tips for achieving successful software projects.
This is a technology-related book and understanding or flowing with it may be the concern of non-techie readers. However, the author employed many strategies to ensure that readers understand and appreciate this book to a large extent. My favourite topic under the “Conceptual Guide” is “Conceptual Mistakes.” This is because Crosby used real-life events to explain them. This made for an easy understanding and appreciation of the topic. Under that heading, the author wrote about mistakes that can occur at the initial stage of a project, which can have consequences. An event that happened in London Heathrow Airport was used to illustrate the point. Furthermore, the use of quotes and the author’s work experiences created a vivid picture in my mind, aiding in my understanding of the concepts. Ordinarily, repetitions could be tedious to read. However, I found the ones in this book to be relevant for emphasis and for a better understanding of crucial points. To allow readers to unravel all the education and insightful comments in this book, I would not want to reveal any more details. Furthermore, this book was excellently edited, and you will not be distracted by errors.
I, however, have a grouse about this book. It is quite an extensive and deep read, and as a result, there were so many headings and subheadings. However, asides from the headings (and parts) at the beginning of chapters, several subheadings were not numbered. Due to the nature of the book, I felt numbering them will aid readers in flowing with it. As a result, I felt a bit overwhelmed, and it was a tad difficult to flow constantly with the book.
Considering the importance of this book in the business/technology world today, I will rate this book four out of five stars. I deducted one star because of my complaint about it. Other than that, this book is worth every bit of your time. Therefore, I am recommending it to all business persons or even software developers working or aspiring to work with enterprises. This is because the lessons and information contained in it will be helpful in their professional relationship.
November 14, 2020
The business of making software is fairly unique. Software does not follow a traditional assembly-line process, but still borrows from many sources of theory to guide its production. Some projects follow a “waterfall” plan, and others follow an “agile” methodology; a wide array of differently named tests populates discussions. Crosby seeks to unify disparate voices such as these in one place and so to inform us of the business-side of software development.
The author is at his best when he simplifies these theories into root metaphors – like a “Jenga game,” planning an amusement park, or speaking of software “construction.” These metaphors quickly communicate a concept without getting lost in the details. Of course, analogies are always limited, but together, this host of metaphors paint an overall picture that facilitates learning and communication.
Crosby hits on most of the major operative points. He divides his work into three sections: on concepts, on practical matters, and on technical matters. The largest section is on practical matters and the smallest is on technical matters. The conceptual part is the most compelling. He never blitzes the reader with hard-to-understand technical jargon. This is evidently an effective piece of communication and a balanced overview grounded in deep experience with the software business.
The weakness of this work lies in its introductory manner. It does not delve into detail although it does provide references for future reading. It’s a guide. It does not seek to communicate new concepts or data to the field but only to convey existing information to business people. However, Crosby apparently seeks an audience for whom the material is new.
As an introduction, it is suitable (as the title implies) for business people seeking to learn about software. It could also prove helpful to software developers who seek to enhance their knowledge of the business and their ability to communicate with non-developers. For anyone involved in the development of software, receiving someone else’s perspective on one’s work is always helpful. Crosby does that and more in this book.
The author is at his best when he simplifies these theories into root metaphors – like a “Jenga game,” planning an amusement park, or speaking of software “construction.” These metaphors quickly communicate a concept without getting lost in the details. Of course, analogies are always limited, but together, this host of metaphors paint an overall picture that facilitates learning and communication.
Crosby hits on most of the major operative points. He divides his work into three sections: on concepts, on practical matters, and on technical matters. The largest section is on practical matters and the smallest is on technical matters. The conceptual part is the most compelling. He never blitzes the reader with hard-to-understand technical jargon. This is evidently an effective piece of communication and a balanced overview grounded in deep experience with the software business.
The weakness of this work lies in its introductory manner. It does not delve into detail although it does provide references for future reading. It’s a guide. It does not seek to communicate new concepts or data to the field but only to convey existing information to business people. However, Crosby apparently seeks an audience for whom the material is new.
As an introduction, it is suitable (as the title implies) for business people seeking to learn about software. It could also prove helpful to software developers who seek to enhance their knowledge of the business and their ability to communicate with non-developers. For anyone involved in the development of software, receiving someone else’s perspective on one’s work is always helpful. Crosby does that and more in this book.
October 11, 2020
First, I was given a copy of this book in exchange for a review.
With that being said - I'm quite possibly technologically in the equivalent of kindergarten. I can tell when something isn't working, but I have no idea why it isn't. I'm not really sure what mindset I went into reading this book with, but I certainly understand more about software development than I did before. Thanks to creative metaphors, simple speech, and amusing (and enlightened) quotes and pictures sprinkled throughout the book, I might possibly have graduated to first grade... possibly. But then, I might have just more about how to deal wisely with the software development teams and IT departments that come hand-in-hand with software development. Wisdom and people skills are sprinkled through the book just as liberally as quotes and metaphors, and as a hard-drive/logic/ration-brained introvert with few people skills, this was infinitely more valuable to me than the software knowledge.
I think my only complaint is that the ebook format changed after the start of part 2, from a new page for the start of each chapter, to the new chapter starting on the same page as the last one ended. This made finding the end of a chapter difficult, and it was frustrating, because I was reading chapter by chapter. I docked one star for the frustration. I'm autistic, and things like this can be off-putting for people like me. This might be something for the author to consider revising in a second version.
That being said, I would still recommend this book to anyone and everyone. I still don't know much of anything technologically-speaking, but I did learn a great deal about how to function in a business team setting, and that's a priceless skill to have these days. For that, I would say any business people in teams should read this.
With that being said - I'm quite possibly technologically in the equivalent of kindergarten. I can tell when something isn't working, but I have no idea why it isn't. I'm not really sure what mindset I went into reading this book with, but I certainly understand more about software development than I did before. Thanks to creative metaphors, simple speech, and amusing (and enlightened) quotes and pictures sprinkled throughout the book, I might possibly have graduated to first grade... possibly. But then, I might have just more about how to deal wisely with the software development teams and IT departments that come hand-in-hand with software development. Wisdom and people skills are sprinkled through the book just as liberally as quotes and metaphors, and as a hard-drive/logic/ration-brained introvert with few people skills, this was infinitely more valuable to me than the software knowledge.
I think my only complaint is that the ebook format changed after the start of part 2, from a new page for the start of each chapter, to the new chapter starting on the same page as the last one ended. This made finding the end of a chapter difficult, and it was frustrating, because I was reading chapter by chapter. I docked one star for the frustration. I'm autistic, and things like this can be off-putting for people like me. This might be something for the author to consider revising in a second version.
That being said, I would still recommend this book to anyone and everyone. I still don't know much of anything technologically-speaking, but I did learn a great deal about how to function in a business team setting, and that's a priceless skill to have these days. For that, I would say any business people in teams should read this.
February 20, 2022
You have just been named to a team tasked with creating a new software package, from scratch. Where do you even start?
Planning is essential before any code is written. Who is the intended recipient? Is it for internal use only, or will it be sold to the public? Constant communication between the corporate side and the IT side is also essential. Imposing an arbitrary deadline on the IT Department to have the software finished will not help.
The author uses the metaphor of building a house to make the whole process easier to understand for non-IT types. While in the planning stage, changes are acceptable (they are practically expected). When construction is half done, changes will cost a lot of time and money. It's tempting to want the software equivalent of a mansion, but it's a bad idea. Instead of having software that does everything but walk and talk by itself, and is full of bugs, what's wrong with having a much more basic piece of software that does only a few things, and has a lot fewer bugs?
Speaking of bugs, quality control is a requirement. Each finished chunk of software must be tested to make sure that it works with every other chunk of software. For example, this is a piece of HR software. Give it to your HR department for a test drive. Have IT people sit and watch how the software is used. Make note of, and fix, anything that doesn't work, or could be done better.
Corporate IT departments have constantly been accused of having their own language, incomprehensible to the rest of us. This book goes a long way toward bringing Corporate and IT closer together. It is very much worth reading for anyone in business, regardless of which side you are on.
Planning is essential before any code is written. Who is the intended recipient? Is it for internal use only, or will it be sold to the public? Constant communication between the corporate side and the IT side is also essential. Imposing an arbitrary deadline on the IT Department to have the software finished will not help.
The author uses the metaphor of building a house to make the whole process easier to understand for non-IT types. While in the planning stage, changes are acceptable (they are practically expected). When construction is half done, changes will cost a lot of time and money. It's tempting to want the software equivalent of a mansion, but it's a bad idea. Instead of having software that does everything but walk and talk by itself, and is full of bugs, what's wrong with having a much more basic piece of software that does only a few things, and has a lot fewer bugs?
Speaking of bugs, quality control is a requirement. Each finished chunk of software must be tested to make sure that it works with every other chunk of software. For example, this is a piece of HR software. Give it to your HR department for a test drive. Have IT people sit and watch how the software is used. Make note of, and fix, anything that doesn't work, or could be done better.
Corporate IT departments have constantly been accused of having their own language, incomprehensible to the rest of us. This book goes a long way toward bringing Corporate and IT closer together. It is very much worth reading for anyone in business, regardless of which side you are on.
January 24, 2022
Jonathan Crosby wrote a great book that advises business people on how to plan, put together, and promote software projects.
Crosby takes his Readers step by step through the various procedures making each step important. For example, he expands on conceptual planning and maintenance work before release. These preplanning steps save the User from excess time and money to fix costly mistakes after the fact.
Crosby uses metaphor and examples to illustrate many of his points. He tells the story of innovators like Henry Beck who created the definitive design of the London Underground to show that anyone can come up with important ideas, not just the select few with the so-called "right training and experience."
Crosby also uses personal experience to demonstrate many of his points. To show the importance of providing developers with an adequate quiet space for work. Crosby ended up responding to help desk calls while writing software tools. It's not a surprise that Crosby described his manager as "a great guy but not much of a developer. As a manager, (Crosby's boss) was used to switching tasks and was unaware of the programmer's need to concentrate for long periods without interruptions."
Guide to Software Projects For Business People is perfect for the Reader who is struggling with the complexities of software production. Crosby does a good job at taking Readers down that long path with small steps and examples. He makes that path understandable and ultimately successful.
January 11, 2022
There is something, this book cared to do, and I believe it did it but not perfectly like it was expected; to demystify the tech language and make it understandable to a layman.
Jonathan P. Crosby’s, "Guide to Software Projects for Business People: digital transformation," did something which I found unique but tedious, as it tried to teach the readers through careful examination and comparison of practical real-life issues. But the author didn't know how this book would have still become a hard read for anyone who is not well versed with languages. As you need to have a careful understanding of the language and what it entails, before unearthing the book.
I read this book through my Amazon Kindle app as a second book of the year and before the review, it's worth every ounce. I am an avid reader, who is versed with metaphors. But I barely have an understanding of technology, except basic computer literacy and being a biological science major, but the author did a beautiful work by mirroring it down to us who are novices.
It's not far fetched that the author had embarked on this journey, as he emphasized even in the corporate world, tech people need to simplify their words and stay tactical in their dealings. The book encompassed many things more than a software guide but navigates other workforce and the behavioural tactics when dealing with people.
Jonathan P. Crosby’s, "Guide to Software Projects for Business People: digital transformation," did something which I found unique but tedious, as it tried to teach the readers through careful examination and comparison of practical real-life issues. But the author didn't know how this book would have still become a hard read for anyone who is not well versed with languages. As you need to have a careful understanding of the language and what it entails, before unearthing the book.
I read this book through my Amazon Kindle app as a second book of the year and before the review, it's worth every ounce. I am an avid reader, who is versed with metaphors. But I barely have an understanding of technology, except basic computer literacy and being a biological science major, but the author did a beautiful work by mirroring it down to us who are novices.
It's not far fetched that the author had embarked on this journey, as he emphasized even in the corporate world, tech people need to simplify their words and stay tactical in their dealings. The book encompassed many things more than a software guide but navigates other workforce and the behavioural tactics when dealing with people.
June 16, 2022
The Guide to Software Projects for Business People by Jonathan P. Crosby is a practical guide for non-technological people to have a basic understanding of the process involved in creating/setting up new software for a business or organization. The author does a phenomenal job of explaining technical terms and concepts that are used by programmers and software analysts in ways that the average person who has no such training or background can understand. The author accomplishes this by comparing the process of building or maintaining software to that of a house or building while explaining important areas where the two processes will differ. The book is very thorough from the information gathering phase of the core processes that must be served by the software to the creation or implementation of existing software and finally the testing and user acceptance of said software. All the while emphasizing communication between the various stakeholders within the project. If that weren't enough, the author includes a nice reference list for further reading and a wonderful glossary at the end. Highly recommend if you are a person that works directly in or adjacent to a company or organization that utilizes software or technology in anyway.
Displaying 1 - 30 of 37 reviews