4 Prerequisites for Reducing Sprint Duration

Agile manifesto has explicit stated preference for shorted sprints. Shorter sprints can ensure that: “Parkinson’s Law” does not set in, that is work does not expand to fill the available time “Understanding gap” between users and developers gets ironed out quickly “Quick response to change” becomes possible However, there are other factors which may make too … Continue reading

Distributed team in different timezone and Product Ownership

How do you work with a remote product owner who is in a different time zone with very little overlap of normal working hours? An agile puritan would have a simple answer – Don’t. There is an underlying assumption behind this statement. The assumption is that the product owner can provide an instant clarification and decision to … Continue reading

Evolutionary Architecture and Conway’s Law

Way back … in 1968, Melvin Edward Conway, an early computer scientist, computer programmer, and hacker postulated that… Organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations. Or more concisely… Any piece of software reflects the organizational structure that produced it. For example, if you have … Continue reading

Are Large Software Projects like Eating an Elephant?

How do you eat an elephant? Simple – cut it into small pieces at eat one piece at a time. BUT… …is it really that simple? When you have a large software project it is too simplistic to assume that all you need to do is to decompose the problem to individual manageable chunk which … Continue reading

Is Agile Elitist?

Best way to do software development is to get hold of master programmers. Get them to form a self organizing team and do the development in short increments. That is agile. What happens if you cannot find sufficient number of master programmers? Get as many master programmers as you can. For the rest of the … Continue reading

Agile, Offshoring and Dreyfus Model of Learning

Agile works! If you have any doubt about it just look at the adoption rate … look at the study results published … or just try it yourself. Offshoring also works! Again, if you have any doubt, just look at the growth of offshoring … look at the success of the success of the India … Continue reading

How has the world changed since Agile Manifesto happened?

Agile Manifesto was (formulated? signed? declared?) in 2001 February. The manifesto was born out the software development challenges faced in the 90’s. More than a decade has passed and we live in a different world. 6 ways the world has changed 1) Pace of change has become faster and faster Technology is changing faster. User … Continue reading

Does the Agile Manifesto read like a Deceleration of Independence?

The Agile Manifesto happens to be a unique piece of document. I cannot find any equivalent document in whole of software engineering history. Why only software engineering, I cannot think of any equivalent in any field of engineering. Think of how it was developed. In February, 2001, seventeen like-minded people got together and came up with the manifesto. … Continue reading

Is Offshore-Agile a Bad Idea?

Yes … if you have a co-located cross-functional team … and … there is no pressure or compulsion to shift part of the work offshore. Yes … if you do not feel any necessity or face any difficulty in scaling the team. In all other cases offshore-agile may not be such a bad idea. If you must … Continue reading

(Offshored-Distributed-Outsourced) Agile: What is the relation between them?

Is off-shore agile a special case of distributed agile? Can the term offshore agile and outsourced agile be used interchangeably? If you have done distributed agile, then can you claim to understand off-shored agile and outsourced agile? Similarly, if you have mastered off-shored agile you say with confidence that you understand distributed agile and outsourced agile? Lastly, if you have … Continue reading