東華大學圖書館 |

Language: English

Help

回圖書館首頁

手機版館藏查詢

Back

Switch To: Labeled | MARC Mode | ISBD

The business manager's guide to soft...

Crosby, Jonathan Peter.

Linked to FindBook

Google Book

Amazon

博客來

The business manager's guide to software projects = a framework for decision-making, team collaboration, and effectiveness /

Record Type:	Electronic resources : Monograph/item
Title/Author:	The business manager's guide to software projects/ by Jonathan Peter Crosby.
Reminder of title:	a framework for decision-making, team collaboration, and effectiveness /
Author:	Crosby, Jonathan Peter.
Published:	Berkeley, CA :Apress : : 2023.,
Description:	xxv, 306 p. :ill., digital ;24 cm.
[NT 15003449]:	Part I: Conceptual Guide -- Chapter 1: Architecture and Construction -- Chapter 2: Planning and Scope -- Chapter 3: Teething Troubles -- Chapter 4: Greenfield Construction -- Chapter 5: Laying the Right Foundation -- Chapter 6: Renovating and Extending -- Chapter 7: Technical Debt -- Chapter 8: Maintenance -- Chapter 9: Differences Between Physical Construction and Software Development -- Chapter 10: More Metaphors -- Part II: Practical Guide -- Chapter 11: The Practical Side -- Chapter 12: Plan and Prepare -- Chapter 13: Define -- Chapter 14: Develop -- Chapter 15: Test -- Chapter 16: Training, Going Live, and Maintenance -- Part III: Technical Guide -- Chapter 17: The Technical Side -- Chapter 18: Coding and Design -- Chapter 19: Metaphors for Technical Terms -- Chapter 20: Tricky Areas in Technical Development -- Chapter 21: To Sum Up -- Appendix A: Collaboration -- Appendix B: Glossary -- Appendix C: References and Further Reading.
Contained By:	Springer Nature eBook
Subject:	Software engineering. -
Online resource:	https://doi.org/10.1007/978-1-4842-9231-0
ISBN:	9781484292310

The business manager's guide to software projects = a framework for decision-making, team collaboration, and effectiveness /
Crosby, Jonathan Peter.

The business manager's guide to software projectsa framework for decision-making, team collaboration, and effectiveness /[electronic resource] :by Jonathan Peter Crosby. - Berkeley, CA :Apress :2023. - xxv, 306 p. :ill., digital ;24 cm.

Part I: Conceptual Guide -- Chapter 1: Architecture and Construction -- Chapter 2: Planning and Scope -- Chapter 3: Teething Troubles -- Chapter 4: Greenfield Construction -- Chapter 5: Laying the Right Foundation -- Chapter 6: Renovating and Extending -- Chapter 7: Technical Debt -- Chapter 8: Maintenance -- Chapter 9: Differences Between Physical Construction and Software Development -- Chapter 10: More Metaphors -- Part II: Practical Guide -- Chapter 11: The Practical Side -- Chapter 12: Plan and Prepare -- Chapter 13: Define -- Chapter 14: Develop -- Chapter 15: Test -- Chapter 16: Training, Going Live, and Maintenance -- Part III: Technical Guide -- Chapter 17: The Technical Side -- Chapter 18: Coding and Design -- Chapter 19: Metaphors for Technical Terms -- Chapter 20: Tricky Areas in Technical Development -- Chapter 21: To Sum Up -- Appendix A: Collaboration -- Appendix B: Glossary -- Appendix C: References and Further Reading.

Every day, successful software projects scale and sustain businesses of all sizes and across all industries. Unfortunately, the reality is that many software projects still fail. The reasons behind these failures are seldom due to the underlying technology. Misunderstandings and communication barriers lead to wrong decisions, missed opportunities, communication breakdowns, or worse-huge economic loss. In this digitally connected world, business professionals can't afford to be hands-off on technical projects, but they also can't be expected to have technical certifications. They have first-hand knowledge of the business processes, are subject matter experts in software requirements, and they finance the projects. Even C-level management or board members need to rapidly gain just enough understanding of technology to make mission-critical decisions for businesses to survive and flourish. In most software projects the number of non-technical stakeholders far exceeds the number of techies. This book distills the world of software projects into simple terms and relatable metaphors for even the most technically adverse reader. Real-life examples, entertaining analogies, and hand-drawn illustrations will stick with readers throughout their own software projects, bolstering their success. Business requirements, use cases, process flows-the list goes on. It's all broken down in this game-changing book aimed at delivering for business and tech teams what DevOps has done for developers and operations. What You Will Learn Know the importance of good business requirements and how to write them Identify the most important business roles, key decisions, and critical activities involved in software projects Strengthen collaboration between non-technical and technical teams Grasp common software project terminology, required for non-techies Understand the software development life cycle Gain insight on the common software project methodologies and how they differ Understand what software developers do at a high level.

