PMI ACP intrebarea 3: Agile e metoda sau nu? E ARTA!

Si intrebarea 3:

Which of these is not a method?

(A)      Lean
(B)      Scrum
(C)      Agile
(D)      XP

Aici ajungem la alt post http://agile-romania.blogspot.de/2011/01/metoda-metodologie-sau-proces-cum.html unde filosofam daca Scrum este metoda, metodologie sau proces.

Ei zic asa:

Why (C): Is a philosophy or principles, not a method.
Why NOT (A), Why NOT (B), Why NOT (D): All these are methods or practices

Referinta: The Art of Agile Development - James Shore & Shane Warden, chap 2, page 9

Eu as putea adauga ca Agile este mai mult decat o filosofie, este ARTA! Nu degeaba intrebarea are o referinta catre cartea "The Art of Agile Development".

PMI ACP intrebarea 2: ban la ban trage

Si sa trecem mai departe la intrebarea 2:

A project was considered as challenged since it went over budget and beyond schedule when it was completed for a total cost of $3 million.  But the clients eventually claimed it to be a success.  Which one of the following reasons could potentially justify their claims?

(A)      The business was affected seriously since budget re-allocation had to be performed to fund the project to completion
(B)      The clients ended up spending an extra $2 million on this project
(C)      The project was estimated to save the client organization 20 man-years worth of man power
(D)      A review report after 12 months indicated that the client saved $11 million

O mica observatie:

challenged = contestat

challenging = provocator

Chiar simpatica intrebarea! Am rezolvat-o usor dupa logica urmatoare: avem in enunt bani, bani trebuie sa avem si in raspuns. Deci singurul raspuns corect nu poate fi decat D).

Ei zic asa:
Why (D): This is stating the fact, that has already occurred
Why NOT (A): Actually stating what the question says and is not adding anything to the client's claim to success
Why NOT (B): Indirectly stated in the question (over budget)
Why NOT (C): This looks promising, but a closer look makes it clear that this is only an “estimate”, with no guarantee of this happening

Dau si o referinta: The Art of Agile Development - James Shore & Shane Warden, chap 1, page 4

PMI ACP intrebarea 1: from project management perspective

Mi-a trecut prin cap sa incerc sa ma certific PMI ACP. Groaznic! Hai sa va demonstrez!

Pana una alta voi lua intrebari gasite pe Internet si voi incerca sa le comentez.

Traditional criteria for project success include meeting time, budget and specifications.  From a project management perspective, a project meeting these criteria may be considered a success, but may still fail in the end.  Which of these may be a good reason?

(A)      They fail to appeal to the intended users
(B)      They fail to add much value to the business
(C)      Project management success does not translate to business success
(D)      They fail to satisfy the customers needs

Asta e genul de intrebare pe care o iubesc. Ma uit la toate cele patru raspunsuri posibile si la prima vedere nu pot exclude nici macar unul. Daca se reciteste cu atentie intrebarea se observa un mic detaliu care iti poate scapa la prima vedere: "from a project management perspective".

Deci sa vedem cum argumenteaza ei raspunsurile:

(A)      They fail to appeal to the intended users 

Why NOT (A): Project success cannot be determined by individual likes / dislikes

Avem un proiect care esuaza din cauza ca nu prezinta interes pentru utilizatorii carora le-a fost destinat. Pentru mine e un bun motiv de insucces, deci raspuns posibil. Gresit! Nu trebuie sa gandim decat din punct de vedere al managementului de proiect. Poate ca proiectul a avut noroc, a facut in scaldatoare in faza de initiere, si, din intamplare, desi a fost un produs adresat manelistililor de 20-25 ani, a avut un succes imens in randul iubilorilor de opera, categoria de varsta 45-50 de ani.

(C)      Project management success does not translate to business success

Why NOT (C): The issue here is not about project management success

Bun! Proiectul nu are succes in business dar NU NE INTERESEAZA! Operatia a reusit, pacientul a murit! Ce daca pacientul a murit?

D)      They fail to satisfy the customers needs

Why NOT (D): It is possible that even though the customer is satisfied, the project may fail to add value to the business. 

Odata ce te-ai hotarat sa elimini raspunsul (C), e foarte usor de eliminat si raspunsul acesta.

(B)      They fail to add much value to the business Why (B): Without value, a project cannot be considered a success even if we consider that it came on schedule, within scope and budget 

Ati vazut unde era cheia? Cuvintele cheie sunt: add value to the business. Probabil ca pe undeva, printr-o carte ce nu poate fi citita decat de manageri, scrie clar: Traditional criteria for project success include meeting time, budget, specifications, value added to the business. Simplu, nu? Va rog insistent sa considerati ca a satisface nevoile clientilor nu are nici o legatura cu valoarea adaugata business-ului :D!