000 04380nam a22003615i 4500
001 238665
003 ES-VaUEC
005 20240103143950.0
007 cr nn 008mamaa
006 a||||fo|||| 00| 0
008 230323s2023 xxu| s |||| 0|eng d
020 _a9781484292310
024 7 _a10.1007/978-1-4842-9231-0
_2doi
040 _aES-VaUEC
_bspa
_cES-VaUEC
050 0 4 _aHF54.5-54.56
_b2024
100 1 _aCrosby, Jonathan Peter.
_eautor
_4aut
_4http://id.loc.gov/vocabulary/relators/aut
245 0 4 _aThe Business Manager's Guide to Software Projects:
_bA Framework for Decision-Making, Team Collaboration, and Effectiveness
_cby Jonathan Peter Crosby
250 _a1st ed 2023
264 1 _aBerkeley CA
_c2023
_bSpringer International Publishing
300 0 0 _a1 recurso en línea
336 _atexto
_btxt
_2rdacontent
337 _aelectrónico
_bc
_2rdamedia
338 _arecurso electrónico
_bcr
_2rdacarrier
505 0 _aPart 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 _aEvery 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.
856 4 0 _uhttps://go.openathens.net/redirector/universidadeuropea.es?url=https://doi.org/10.1007/978-1-4842-9231-0
_zAcceso a este recurso digital (usuarios Universidad Europea de Valencia)
912 _aZDB-2-BUM
912 _aZDB-2-SXBM
942 _2lcc
_cLE
988 _aSpringer_Business_2023
999 _c238665
_d238665