MARC 닫기
05444cam a2200553Ki 4500
000000536199
20210114162128
m d
cr cnu---unuuu
190713s2019 enk o 000 0 eng d
▼a 1107446881
▼a 1789610982
▼a 9781789610987
▼q (electronic bk.)
▼a 2181409
▼b (N$T)
▼a (OCoLC)1107589587
▼z (OCoLC)1107446881
▼a 7877A451-F81E-4064-999A-D1D207DDB19A
▼b OverDrive, Inc.
▼n http://www.overdrive.com
▼a EBLCP
▼b eng
▼e pn
▼c EBLCP
▼d TEFOD
▼d EBLCP
▼d TEFOD
▼d OCLCQ
▼d OCLCF
▼d YDX
▼d UKAHL
▼d OCLCQ
▼d N$T
▼d 248023
▼a QA76.76.D47
▼a 005.1/068
▼2 23
▼a Fung, Herman.
▼a The Successful Software Manager:
▼b the Definitive Guide to Growing from Developer to Manager.
▼a Birmingham:
▼b Packt Publishing, Limited,
▼c 2019.
▼a 1 online resource (433 pages).
▼a text
▼b txt
▼2 rdacontent
▼a computer
▼b c
▼2 rdamedia
▼a online resource
▼b cr
▼2 rdacarrier
▼a Cover; Copyright; About Packt; Contributors; Table of Contents; Preface; Chapter 1: Why Do You Want to Become a Manager?; Start with ""why?; The pros and cons of becoming a manager; Your attitude and tolerance for risk-taking; Where am I and how did I get here?; The cost of the journey; Are you ready to become a manager?; Breaking down your working week; What jobs are there?; Team leader / manager; Development / delivery manager; Project manager; Being an Agile practitioner; Scrum master; Does being a manager mean managing people?; Maslow's hierarchy of needs
▼a You don't have to be a psychologistThe ""Accidental Manager; The Johari Window; Hacking the impostor syndrome; The Rumsfeld Matrix; Summary; Chapter 2: What Are the Key Skills I Need?; Skill 1 -- Flexibility and adaptability; Skill 2 -- Communication, communication, communication; Inbound communication; Internal communication; Outbound communication; Skill 3 -- Team leadership; Aspects of team leadership; Don't do everything yourself; Clarity of team responsibilities; Document your team services; Skill 4 -- Stakeholder management; Stakeholder mapping; The layers of a stakeholder relationship
▼a Stakeholder management case study -- the UK NHSSkill 5 -- Negotiation; Building rapport; Skill 6 -- Using a chosen methodology; Agile; Incremental development, over big-bang releases; Dynamic daily huddles, over regular static updates; User stories, over exhaustive requirements; The Waterfall model; PRINCE2; If I'm not ready, then how do I get ready?; Get a mentor; Shadowing; How do I get the job?; Internal or external; Positioning yourself; Will I like it?; The interview and the offer; Summary; Chapter 3: What Is My Job Now?; The seven fundamental roles of any software project
▼a 1. Project ManagerPlanning; Controlling; 1. Scope risk; 2. Scheduling risk; 3. Resource risk; 4. Technology risk; Reporting; 2. Project Sponsor; 3. Business Subject Matter Expert; 4. Business Analyst; 5. Technical Architect; 6. Developer; 7. Testers; Your first day; Meet your manager; Induction training; Meet your team; The first team meeting; Your first week; Meet your stakeholders; Set your own schedule; Make a plan; Summary; Chapter 4: A Week in the Life of a Manager; The 70/20/10 blended learning model; Experiential learning; Exposure learning; Educational learning
▼a The impact of your methodology choiceAgile, PRINCE2, and ITIL; The ITIL framework; The five stages of the ITIL life cycle; ITIL versus DevOps; Event, incident, and problem management; Event management; Incident management; Problem management; The weekly project template; Monday; 09:00 A.M. to 09:15 A.M. -- team huddle; 10:00 A.M. to 11:00 A.M. -- power meeting; 11:00 A.M. to 12:00 A.M. -- backlog/task list review; 12:00 P.M. onward -- stakeholder time; Tuesday; 09:00 A.M. to 09:15 A.M. -- team huddle; 10:00 A.M. onward -- planning time; Burn charts; Wednesday; 09:00 A.M. to 09:15 A.M. -- team huddle
▼a 12:00 P.M. onward -- team meeting/backlog review/sprint planning
▼a The Successful Software Manager is a comprehensive and practical guide to managing software developers, software customers, and the process of deciding what software needs to be built. It explains in detail how to develop a management mindset, lead a high performing developer team, and meet all the expectations of a good manager.
▼a Print version record.
▼a Added to collection customer.56279.3
▼a Computer software
▼x Development
▼x Management.
▼a Computer programming
▼x Management.
▼a Computer programming
▼x Management.
▼2 fast
▼0 (OCoLC)fst00872399
▼a Computer software
▼x Development
▼x Management.
▼2 fast
▼0 (OCoLC)fst00872548
▼a Electronic books.
▼i Print version:
▼a Fung, Herman.
▼t Successful Software Manager : The Definitive Guide to Growing from Developer to Manager.
▼d Birmingham : Packt Publishing, Limited, ©2019,
▼z 9781789615531
▼3 EBSCOhost
▼u http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=2181409
▼a Askews and Holts Library Services
▼b ASKH
▼n BDZ0040221366
▼a ProQuest Ebook Central
▼b EBLB
▼n EBL5808104
▼a YBP Library Services
▼b YANK
▼n 300678112
▼a EBSCOhost
▼b EBSC
▼n 2181409
▼a 강리원
▼a eBook
▼a 92
▼b N$T
| 자료유형 : | eBook |
|---|---|
| ISBN : | 1789610982 |
| ISBN : | 9781789610987 |
| 개인저자 : | Fung, Herman. |
| 서명/저자사항 : | The Successful Software Manager: the Definitive Guide to Growing from Developer to Manager. |
| 발행사항 : | Birmingham: Packt Publishing, Limited, 2019. |
| 형태사항 : | 1 online resource (433 pages). |
| 내용주기 : | Cover; Copyright; About Packt; Contributors; Table of Contents; Preface; Chapter 1: Why Do You Want to Become a Manager?; Start with ""why?; The pros and cons of becoming a manager; Your attitude and tolerance for risk-taking; Where am I and how did I get here?; The cost of the journey; Are you ready to become a manager?; Breaking down your working week; What jobs are there?; Team leader / manager; Development / delivery manager; Project manager; Being an Agile practitioner; Scrum master; Does being a manager mean managing people?; Maslow's hierarchy of needs |
| 내용주기 : | You don't have to be a psychologistThe ""Accidental Manager; The Johari Window; Hacking the impostor syndrome; The Rumsfeld Matrix; Summary; Chapter 2: What Are the Key Skills I Need?; Skill 1 -- Flexibility and adaptability; Skill 2 -- Communication, communication, communication; Inbound communication; Internal communication; Outbound communication; Skill 3 -- Team leadership; Aspects of team leadership; Don't do everything yourself; Clarity of team responsibilities; Document your team services; Skill 4 -- Stakeholder management; Stakeholder mapping; The layers of a stakeholder relationship |
| 내용주기 : | Stakeholder management case study -- the UK NHSSkill 5 -- Negotiation; Building rapport; Skill 6 -- Using a chosen methodology; Agile; Incremental development, over big-bang releases; Dynamic daily huddles, over regular static updates; User stories, over exhaustive requirements; The Waterfall model; PRINCE2; If I'm not ready, then how do I get ready?; Get a mentor; Shadowing; How do I get the job?; Internal or external; Positioning yourself; Will I like it?; The interview and the offer; Summary; Chapter 3: What Is My Job Now?; The seven fundamental roles of any software project |
| 내용주기 : | 1. Project ManagerPlanning; Controlling; 1. Scope risk; 2. Scheduling risk; 3. Resource risk; 4. Technology risk; Reporting; 2. Project Sponsor; 3. Business Subject Matter Expert; 4. Business Analyst; 5. Technical Architect; 6. Developer; 7. Testers; Your first day; Meet your manager; Induction training; Meet your team; The first team meeting; Your first week; Meet your stakeholders; Set your own schedule; Make a plan; Summary; Chapter 4: A Week in the Life of a Manager; The 70/20/10 blended learning model; Experiential learning; Exposure learning; Educational learning |
| 내용주기 : | The impact of your methodology choiceAgile, PRINCE2, and ITIL; The ITIL framework; The five stages of the ITIL life cycle; ITIL versus DevOps; Event, incident, and problem management; Event management; Incident management; Problem management; The weekly project template; Monday; 09:00 A.M. to 09:15 A.M. -- team huddle; 10:00 A.M. to 11:00 A.M. -- power meeting; 11:00 A.M. to 12:00 A.M. -- backlog/task list review; 12:00 P.M. onward -- stakeholder time; Tuesday; 09:00 A.M. to 09:15 A.M. -- team huddle; 10:00 A.M. onward -- planning time; Burn charts; Wednesday; 09:00 A.M. to 09:15 A.M. -- team huddle |
| 내용주기 : | 12:00 P.M. onward -- team meeting/backlog review/sprint planning |
| 요약 : | The Successful Software Manager is a comprehensive and practical guide to managing software developers, software customers, and the process of deciding what software needs to be built. It explains in detail how to develop a management mindset, lead a high performing developer team, and meet all the expectations of a good manager. |
| 일반주제명 : | Computer software -- Development -- Management. -- |
| 일반주제명 : | Computer programming -- Management. -- |
| 일반주제명 : | Computer programming -- Management. -- |
| 일반주제명 : | Computer software -- Development -- Management. -- |
| 기타형태 저록 : | Print version: Fung, Herman. Successful Software Manager : The Definitive Guide to Growing from Developer to Manager. Birmingham : Packt Publishing, Limited, ©2019, 9781789615531 |
| 언어 | 영어 |
| URL : |
|---|
서평쓰기