Agile Roles

Product Owner is responsible for "What" part of it.
Team is responsible for "How" part of it.
Scrum Master or Project Manager is responsible for "Process".

PMBOK and Agile

After getting PMP certified in May 2011, recently, I conducted a session in my company on an Overview of Agile and Scrum. This allowed me to explore Agile further and further, which took me to the point where I started getting a feeling and hearing that PMBOK is Waterfall Methodology based process and Agile is not part of it.

I started googling and also viewed YouTube videos to my doubts. Finally, I found different supportive videos and pages which proved that it was my misconception, my myth. PMBOK is guide, it is standards for Project Management. PMBOK teaches of WHAT do in Project management and Agile's different methodology teaches you HOW to implement that in Software Development by using suitable methodology like Scrum, Extreme Programming (XP), Crystal, Dynamic Systems Development Method (DSDM), Feature-Driven Development (FDD), Lean Software Development. PMBOK is a guide and Agile's methodology tells you how to do. PMBOK does not echo waterfall.

Agile is a philosophy. Agile is a way of Thinking and not just doing.

Scrum Terminology

Following article on Scrum is very well defined. I think this would be useful for few out there...

Scrum Terminology

is made up of three roles, four ceremonies, and three artifacts.

Three roles

• Product owner: responsible for the business value of the project
• ScrumMaster: ensures that the team is functional and productive
• Team: self-organizes to get the work done

Four ceremonies

• Sprint planning: the team meets with the product owner to choose a set of work to deliver during a sprint
• Daily scrum: the team meets each day to share struggles and progress
• Sprint reviews: the team demonstrates to the product owner what it has completed during the sprint
• Sprint retrospectives: the team looks for ways to improve the product and the process.

Three artifacts

• Product backlog: prioritized list of desired project outcomes/features
• Sprint backlog: set of work from the product backlog that the team agrees to complete in a sprint, broken into tasks
• Burndown chart: at-a-glance look at the work remaining (can have two charts: one for the sprint and one for the overall project)

[Source]

What is Velocity in Agile Environment?

Velocity is the rate at which Sprint teams delivers business value at consistent rate. Velocity is calculated by adding story points of the user stories which are successfully accepted by business in a sprint.