Mapping Traditional Roles to Scrum

Many organizations, which have embarked on the Agile adoption path, have to tackle the challenge of mapping traditional software development roles to the three roles that Scrum provides. Traditional roles like Product Manager, Project Manager, Business Analyst, Designer, DBA etc. do not cleanly map into roles defined by Scrum. In a series of views Mike Cottmeyer attempts to effectively map traditional roles to Scrum.

Read more about it on InfoQ.

Performance Engineering in Scrum

Performance Engineering is an often neglected aspect in software development. This is a bigger pain in Agile where a heavy amount of focus is spent on adding business value which mostly translates to adding more functionality thus sidelining the so called Non-Functional Requirements.

My post on InfoQ tries to address this situation. Read and comment.

How to Scale Your Web Application Without Looking Outside?

You create a web application. The application becomes popular and you start getting a lot of traffic. Traffic which you had not imagined. The drawback … the response time increases, the threads on your web servers start building up and the application starts to get on its knees.

Under these circumstances what most organizations would do is to start looking externally at promise the world tools like terracotta, memcache, in-memory data grid, etc etc.

Nothing wrong with that and probably you would need them anyway but before getting there it might be worthwhile to look internally to see if there is stuff which could be done with the application. This includes

How to Give a Good Demo?

I happened to be in a demo last evening and that made me think that the world still needs to be reminded of how to do a good demo. I am not saying that I have conducted perfect demo’s all the time but then I have learned over time and these are my learning’s so far, feel free to add more and help

Learning’s so far -