By Ken Schwaber
Observe the foundations of Scrum, the most renowned agile programming equipment, to software program venture management—and concentration your staff on offering genuine company price. writer Ken Schwaber, a pace-setter within the agile method circulation and a co-creator of Scrum, brings his enormous services to assisting you consultant the product and software program improvement strategy extra successfully and successfully. aid get rid of the anomaly into which such a lot of software program tasks are borne, the place imaginative and prescient and making plans records are primarily thrown over the wall to builders. This high-level reference describes easy methods to use Scrum to control advanced expertise initiatives intimately, combining specialist insights with examples and case stories in response to Scrum. Emphasizing perform over thought, this booklet explores each element of utilizing Scrum, concentrating on using tasks for max go back on funding.
Read or Download Agile Project Management with Scrum (Microsoft Professional) PDF
Similar project management books
First-class consultant for these eager to know about venture administration. Used this for a category and it used to be super worthy. effortless, transparent analyzing.
There is not any secret surrounding the explanations for IT venture failure however the key factor is that IT companies owners and purchasers make an identical errors many times, and back. This handbook bargains systematic assistance on how one can feel and keep away from the explanations of IT venture failure at each step; from venture belief to the disposal of the process after a protracted and worthwhile operational existence.
Even top businesses with refined IT infrastructures and groups of attorneys can locate themselves unprepared to accommodate the variety of matters which could come up in IT contracting. Written by means of pro legal professionals, A consultant to IT Contracting: Checklists, instruments, and strategies distills the main severe enterprise and criminal classes discovered in the course of the authors’ many years of expertise drafting and negotiating IT-related agreements.
Designed to supply software program engineers, scholars, and IT pros with an figuring out of the basics of undertaking administration within the technology/IT box, this publication serves as a pragmatic creation to the topic. up to date with details on how basics of venture administration integrates with and enhances venture administration Institute's venture administration physique of information, this assortment explains primary methodologies and strategies whereas additionally discussing new know-how, instruments, and digital paintings environments.
- Project-Management in Practice: A Guideline and Toolbox for Successful Projects
- Practice standard for earned value management
- Autopoietic Knowledge Systems in Project-Based Companies
- Implementing Program Management: Templates and Forms Aligned with the Standard for Program Management - Second Edition (2008)
- Tools for Project Management, Workshops and Consulting: A Must-Have Compendium of Essential Tools and Techniques
Additional resources for Agile Project Management with Scrum (Microsoft Professional)
Scrum excels on urgent projects that are critical to an organization. Scrum excels when requirements are unknown, unknowable, or changing. Scrum excels by helping teams excel. In this book, Ken Schwaber correctly points out that Scrum is hard. It’s not hard because of the things you do; it’s hard because of the things you don’t do. If you’re a project manager, you might find some of your conventional tools missing. There are no Gantt charts in Scrum, there’s no time reporting, and you don’t assign tasks to programmers.
More detailed information about Scrum can be found in Appendix C, and in Ken Schwaber and Mike Beedle’s, Agile Software Development with Scrum (Prentice Hall, 2002). Scrum Roles There are only three Scrum roles: the Product Owner, the Team, and the ScrumMaster. All management responsibilities in a project are divided among these three roles. The Product Owner is responsible for representing the interests of everyone with a stake in the project and its resulting system. The Product Owner achieves initial and ongoing funding for the project by creating the project’s initial overall requirements, return on investment (ROI) objectives, and release plans.
Scrum doesn’t focus on delivering just any increment of business value; it focuses on delivering the highest priority business value as defined by the customer (Product Owner). The Product Owner and the Team confer about what that definition is, and then the Team decides what it can do in 30 days to deliver high-priority business value. Thus the short feedback loop becomes a business feedback loop—Scrum tests early and often whether the system being developed will deliver value and exactly what that value will look like.