Anurag Prakash

  

Project Manager, American Express

Location: Chandler, AZ, USA


Certifications

Certified ScrumMaster

Groups I belong to

Phoenix SUG


Activity

Anurag Prakash commented on the article, "Reorganizing for Agility I"

Anurag Prakash commented on the article, "Debugging Scrum Implementations"

Anurag Prakash commented on the article, "Debugging Scrum Implementations"

Anurag Prakash commented on the article, "Debugging Scrum Implementations"

Anurag Prakash commented on the article, "The Case Against Task Hours Reporting for a Sprint Burn-Down"

Biography

Bio not yet available for Anurag Prakash. If you are Anurag Prakash, login and then click Edit Profile to get started.

Work experience

American Express, Project Manager, Scrum Coach, Scrum Master
January 2012 - August 2013, Phoenix, AZ, United States

Project Manager, Scrum Coach, Scrum Master

Intel Corp, Scrum Master, Validation Arch, Program Manager, Team Lead, Developer
July 1999 - December 2011, Chandler, AZ, United States

Scrum Master, Validation Arch, Program Manager, Team Lead, Developer

Articles I've written

The Need to Include Design Topics During Agile Transformation
For effective Scrumming, stories should have the desirable INVEST characteristics: They should be independent, negotiable, valuable, estimable, sized, and testable). We'll assume that the product owner is trained in Scrum and creates clean stories...

What Is Sprint Zero?
The idea of Sprint Zero, like a lot of other things, has been used and abused. . . .

The Case Against Task Hours Reporting for a Sprint Burn-Down
Teams new to Scrum frequently push back on the Scrum rituals and the updates. The most painful of these is updating hours left. . . .

Debugging Scrum Implementations
Scrum is easy to learn but difficult to implement, as has often been said. Everyone I have met has had tons of issues, from how to size a story to "Oh, we have a constant stream of bugs." Let's examine broad categories of issues.

Dealing with Bugs in the Product Backlog
How do we deal with bugs in Scrum? Do we size them? Do we add them to a separate backlog? Or do we assign them to a different team running Kanban?

More Articles