Shuk's contribution to Software Extension to the PMBOK® Guide (2013)

1. 3/25/13 Gmail - PMI Notification Email
Aditya Shukla <mailplz@gmail.com>
PMI Notification Email
1 message
Project Management Institute <DoNotReply@pmi.org> Mon, Mar 25, 2013 at 6:23 AM
To: aditya.shukla@alumni.usc.edu
Cc: karl.best@pmi.org
Notification from PMI regarding The Software Extension to the PMBOK® Guide
Thank you for participating in The Software Extension to the PMBOK® Guide Exposure Draft process.
Below you will find a list of the recommendations that you have made and the committee’s decision for
each of your recommendations. If you have any additional questions or comments you can contact Karl
Best at Karl.Best@pmi.org.
If you are unsatisfied with the final decision made by the committee you have the opportunity to appeal.
You will have two weeks, until Sunday, 7 April 2013 to do so. Click on the "Go to Exposure Draft" link
provided below for more information.
Go to Exposure Draft
Adjudication will end on: 3/24/2013
OriginalText
808
2.2.1 Software Project Stakeholders
Your Recommendation
Add a section 2.2.1.1 explaining Key Stakeholders
Your Justification
I would suggest to make clear note on Stakeholders and Key stakeholders in S/W project
management. Variety of time, I have seen many projects managers miss this in variety of S/W
projects. I S/W project management 80/20 rule applies really well. Your 20% stakeholder
essentially decide 80% or more features/success of your project. From the para under section
2.2.1 it seems project mangers equally emphasis all stakeholders even though they are affected
very remotely. Calling out Key Stakeholder make it very clear and projects managers can prioritize
deliveries with the exit criterion coming from key stakeholders first.
Our vote on your recommendation: Accepted With Modification
Our justification: Thank you for taking the time to provide feedback on the exposure draft for
Software Extension to the PMBOK® Guide Fifth Edition. The core committee has reviewed your
recommendation and determined that the text will be modified in a manner consistent with the
recommendation
https://mail.google.com/mail/u/0/?ui=2&ik=b7b1e3c8ab&view=pt&search=inbox&th=13da1b8107531066 1/3

2. 3/25/13 Gmail - PMI Notification Email
OriginalText
898
Your Recommendation
Add a new category: Specialist Generalist Vs. (Pure) Specialist
Your Justification
We call a new category which kicks out "specialist only" category within a team. In fact, I have not
seen any pure specialist in my S/W career. We usually have specialists in teams who are
generalist for some other tasks/skill sets. For example, an excellent Java specialist is capable of
understanding (or at least quickly picking up) HTML code or JavaScript. In case if we need help of
this specialist in his/her downtime, s/he performs as generalist in the same team.
Our vote on your recommendation: Rejected
Our justification: We usually have specialists in teams who are generalist for some other
tasks/skill sets. For example, an excellent Java specialist is capable of understanding (or at least
quickly picking up) HTML code or JavaScript. In case if we need the help of this specialist in his/her
downtime, s/he performs as generalist in the same team.
OriginalText
898
Your Recommendation
Add a new category: Specialist Generalist Vs. (Pure) Specialist
Your Justification
We call a new category which kicks out "specialist only" category within a team. In fact, I have not
seen any pure specialist in my S/W career. We usually have specialists in teams who are
generalist for some other tasks/skill sets. For example, an excellent Java specialist is capable of
understanding (or at least quickly picking up) HTML code or JavaScript. In case if we need help of
this specialist in his/her downtime, s/he performs as generalist in the same team.
Our vote on your recommendation: Rejected
Our justification: We usually have specialists in teams who are generalist for some other
tasks/skill sets. For example, an excellent Java specialist is capable of understanding (or at least
quickly picking up) HTML code or JavaScript. In case if we need help of this specialist in his/her
downtime, s/he performs as generalist in the same team.
OriginalText
1227 Product size for adaptive software projects is often measured in stories, use cases, or
Your Recommendation
We need add Epics (or large feature sets)
Your Justification
Product size for adaptive s/w projects is often relatively measured (in rough order of magnitude) in
the form of Epics, stories or uses cases..
Our vote on your recommendation: Deferred
Our justification: editorial decision; your recommendation will be forwarded to the team that
prepares the next edition of this extension
https://mail.google.com/mail/u/0/?ui=2&ik=b7b1e3c8ab&view=pt&search=inbox&th=13da1b8107531066 2/3

3. 3/25/13 Gmail - PMI Notification Email
OriginalText
1231 complete the implementation of a set of features. A measure of productivity call velocity,
Your Recommendation
A measure of productivity some times also referered as velocity
Your Justification
Looks better to me as I wrote!!
Our vote on your recommendation: Accepted With Modification
Our justification: "A measure of productivity call velocity" will be changed to "A measure of the
team's production rate, sometimes referred to as velocity, is the ratio" on line 1231.
OriginalText
1232 which is the ratio of work products produced to amount of effort expended during an
Your Recommendation
which is ratio of completed (developed and fully tested) features to amount of effort expended an...
Your Justification
not necessarily all work produced can account for velocity. Only work which meats success
criterion/exit criterion is counted toward team velocity.
Our vote on your recommendation: Accepted With Modification
Our justification: "A measure of productivity call velocity" will be changed to "A measure of the
team's production rate, sometimes referred to as velocity, is the ratio" on line 1231.
https://mail.google.com/mail/u/0/?ui=2&ik=b7b1e3c8ab&view=pt&search=inbox&th=13da1b8107531066 3/3