ISBN: 9781484292310

Standard No.: 10.1007/978-1-4842-9231-0doiSubjects--Topical Terms:

559826
Software engineering.

LC Class. No.: QA76.758

Dewey Class. No.: 005.1

The business manager's guide to software projects = a framework for decision-making, team collaboration, and effectiveness /
LDR:04093nmm a2200349 a 4500 001 2316801
003 DE-He213
005 20230323080636.0
006 m d
007 cr nn 008maaau
008 230902s2023 cau s 0 eng d
020 $a 9781484292310 $q (electronic bk.)
020 $a 9781484292303 $q (paper)
024 7 $a 10.1007/978-1-4842-9231-0 $2 doi
035 $a 978-1-4842-9231-0
040 $a GP $c GP
041 0 $a eng
050 4 $a QA76.758
072 7 $a KJQ $2 bicssc
072 7 $a UF $2 bicssc
072 7 $a BUS083000 $2 bisacsh
072 7 $a KJQ $2 thema
072 7 $a UF $2 thema
082 0 4 $a 005.1 $2 23
090 $a QA76.758 $b .C949 2023
100 1 $a Crosby, Jonathan Peter. $3 3630340
245 1 4 $a The business manager's guide to software projects $h [electronic resource] : $b a framework for decision-making, team collaboration, and effectiveness / $c by Jonathan Peter Crosby.
260 $a Berkeley, CA : $b Apress : $b Imprint: Apress, $c 2023.
300 $a xxv, 306 p. : $b ill., digital ; $c 24 cm.
505 0 $a Part I: Conceptual Guide -- Chapter 1: Architecture and Construction -- Chapter 2: Planning and Scope -- Chapter 3: Teething Troubles -- Chapter 4: Greenfield Construction -- Chapter 5: Laying the Right Foundation -- Chapter 6: Renovating and Extending -- Chapter 7: Technical Debt -- Chapter 8: Maintenance -- Chapter 9: Differences Between Physical Construction and Software Development -- Chapter 10: More Metaphors -- Part II: Practical Guide -- Chapter 11: The Practical Side -- Chapter 12: Plan and Prepare -- Chapter 13: Define -- Chapter 14: Develop -- Chapter 15: Test -- Chapter 16: Training, Going Live, and Maintenance -- Part III: Technical Guide -- Chapter 17: The Technical Side -- Chapter 18: Coding and Design -- Chapter 19: Metaphors for Technical Terms -- Chapter 20: Tricky Areas in Technical Development -- Chapter 21: To Sum Up -- Appendix A: Collaboration -- Appendix B: Glossary -- Appendix C: References and Further Reading.
520 $a Every day, successful software projects scale and sustain businesses of all sizes and across all industries. Unfortunately, the reality is that many software projects still fail. The reasons behind these failures are seldom due to the underlying technology. Misunderstandings and communication barriers lead to wrong decisions, missed opportunities, communication breakdowns, or worse-huge economic loss. In this digitally connected world, business professionals can't afford to be hands-off on technical projects, but they also can't be expected to have technical certifications. They have first-hand knowledge of the business processes, are subject matter experts in software requirements, and they finance the projects. Even C-level management or board members need to rapidly gain just enough understanding of technology to make mission-critical decisions for businesses to survive and flourish. In most software projects the number of non-technical stakeholders far exceeds the number of techies. This book distills the world of software projects into simple terms and relatable metaphors for even the most technically adverse reader. Real-life examples, entertaining analogies, and hand-drawn illustrations will stick with readers throughout their own software projects, bolstering their success. Business requirements, use cases, process flows-the list goes on. It's all broken down in this game-changing book aimed at delivering for business and tech teams what DevOps has done for developers and operations. What You Will Learn Know the importance of good business requirements and how to write them Identify the most important business roles, key decisions, and critical activities involved in software projects Strengthen collaboration between non-technical and technical teams Grasp common software project terminology, required for non-techies Understand the software development life cycle Gain insight on the common software project methodologies and how they differ Understand what software developers do at a high level.
650 0 $a Software engineering. $3 559826
650 0 $a Project management. $3 578186
650 1 4 $a IT in Business. $3 2114922
650 2 4 $a Software Management. $3 2139173
710 2 $a SpringerLink (Online service) $3 836513
773 0 $t Springer Nature eBook
856 4 0 $u https://doi.org/10.1007/978-1-4842-9231-0
950 $a Business and Management (SpringerNature-41169)