Creative Thinking Introduction article

Organized study of Creativity is necessary for simple and complex problem solving.
It is important that these creative skills are improved and practiced.

We all are Creative. It is a inherent quality which evolution of human beings and every advancements on earth provides. It is difficult to realize and acknowledge these skills though. Individuals should acknowledge the reality, that like any other skills creativity of a person can be improved.

I have been doing some study on Critical problem solving, Creative thinking and Logical reasoning. I will blog about my findings, research and practical experiences on this subject.

 I am an software developer and have my limitations in framing  imaginative, impacting quotes to sell ideas. I will keep it simple, practical and understandable for other folks like me.

Very good introduction to Creative Thinking from Robert Harris.

Summary of the article:

Robert Harris  discusses the following:

1) What is Creative thinking?
 – An ability, an attitude and a process for imagine or invent something new, accept change and newness and improve ideas and solutions.

2) Creative Methods – Evolution, Synthesis, Revolution and Reapplication and methods though which creative results can be produced.

3) Negative Attitudes that Block Creativity and Positive Attitudes Creating Creativity

4) Mental Blocks to Creative Thinking and Problem Solving

5) Myths about Creative Thinking and Problem Solving

User Stories Driven Development

User stories driven development is great way to do agile development. No better way to get the User, Product owner, developers and QA getting engaged together into active conversation through out the development cycle. Though simple, the implementation for new organization can get really difficult. System, process and people doing traditional long detailed requirements docs driven development have to unlearn lot of old practices before adopting new agile concepts of User stories. Roles and  responsibilities of each stakeholders are always at conflict and development organizations  struggle to get it right the first time. My suggestion is get the Agile champion to infuse new agile ideas and concepts. 
Old timers will always oppose it. Product management will get their hands off from writing User stories which contain just enough details to initiate the conversation between team members. They will always crib about the time constraints. We can not blame them, as they have been trained in writing either detailed requirement docs or Use Cases behind closed doors before other team members actually get a chance see it. There are other practices which make proactive dialog between Agile team memebrs difficult. Developers have ego,  they think they can read any requirement doc and craft it into a product. QA will always test and break what developer has implemented. Real user requirements are lost in this cycle because therir is npo active feedback loop keeing them on track. Finally user get a system as per the stated requirements but not what they wanted. 
Mike Cohn’s book on User story driven development is is great read. 

Persistence and Determination

“Nothing in this world can take the place of persistence. Talent will not; nothing is more common than unsuccessful people with talent. Genius will not; unrewarded genius is almost a proverb. Education will not; the world is full of educated derelicts. Persistence and determination alone are omnipotent. The slogan “press on” has solved and always will solve the problems of the human race.” – Calvin Coolidge

“Persistence isn’t using the same tactics over and over. That’s just annoying. Persistence is having the same goal over and over.” – Seth Godin on Persistence

“In the confrontation between the stream and the rock, the stream always wins – not through strength but by perseverance.” – H. Jackson Brown

Qualities of Software Architect – TaoDeJing’s readings applied.

Philippe Kruchten has summarized some of  TaoDeJing’s reading in his 2001 article – 
The Tao of the Software Architect

A good traveler has no fixed plans
and is not intent upon arriving.
A good artist lets her intuition
lead her wherever it wants.
A good scientist has freed herself of concepts
and keeps her mind open to what is.
Thus the architect is available to everyone
and rejects no one.
She is ready to use all situations
and does not waste anything.
This is called embodying the light.