000 06092nam a22004573i 4500
001 EBC4543921
003 MiAaPQ
005 20240729130541.0
006 m o d |
007 cr cnu||||||||
008 240724s2016 xx o ||||0 eng d
020 _a9781457199486
_q(electronic bk.)
020 _z9780994346919
035 _a(MiAaPQ)EBC4543921
035 _a(Au-PeEL)EBL4543921
035 _a(CaPaEBR)ebr11484334
035 _a(OCoLC)937390330
040 _aMiAaPQ
_beng
_erda
_epn
_cMiAaPQ
_dMiAaPQ
050 4 _aQA76.76.D47 .G744 2016
082 0 _a005.1
100 1 _aGreen, M. David.
245 1 0 _aScrum :
_bMethods for Agile, Powerful Development.
250 _a1st ed.
264 1 _aVictoria :
_bSitePoint,
_c2016.
264 4 _c©2016.
300 _a1 online resource (187 pages)
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
505 0 _aCover -- Scrum: Novice to Ninja -- Table of Contents -- Preface -- Who Should Read This Book -- Conventions Used -- Tips, Notes, and Warnings -- Supplementary Materials -- Want to take your learning further? -- Introducing Scrum -- What Is Scrum? -- A Brief History of Scrum -- Comparing Scrum and Waterfall -- Reasons to Choose Scrum for Web and Mobile -- Time Sensitivity -- Modular Development -- Flexible Scheduling -- Reflection and Improvement -- Summary -- Meet the Team -- A Senior Engineer -- My Role -- Motivations -- Perfect Day -- Frustrations -- Concerns About Scrum -- A Junior Engineer -- My Role -- Motivations -- Perfect Day -- Frustrations -- Concerns About Scrum -- An Engineering Manager -- My Role -- Motivations -- Perfect Day -- Frustrations -- Concerns About Scrum -- A QA Engineer -- My Role -- Motivations -- Perfect Day -- Frustrations -- Concerns About Scrum -- A Product Manager -- My Role -- Motivations -- Perfect Day -- Frustrations -- Concerns About Scrum -- A Designer -- My Role -- Motivations -- Perfect Day -- Frustrations -- Concerns About Scrum -- An Executive -- Role -- Motivations -- Frustrations -- My Perfect Day -- Concerns About Scrum -- Summary -- Scrum Roles -- Establishing Who Does What -- No Hierarchy -- Scrum Roles and Organizational Roles -- Scrum Master -- Responsibilities -- A Day in the Life -- Product Owners -- Responsibilities -- A Day in the Life -- Team Members -- Cross-Training -- Responsibilities -- A Day in the Life -- Team Resources -- Designers -- QA Engineers -- Operations -- Managers -- The Rest of the World -- Users -- Customers -- Executives and Other Employees -- Summary -- Scrum Rituals -- What Are Rituals? -- Not Another Meeting! -- Time Boxing -- The Length of the Sprint -- Sprint Planning -- Objective -- Time Box -- Preparation -- Introducing New Stories -- Story Estimation -- Bugs -- Tasks.
505 8 _aSpikes -- Committing to a Sprint Backlog -- Daily Standup -- Objective -- Time Box -- Preparation -- Three Questions -- Other Status Updates -- Sprint Demo -- Objective -- Time Box -- Preparation -- Demonstrating a Story -- Tallying up the Points -- Releasing the Stories -- Sprint Retrospective -- Objective -- Time Box -- Preparation -- What Went Well? -- What Didn't Go Well? -- What Should We Do about It? -- Conclusion -- Scrum Artifacts -- Artifacts Overview -- Stories -- Product Backlog -- Sprint Backlog -- Scrum Board -- Definition of Done -- Velocity Chart -- Burndown Chart -- Product Increment -- Conclusion -- The Scrum Contract -- The Beginner's Mind -- Respecting Scrum Roles -- Providing Transparency -- Establishing Work Boundaries -- Honoring Reflective Iteration -- Adhering to Shared Definitions -- Summary -- The Lifecycle of a Story -- What's WithKittens? -- Why Just Kittens? -- Client Desires -- Product Backlog -- Formulating a Feature -- Lining up Design Resources -- Writing Stories -- A Full Slice of Functionality -- Story Format -- Presenting and Estimation -- Defining Scope -- Debating Effort -- Agreeing to a Sprint Backlog -- Summary -- Working Through Scrum -- Working Through a Story -- Taking Ownership -- Defining Tasks -- Tracking Progress -- The First Standup -- The Second Standup -- The Rest of the Sprint -- Demonstrating the Story -- Checking Acceptance Criteria -- Sprint Retrospective -- Summary -- Making Scrum Work for Your Web or Mobile Team -- Taking Steps Toward Scrum -- Buy-in -- Training -- Staffing -- Tracking Effectiveness -- Troubleshooting -- Undefined Time Boxes -- Optimizing for Sprints -- Long, Lazy Standups -- Work Interruptions -- Loose Demos -- Problem Solving During Retrospectives -- Summary -- Adapting to Scrum -- A Senior Engineer -- Initial Concerns -- What I've Learned -- What Still Frustrates Me.
505 8 _aWhat I Do About It -- A Junior Engineer -- Initial Concerns -- What I've Learned -- What Still Frustrates Me -- What I Do About It -- An Engineering Manager -- Initial Concerns -- What I've Learned -- What Still Frustrates Me -- What I Do About It -- A QA Engineer -- Initial Concerns -- What I've Learned -- What Still Frustrates Me -- What I Do About It -- A Product Manager -- Initial Concerns -- What I've Learned -- What Still Frustrates Me -- What I Do About It -- A Designer -- Initial Concerns -- What I've Learned -- What Still Frustrates Me -- What I Do About It -- An Executive -- Initial Concerns -- What I've Learned -- What Still Frustrates Me -- What I Do About It -- Conclusion.
588 _aDescription based on publisher supplied metadata and other sources.
590 _aElectronic reproduction. Ann Arbor, Michigan : ProQuest Ebook Central, 2024. Available via World Wide Web. Access may be limited to ProQuest Ebook Central affiliated libraries.
650 0 _aScrum (Computer software development).
650 0 _aWeb applications-Development.
655 4 _aElectronic books.
776 0 8 _iPrint version:
_aGreen, M. David
_tScrum: Novice to Ninja
_dVictoria : SitePoint,c2016
_z9780994346919
797 2 _aProQuest (Firm)
856 4 0 _uhttps://ebookcentral.proquest.com/lib/orpp/detail.action?docID=4543921
_zClick to View
999 _c111723
_d111723