Indian Medicine

The Agile Manifesto seems like ancient history now.  The concepts of iterative development were not new - but they hadn't been marketed until the manifesto was published and the movement was unleashed. In  late 1999 or early 2000 I can remember sitting in a meeting room with the Assistant CIO of a large healthcare organization .. describing my preference for using what I then called an iterative development process - where we would define "bite-sized parts" for implementation, exposure, and refinement on a regular basis.  She had never heard of such a thing - and advocated for the developers on the team:  "They need to know when it's finished!"  Me:  "This is software - it's never finished" "But the customer needs to sign off on a completed project.  How can we know that it will meet the customer need?" "uuuh ... ask them?" "We ask them during the requirements process - when they define the project" "And that is successful?  They are always happy with the final product?" "Well - no - but if they didn't describe their needs appropriately - that isn't our concern.  So long as they have signed off on the spec before the development work begins - we have clarity for the what the requrements are - and if we build it to spec - we've completed the project and we can move on." .. I stopped trying.  Clearly the goal here was to complete the project "to spec" and move on to the next project.  There was a problem though - developers were bypassing standard process - and interacting directly with customers (with no management oversight) and were creating solutions collaboratively with customers. So the Ass(istant) CIO wanted to give the developers a sense of closure .. but the developers wanted to please the customers - and bypassed their managers to do so! Trouble in them thar hills, too.  With no Human Factors training - and minimal design skill - developers all-too-often gave the customers what they asked for rather than what they needed.  End result: ACIO came down hard on such "renegade" developers. This reinforced the waterfall mentality.  :-(

The Agile Manifesto seems like ancient history now.  The concepts of iterative development were not new - but they hadn't been marketed until the manifesto was published and the movement was unleashed.

In  late 1999 or early 2000 I can remember sitting in a meeting room with the Assistant CIO of a large healthcare organization .. describing my preference for using what I then called an iterative development process - where we would define "bite-sized parts" for implementation, exposure, and refinement on a regular basis. 

She had never heard of such a thing - and advocated for the developers on the team: 

"They need to know when it's finished!" 

Me:  "This is software - it's never finished"

"But the customer needs to sign off on a completed project.  How can we know that it will meet the customer need?"

"uuuh ... ask them?"

"We ask them during the requirements process - when they define the project"

"And that is successful?  They are always happy with the final product?"

"Well - no - but if they didn't describe their needs appropriately - that isn't our concern.  So long as they have signed off on the spec before the development work begins - we have clarity for the what the requrements are - and if we build it to spec - we've completed the project and we can move on."

I stopped trying.  Clearly the goal here was to complete the project "to spec" and move on to the next project. 

There was a problem though - developers were bypassing standard process - and interacting directly with customers (with no management oversight) and were creating solutions collaboratively with customers.

So the Ass(istant) CIO wanted to give the developers a sense of closure .. but the developers wanted to please the customers - and bypassed their managers to do so!

Trouble in them thar hills, too.  With no Human Factors training - and minimal design skill - developers all-too-often gave the customers what they asked for rather than what they needed.  End result: ACIO came down hard on such "renegade" developers.

This reinforced the waterfall mentality.  :-(

All of us know that to lose weight we all need to make permanent changes in our eating habits. It is much easier said than done. So many of us return to our old eating habits after a short interval of time and thus regain the weight back.We need to convert a diet in to our way of eating. Here I am suggesting you some tips to convert the diet in to your way of eating and stick with your diet for

Losing weight is not as easy as many of us think. It is in fact a big challenge for all of which we have to face and get success. There are some facts about weight loss we have to avoid. We all need to be realistic while setting the targets and diets to follow for us. So here I am suggesting you some things to avoid if you are going to try losing weight: Do not be too mush tough with your diet

WASHINGTON (Reuters) - An outbreak of salmonella food poisoning linked to peanut butter has widened to 329 people in 41 states, the U.S. Centers for Disease Control and Prevention reported on Thursday.