Agile Project Management with Scrum 在线电子书 图书标签: agile Scrum 项目管理 敏捷开发 软件工程 management 敏捷 软件开发
发表于2024-11-24
Agile Project Management with Scrum 在线电子书 pdf 下载 txt下载 epub 下载 mobi 下载 2024
Good case studies and very to the point. However, the methodology is not fully suitable for Enterprise Agile and Portfolio Management. You would also need strong individuals on the team.
评分经历过这样的项目模式,再回头看看指导手册,一一对应三个角色、报表、Daily & whole process,又多一层理解,感觉很有趣。
评分不错的SCRUM 介绍书籍.
评分不错的SCRUM 介绍书籍.
评分scrum的第一要素是人,只有有经验、有主观能动性的人才能使scrum真正运作起来。但吊诡的问题是,既然有了有经验,有主观能动性的人用什么方法论能有多大的区别呢?
Apply the principles of Scrum to software project management with guidance from one of the leaders in the agile process movement. Case studies and project examples demonstrate Scrum concepts in practice and emphasize driving projects for maximum ROI.
The rules and practices for Scrum—a simple process for managing complex projects—are few, straightforward, and easy to learn. But Scrum's simplicity itself—its lack of prescription—can be disarming, and new practitioners often find themselves reverting to old project management habits and tools and yielding lesser results. In this illuminating series of case studies, Scrum co-creator and evangelist Ken Schwaber identifies the real-world lessons—the successes and failures—culled from his years of experience coaching companies in agile project management. Through them, you'll understand how to use Scrum to solve complex problems and drive better results—delivering more valuable software faster.
Gain the foundation in Scrum theory—and practice—you need to:
Rein in even the most complex, unwieldy projects
Effectively manage unknown or changing product requirements
Simplify the chain of command with self-managing development teams
Receive clearer specifications—and feedback—from customers
Greatly reduce project planning time and required tools
Build—and release—products in 30-day cycles so clients get deliverables earlier
Avoid missteps by regularly inspecting, reporting on, and fine-tuning projects
Support multiple teams working on a large-scale project from many geographic locations
Maximize return on investment!
My new boss wasn’t being a jerk, but it seemed like it at the time. We were writing new software for use in the company’s high-volume call centers. Instead of the 12 months I told him we’d probably need, he had agreed to give me 4 months. We wouldn’t necessarily start using the new software in 4 months, but from that point on, all my boss could give me was 30 days’ notice of a go-live date. After the first 4 months, I would have to keep the software within 30 days of releasable. My boss understood that not all functionality would be there after 4 months. He just wanted as much as he could get, as fast as he could get it. I needed to find a process that would let us do this. I scoured everything I could find on software development processes, which led me to Scrum and to Ken Schwaber’s early writings on it.
In the years since my first Scrum project, I have used Scrum on commercial products, software for internal use, consulting projects, projects with ISO 9001 requirements, and others. Each of these projects was unique, but what they had in common was urgency and criticality. 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. Instead you’ll learn the few simple rules of Scrum and how to use its frequent inspect-and-adapt cycles to create more valuable software faster.
Ken was there at the beginning of Scrum. Ken, along with Jeff Sutherland, was the original creator of Scrum and has always been its most vocal proponent. In this book, we get to read about many of the Scrum projects Ken has participated in. Ken is a frequent and popular speaker at industry conferences, and if you’ve ever heard him speak, you know he doesn’t pull any punches. This book is the same way: Ken presents both the successes and the failures of past Scrum projects. His goal is to teach us how to make our projects successful, and so he presents examples we can emulate and counterexamples for us to avoid.
This book clearly reflects Ken’s experience mentoring Scrum Teams and teaching Certified ScrumMaster courses around the world. Through the many stories in this book, Ken shares with us dozens of the lessons he’s learned. This book is an excellent guide for anyone looking to improve how he or she delivers software, and I recommend it highly.
首先想到一个问题,那就是为什么要学管理? 很多刚毕业的管理系学生,都会被问或者自问上述的问题,而一般很少有人知道怎么作答。 当然标准答案这种存在就好像北京的温柔春天,理论上声情并茂实际上难以遇到,不过我们可以无限逼近这一极限。给出一个对绝大多数人来说有意义...
评分我是一个典型的从CMMI体系下作项目管理的,外面敏捷的呼声越来越大,让我也开始关注敏捷,不得不说一句,敏捷宣传的相当好。 这本书写清楚了Scrum这种方式是如何管理项目的,也说了为什么这样管理,虽然这部分我觉得部分地方写的有些牵强,但至少明白了初衷。 翻译的还行,有明...
评分Ken是一个实践者,但是Ken有个特点就是他会先告诉你Scrum解决不了那些问题。大家在找寻方法论的时候都希望它能帮你解决所有问题,但是世界上没有后这样的方法论,这些东西永远都是指导,是别人的成功,你要成功只能靠自己。 如果大家没有时间来看书的话,《Scrum指南》在14页的...
评分今年开始尝试做PM, 在我看来PM貌似就是个打杂的角色, 不管了, 先尝试一下, 因此找了一些书来看看, scrum也是我今年规划中需要了解的一个东东, 因此就选了这本书. 这本书据说是scrum的入门书, 也是scrum的鼻祖ken schwaber的大作. 以前也在网上对scrum有过只言片语的了解, 从这...
评分作者是一位实践者。他结合各种实际中的案例,将Scrum剖析了一番。 重点介绍了Scrum的流程,即四个会和sprint的流程。对人和工件的介绍较少。 后面的翻译不是很通顺,比较生硬。大家看看罢了。 后面的翻译不是很通顺,比较生硬。大家看看罢了。
Agile Project Management with Scrum 在线电子书 pdf 下载 txt下载 epub 下载 mobi 下载 2024