LEADER 04235nam  22006971  450 
001 9910452697003321
005 20200520144314.0
010   $a1-84928-447-4
010   $a1-299-46853-5
010   $a1-84928-446-6
035   $a(CKB)2550000001019509
035   $a(EBL)1186297
035   $a(OCoLC)834071747
035   $a(SSID)ssj0000906068
035   $a(PQKBManifestationID)11475075
035   $a(PQKBTitleCode)TC0000906068
035   $a(PQKBWorkID)10927001
035   $a(PQKB)10716178
035   $a(MiAaPQ)EBC1186297
035   $a(WaSeSS)IndRDA00019527
035   $a(CaSebORM)9781849284479
035   $a(Au-PeEL)EBL1186297
035   $a(CaPaEBR)ebr10772220
035   $a(CaONFJC)MIL478103
035   $a(EXLCZ)992550000001019509
100   $a20130516d2013      uy             0
101 0 $aeng
135   $aur|n|---|||||
181   $ctxt
182   $cc
183   $acr
200 10$aAgile SAP $eIntroducing flexibility, transparency and speed to SAP implementations /$fSean Robson
205   $a1st edition
210  1$aEly, Cambridgeshire :$cIT Governance Publishing,$d2013.
215   $a1 online resource (208 p.)
300   $aDescription based upon print version of record.
311   $a1-84928-445-8 
320   $aIncludes bibliographical references.
327   $aForeword; Preface; About the Author; Acknowledgements; Contents; Introduction; Chapter 1: Introduction to Scrum and Kanban; Scrum; Kanban; Scrum or Kanban?; Chapter 2: Project Conception; Setting expectations; Working software over documentation; Capacity to accept change; Conditions that challenge Agile in ERP projects; Customer involvement; Landscape complexity; Regulated industries; Distributed teams; Fixed price contracts; Teams; Leadership; High level estimating; Closing; Chapter 3: Project Preparation; Infrastructure; Knowledge transfer; Work environment; Task tracking
327   $aChapter 4: Business BlueprintIntroduction to the approach; Overview; Iteration 0 - Initial demo, requirements and architecture; Infrastructure; Initial solution demo; Story Mapping (aka "process workshops"); Step 1 - Build the Business Process Map; Step 2 - Building the Story Map and identifying stories; Release planning; Overview; The product backlog; Strategy; Slicing; Dependencies; Defining "done"; Acceptance tests; Estimating; A final comment on Story Mapping; Nonfunctional requirements; Project documents; Lean blueprinting; Iteration 1 - First build; Chapter 5: Realization; Overview
327   $aTestingDefining tests; Defining the test team; When to test; RICEFW unit testing; Configuration unit testing; A final note on testing; Backlog grooming; Scrum; When to use Scrum; SAP sprints; Overview; Sprint planning; Tracking the work; Daily Scrums; Getting the work done; Sprint review and retrospective; Kanban; Building the board; Work in progress; The daily standup; The input queue; Pulling versus pushing work; What work types do we track?; Work item size; Using Kanban to improve; Leadtime and throughput; Bottlenecks; Blocks; Waste; Defect tracking; How to manage new work
327   $aVisible policiesProject reporting; Chapter 6: Final Preparation; Appendix A: Development Approach; Further Resources; Books; Websites; ITG Resources
330   $aThe use of Agile methods to implement SAP is a relatively new approach and one that has proven to be very successful. Agile techniques can greatly improve your SAP implementations, reduce risks, and help you bring your projects in on schedule and within budget.
606   $aAgile software development
606   $aInformation technology projects$xManagement
606   $aJava (Computer program language)
606   $aScrum (Computer software development)
608   $aElectronic books.
615  0$aAgile software development.
615  0$aInformation technology projects$xManagement.
615  0$aJava (Computer program language)
615  0$aScrum (Computer software development)
676   $a005.1
700   $aRobson$b Sean$0882050
801  0$bMiAaPQ
801  1$bMiAaPQ
801  2$bMiAaPQ
906   $aBOOK
912   $a9910452697003321
996   $aAgile SAP$91970294
997   $aUNINA