Ebook Agile Portfolio Management, by Jochen Krebs
Agile Portfolio Management, By Jochen Krebs. A task might obligate you to always enrich the understanding as well as experience. When you have no adequate time to boost it directly, you can get the encounter as well as expertise from checking out guide. As everybody recognizes, book Agile Portfolio Management, By Jochen Krebs is incredibly popular as the home window to open up the globe. It suggests that checking out book Agile Portfolio Management, By Jochen Krebs will certainly provide you a brand-new method to locate everything that you require. As the book that we will offer right here, Agile Portfolio Management, By Jochen Krebs
Agile Portfolio Management, by Jochen Krebs
Ebook Agile Portfolio Management, by Jochen Krebs
Agile Portfolio Management, By Jochen Krebs. In undergoing this life, many individuals consistently attempt to do as well as obtain the best. New knowledge, encounter, session, as well as everything that can improve the life will certainly be done. However, lots of people occasionally feel confused to obtain those things. Feeling the limited of experience and sources to be better is among the lacks to have. Nonetheless, there is a really easy thing that can be done. This is just what your educator constantly manoeuvres you to do this one. Yeah, reading is the answer. Reviewing a publication as this Agile Portfolio Management, By Jochen Krebs and also other recommendations could enrich your life high quality. Just how can it be?
Why need to be publication Agile Portfolio Management, By Jochen Krebs Book is among the simple resources to try to find. By obtaining the author as well as style to get, you could locate a lot of titles that offer their data to acquire. As this Agile Portfolio Management, By Jochen Krebs, the impressive publication Agile Portfolio Management, By Jochen Krebs will certainly provide you what you should cover the work target date. And why should be in this site? We will ask initially, have you more times to opt for shopping the books and also look for the referred book Agile Portfolio Management, By Jochen Krebs in book establishment? Many individuals could not have sufficient time to locate it.
For this reason, this website offers for you to cover your issue. We reveal you some referred books Agile Portfolio Management, By Jochen Krebs in all types as well as motifs. From typical author to the famous one, they are all covered to offer in this internet site. This Agile Portfolio Management, By Jochen Krebs is you're searched for book; you just have to visit the link web page to receive this internet site and after that opt for downloading and install. It will not take sometimes to get one publication Agile Portfolio Management, By Jochen Krebs It will certainly rely on your net connection. Just acquisition as well as download the soft documents of this book Agile Portfolio Management, By Jochen Krebs
It is so simple, isn't it? Why do not you try it? In this website, you can additionally discover various other titles of the Agile Portfolio Management, By Jochen Krebs book collections that may be able to aid you locating the most effective option of your task. Reading this publication Agile Portfolio Management, By Jochen Krebs in soft documents will likewise ease you to get the resource quickly. You could not bring for those books to someplace you go. Just with the gizmo that always be with your everywhere, you could read this publication Agile Portfolio Management, By Jochen Krebs So, it will certainly be so swiftly to complete reading this Agile Portfolio Management, By Jochen Krebs
Agile development processes foster better collaboration, innovation, and results. So why limit their use to software projects—when you can transform your entire business?
Written by agile-mentoring expert Jochen Krebs, this book illuminates the opportunities—and rewards—of applying agile processes to your overall IT portfolio.
Whether project manager, business analyst, or executive—you’ll understand the business drivers behind agile portfolio management. And learn best practices for optimizing results.
Use agile processes to align IT and business strategy
- Adapt and extend core agile processes
- Orchestrate the collaboration between IT and business vision
- Eliminate wish-list driven requirements, and manage expectations instead
- Optimize the balance of projects, resources, and assets in your portfolio
- Use metrics to communicate project status, quality, even team morale
- Create a portfolio strategy consistent with the goals of the organization
- Achieve organizational and process transparency
- Manage your business with agility—and help maximize the returns!
- Sales Rank: #1305138 in Books
- Brand: Brand: Microsoft Press
- Published on: 2008-06-30
- Released on: 2008-07-16
- Original language: English
- Number of items: 1
- Dimensions: 9.00" h x .60" w x 7.40" l, 1.05 pounds
- Binding: Paperback
- 240 pages
- Used Book in Good Condition
About the Author
Jochen Krebs is an accomplished agile mentor and instructor, and the founder of an agile coaching and training services company. He spearheads the local chapter of Agile Project Leadership Network (APLN) in New York, speaks at industry conferences and corporate events, and has written numerous articles about agile practices. He is also the coauthor of the IBM RATIONAL UNIFIED PROCESS REFERENCE AND CERTIFICATION GUIDE.
Most helpful customer reviews
27 of 27 people found the following review helpful.
Full of misunderstandings with some insights
By Bas Vodde
I was looking forward to this book! An important hole in the current agile literature and a book only on this subject. Finally... but ... I'm extremely disappointed.
Jochen Krebs' Agile Portfolio Management consists of 3 parts. Part one is called "Agile for Managers", part two is the things about portfolio management and part three is *other* called organization and environment.
The first part consists of three chapters. The first chapter consists a general motivation for agile development and responding to change. The second chapter is a short introduction to Agile development and the last chapter an introduction to project management. This takes up 1/4th of the book. The explanations are poorly written and full with misunderstandings. To give a concrete example, on page 27 Jochen is suggesting that in Scrum you can not have any other meetings except for the daily Scrum. A recommendation which I've never heard before and I'm pretty sure he didn't actually mean that!
Part two consists of about 125 pages and is the main subject of the book, though it starts with three somewhat introduction chapters called Foundation, Metrics and Return of Investment. These chapters don't show too much experience from the author. The suggestion that TDD and Continuous Integration finds defects early so that one of the main quality metrics is open defect count is absurd and goes directly against advise of great agile literature like "Art of Agile development" or "Sustainable Software Development". It gives the feeling the author simply forgot to learn about agile development before he wrote the book. The explanation of story points was vague, the explanation of Use Case points unnecessary. The talk about return of investment forgot to give actual tools for doing so.
After the first 100 pages, I almost threw away the book and was pretty sure I would rate it 1 start. Though, luckily it started to improve. If you buy this book, I recommend to skip the first 100 pages :)
Chapter 7, 8, and 9 cover three portfolios: Project, resource and asset. The project portfolio covered some good ideas like increasing the portfolio decision frequency, using agile metrics and making other decisions than go/kill. The resource portfolio chapter was poor and doesn't talk much about resource management. The asset portfolio chapter is short but covers some important topics not covered frequently in other places.
Part three just consists of two chapters. The first one uses Scrum to become a portfolio management process. I found the idea interest and absurd. Especially the daily portfolio meeting and the portfolio master seen a sure sign of misapplication. The chapter is speculative, the real story about the real situation is missing. It made me doubt the author has actually done this. The second chapter of part three is a chapter about the PMO. I very strongly disagree with the suggestions from the author, especially making the PMO larger for Agile organizations.
In other words, I only thought that part two was worth my time (and only half of that) thats about 50 pages... Next to this, the writing and editing of the book was poor. Some constructions seem very German and sentences are constructed poorly making me sleepy while reading. I wonder if Microsoft Press did any editing at all or supported the author at all. Quite disappointing.
I would not recommend this book to anyone. It's probably better to read some traditional portfolio management book (e.g. Coopers Portfolio Management for New Products) together with some basic Agile books and especially Mike Cohn Agile Estimating and Planning (which covers much of the ROI and value calculation, but explained better). If you read all of these and want some insights and ideas from this book, just read chapter 7, 8 and 9 and skip the rest.
I still rated this book three stars, which is probably too high. After the first 100 pages, I was sure it would not be higher than 1 star. But some chapters contained some insights and that made me decide to give it 2 stars. I switched to three stars simply because I applaud the attempt. This is a new area, there is no existing material and it is great Jochen took this opportunity and tried to fill a gap. Though, a different book is probably needed.
3 of 3 people found the following review helpful.
Accurate Assessment of Conventional Software Processes?
By dmwpepper
While the basic description of agile portfolio management is useful, I found many of the claims about current software project practices to be based on exagerrated weaknesses of these conventional practices.
I believe the author exaggerates the differences between customer expectations and customer requirements. While they can be different, competent systems analysts can capture and document expectations, as well as requirement. The author's view is that traditional requirements analysis, for various reasons cannot be expected to capture customer requirements in a timely and "agile"/adaptable manner. My experience is different.
The author also claims that traditional project management practices contribute to a lack of agility. WBSs, GANT charts and other techniques are inherently inflexible, rigid and labor intensive, in his view. My experience with tools like Microsoft Project is that what-if scenarios and other hypothetical and actual adjustments are easy to create and provide the kind of decision support a project manager needs when requirements change, resources come and go, or schedules tighten unexpectedly.
Having worked on a number of rapid prototyping and quick reaction environments I realize that keeping up with customers that have a fast ops tempo and shifting focus can be a challenge. For that reason, I strongly agree with the author on the value of constant interaction with the customer and stakeholders, continuous builds, on-going testing and integration, teams being given wide latitude to focus on developing solutions and managers focusing on removing impediments. However, the author claims that these and other practices he discusses are unique to an agile development environment.
In my view, agile development represents just one confluence of best practices identified over many years and under different labels, such as rapid prototyping, joint application development, spiral development, Rational Unified Process (RUP), etc. While the author discusses these and other methodologies, I think his comparisons and contrasts with agile development are superficial. RUP, in particular, is not given its due as being an "agile" process and project management framework that can be used on different kinds of software projects.
I'm more of a middle of the road person. I tend to blend the strengths of many different approaches and when I read something that maximizes its strengths while exaggerating the weaknesses of other approaches, I tend to be skeptical. From my own experience with dynamic customer environments, I wonder if the author's description of agile development would lend itself to an EFFICIENT discovery of complex requirements. What's more efficient and agile, trying to code to "vague" requirements and continually coming back to the customer saying, "Is this the rock you wanted?" or holding some JAD sessions, getting with subject matter experts and prototyping aspects of the system that are not clearly understood? I'm not sure the author's description of agile development adds anything new to previous techniques for clarifying vague requirements or discovering unspoken requirements. It just takes a team of analysts, developers and stakeholders willing to work closely together, whether it be in the Elaboration phase of a RUP-based project, the 1st or 2nd iteration phase on a rapid-prototyping project or (get this) even in the requirements analysis phase of a traditional life cycle project.
Also, to me, the notion of "stories", "epics" and "themes" represent unnecessarily relabeled and watered-down versions of more mature UML techniques that model system structure, behavior and human-system and system-to-system interaction. To his credit, the author did spend time discussing the application of use cases which are easily implmented graphically and textually in UML.
While the author does bring together a number of concepts that are useful for running a project, he doesn't make the case that agile development, as a whole, is a major departure from conventional practices, but I like adding some of the "tools" he discussed to my toolbelt.
3 of 3 people found the following review helpful.
Forgettable
By PMO Manager
One fourth of the book is devoted to the usual waterfall badgering. Another fourth to motherhood statements about agile practices. Another fourth to simplistic ideas about project selection and resource planning. And another fourth to mmm..., what was the last fourth about?
Agile Portfolio Management, by Jochen Krebs PDF
Agile Portfolio Management, by Jochen Krebs EPub
Agile Portfolio Management, by Jochen Krebs Doc
Agile Portfolio Management, by Jochen Krebs iBooks
Agile Portfolio Management, by Jochen Krebs rtf
Agile Portfolio Management, by Jochen Krebs Mobipocket
Agile Portfolio Management, by Jochen Krebs Kindle
Tidak ada komentar:
Posting Komentar