This week's book giveaways are in the Cloud/Virtualization and Go forums.
We're giving away four copies each of Cloud Native Transformation: Practical Patterns for Innovation and The Go Workshop and have the authors on-line!
See this thread and this one for details.
Win a copy of Cloud Native Transformation: Practical Patterns for InnovationE this week in the Cloud/Virtualization forum
or The Go Workshop in the Go forum!

Matt Daniels

+ Follow
since Feb 01, 2013
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Matt Daniels

Both have their pros and cons. Project Management is a deeper subject while scrum is more or less just limited to IT related projects and has a much smaller scope within that. IF you are familiar with PMP i would suggest you become more familiar with scrum as well, for a quick understanding you can access multiple links online to enhance your subject knowledge. You can access a lot of free stuff at regarding scrum from various websites.
Hi Jennifer Bellamy,

Regarding your question, the 60 pdu's needed at the end of the 3 years can infact be collected in the third year itself but i would suggest against it. Simply because the reason for creating a continuous education pattern would be defeated if you only do it to maintain your certification rather than to learn and grow as a project manager. However at the end of the day its your call. You can visit - to get a deeper understanding on how to maintain your PMP certification. Also it would be advisable to identify PMI REP's who provide multiple courses along with PDU's so you can tie up with one and make it that much easier for yourself. I personally am making use of and now, both offered by the same provider amongst other courses along with valid PDU's. The call is yours

Generally speaking a team goes thru the classical four stages of team development - Form, Storm, Norm, Perform. If the team has been together for a longer time period i.e over a few months (lets say 8 -10) and you are still facing the same problems with the particular team member, the only logical action steps i see are firstly trying to understand the root of the problem and addressing the same, and if that doesnt work ejecting the member.
I think that is a very valid point, people do get influenced by the name now be it Scrum Master or Agile Expert or what ever it may be its the name that influences the response from people. Thanks for the insight, well put
@ Ashley Morris : I personally believe that we have a habit of complicating simple roles and rules to sound fancy. At the end of the day a product owner role is an evolution of a standard business analyst profile and hence the term product owner is unnecessary. The need of the role is to communicate the customers / stakeholders POV during the SDLC which till before this was being effectively done by a Business Analyst and hence i stand by what i said. However you are entitled to your own views so cheerio.

There is a very basic difference between a scrum master and product owner role. A scrum master is a facilitation role where as the product owner decides the features, communicates between clients and the scrum team and so forth. Quite simply put Product owner is a evolved role from an ordinary business management ( unnecessary if you ask me). However if you are looking for certifications i would suggest Scrum Master Certification over product owner. I did mine at , you can pick and choose what suits you best.


Just wanted to add some more details. There is no certifying body for Scrum Certification. There are a few websites like which give you the different providers and also how and in what they vary. You can go through the same and pick the one that suffices your needs the best.