Saturday, April 21, 2012

JourneyToSuccess - Board Game

In any business situation strategy and obstacles go hand in hand. Every one could use a refresher course in strategy. JourneyToSuccess is a game I have designed for teams that are involved in a variety of business scenarios. This game consists of two major parts. Playing Surface and Game Rules which are independent of business scenarios. Second part consists of Playing cards which are dependent of Business Scenarios. For example for Business Strategy there is one set of card and another set for Agile Methodology of Software development.

Here are details of Playing Surface and Playing Rules.
Journey to Success v1.0
Here are details of playing cards for Scrum ( Agile Software development methodology).

Card Scrum v1.0
I hope you will enjoy the game and will give valuable feedback.

Friday, April 20, 2012

Book Review: Getting Started with OAuth 2.0

Book Review: Getting Started with OAuth 2.0 by Ryan Boyd: Publisher- O'Reilly: ISBN- 13: 978-1449311605

Getting Started with OAuth covers the OAuth very nicely and certainly it is an asset for any software developer. If this book might have covered overview of OAuth in better way, certainly it might have achieved more success. It seems author has assumed that person reading this book has fair idea about OAuth. Nevertheless, book is good reference for any developer on OAuth 2.0.

Disclaimer: I did not get paid to review this book, and I do not stand to gain anything if you buy the book. I have no relationship with the publisher or the author. Further reading: One can read OAuth details on

Wednesday, April 11, 2012

Who cares about Software Quality?

For a software product there are primarily five groups of people (role) who care about quality of software.

1. Sponsors
2. Development Team
3. Purchasers
4. Users
5. Maintenance Team

In case of in-house development, non-productized software either Purchasers do not exist or Purchasers and Users become one.

Software has three dimensions of quality:
1. Functional
2. Structural
3. Process

Functional quality means that the software correctly performs the tasks it is supposed to do. The aspects of functional quality are:

Requirement fulfillment: For any software meeting functional requirements is Raison d'ĂȘtre.

Usability: No one is interested in software which is difficult to use and understand.

Structural quality is deals with code quality and non-functional requirements ( –bilities). It is difficult to test and measure.

The attributes of process quality are:

Delivery schedule: Are various pieces of software delivered on time?

Budgets: Are various pieces of software delivered within budget?

Repeatable development process: Even if software meets delivery schedule and within budget but it is not process driven, not a team work and cannot be created by similar team then process is not repeatable.

Process quality means being consistent from one project to the next.

Affordability: Software which has zero bugs but missing any aspects of time, budget, functionality or structure is of no use.

The process quality affects the value received by users, development team, development team, purchasers, and sponsors, and so all five groups have a stake in improving this aspect of software quality.