Excerpt for Agile Project Management by , available in its entirety at Smashwords



Agile Project Management


Beginner Guide for Scrum Development


James Jackson

Copyright © 2017 by Kashvi Publishing, All rights reserved

All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law. For permission, direct requests to the publisher, addressed “Attention: Permissions Coordinator,” at the address below.Distribution of this book without the prior permission of the author is illegal, and therefore punishable by law. 1st Edition

Disclaimer

Legal Notice: - The author and publisher of this book and the accompanying materials have used their best efforts in preparing the material. The author and publisher make no representation or warranties with respect to the accuracy, applicability, fitness or completeness of the contents of this book. The information contained in this book is strictly for educational purposes. Therefore, if you wish to apply ideas contained in this book, you are taking full responsibility for your actions.

The author and publisher disclaim any warranties (express or implied), merchantability, or fitness for any particular purpose. The author and publisher shall in no event be held liable to any party for any direct, indirect, punitive, special, incidental or other consequential damages arising directly or indirectly from any use of this material, which is provided “as is”, and without warranties.

As always, the advice of a competent legal, tax, accounting or other professional should be sought. The author and publisher do not warrant the performance, effectiveness or applicability of any sites listed or linked to in this book. All links are for information purposes only and are not warranted for content, accuracy or any other implied or explicit purpose.


Table of Contents

INTRODUCTION 8

I.HAVING A CORRECT MINDSET 10

1.1.Communication and Collaboration 10

1.2.Everyone should be self-organized 10

1.3.Divide-and-conquer 11

1.4.Think of the core values 11

1.5.Think of the flexibility 11

1.6.Satisfying the customer 12

II.AGILE METHODOLOGY 13

1.1.Agile principles 13

1.2.Agile manifesto 15

1.3.Sprint 21

III.SCRUM – Roles and Responsibilities 24

1.1.Product Owner 24

1.2.ScrumMaster 26

1.3.Scrum team: 27

IV.Scrum Development Process 29

1.1.Sprint 0 30

i.Business Analyst from development team collects customer requirements 31

ii.Scrum team analyzes the customer's requirements and create Product Requirements Document (PRD). 32

iii.Product Owner breaks down customer's requirements into items (epic, user story, use case), prioritize and put them into the product backlog. 32

1.2.Sprint 1 to sprint n 35

1.17.Maintain product backlog and release plan 53

1.18.Complete a release 54

1.19.Close project 55

1.20.Dealing with the difficulties 55

iv.The team could be distributed. 55

v.Team members are new to Agile 58

V.THINKING PRIOR TO AGILE ADOPTION 61

1.1.Agile project is quick and cheap 61

1.2.The company environment has to be ready 63

1.3.Multifunction people and co-location are the ideal 64

1.4.Communications and ways of working take more effort with Agile than Waterfall 67

1.5.Self-organized teams need help 68

1.6.It’s all about delivering small but delivering often 69

1.7.Planning and reviews have to be done, but can be fun 70

1.8.No documentation in Agile project 71

1.9.Measure and track 72

1.10.Agile is survivor for projects that the requirements are not clear 72