04235nam 22006971 450 991045269700332120200520144314.01-84928-447-41-299-46853-51-84928-446-6(CKB)2550000001019509(EBL)1186297(OCoLC)834071747(SSID)ssj0000906068(PQKBManifestationID)11475075(PQKBTitleCode)TC0000906068(PQKBWorkID)10927001(PQKB)10716178(MiAaPQ)EBC1186297(WaSeSS)IndRDA00019527(CaSebORM)9781849284479(Au-PeEL)EBL1186297(CaPaEBR)ebr10772220(CaONFJC)MIL478103(EXLCZ)99255000000101950920130516d2013 uy 0engur|n|---|||||txtccrAgile SAP Introducing flexibility, transparency and speed to SAP implementations /Sean Robson1st editionEly, Cambridgeshire :IT Governance Publishing,2013.1 online resource (208 p.)Description based upon print version of record.1-84928-445-8 Includes bibliographical references.Foreword; 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 trackingChapter 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; OverviewTestingDefining 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 workVisible policiesProject reporting; Chapter 6: Final Preparation; Appendix A: Development Approach; Further Resources; Books; Websites; ITG ResourcesThe 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.Agile software developmentInformation technology projectsManagementJava (Computer program language)Scrum (Computer software development)Electronic books.Agile software development.Information technology projectsManagement.Java (Computer program language)Scrum (Computer software development)005.1Robson Sean882050MiAaPQMiAaPQMiAaPQBOOK9910452697003321Agile SAP1970294UNINA