Arthur M. Young’s Theory of Process.

Young advocated a process theory, which is a form of integral theory. These theories attempt to integrate the realm of human thought and experience with the realm of science so that the concept of universe is not limited to that which can be physically measured. Young's theory embraces evolution and the concept of the great chain of being. He has influenced such thinkers asStanislav Grof and Laban Coblentz.

The Stages of Organization Model provides a system-level language for understanding the evolutionary development of organizations. 

lizard brain - The new idea is shot down and the old hand gets points

In many ways, our brain has evolved since we were cave dwellers. But the part of the brain responsible for survival still exists, even though we are no longer running from saber toothed tigers. The Lizard Brain switches off the Thinking Brain where reasoning, understanding happens. It’s the part of you that will keep you from trying anything risky or new. How does it happen and why we what can we do about it?

Organization Change Ethnography Approach -The 'Insider's Point of View

Our goal is to see people’s behavior on their terms, not ours. Ethnographers generate understandings of culture through representation the 'insider's point of view. 

To develop an understanding of what it is like to live in a setting, the researcher must both become a participant in the life of the setting while also maintaining "detachment."

Organizational ethnography promises to elucidate two aspects for which other methods, such as surveys, are less suitable: (1) its “hidden” dimensions, and (2) its actor‐context relations.

Kanban for Customer Support

Kanban is about ensuring that tasks flow steadily and continuously through the system and continuously improving. But what if you’re dealing with customers and with their questions/requests?  How do you keep the flow running with verity of issues? How can you set an SLA? And how do you know you have improved?

Agile Coaching - First session - New employee orientation - workload and priority

By: shirly Ronen-Harel

Backround:

• New testing manager appointed from inside the department to manage the testing activities within this department
• Area of responsibility and priorities needs to be defined and visible.
• Outcome – clear understanding of scope of work.

Step 1 : Visualize areas of responsibilities

Technique – building an initial backlog – high level view.

Step 2 :  visualizing the professional areas of responsibility : an example

Going forward and mapping the severity of issues in each area

Identifying  problematic areas

Start to set the correct priority inside the areas of responsibility 

Visualization benefits (example)

While going forward we start to drill down into important areas only(just enough)

Next step

Building high level backlog with drill down to main items.

Building the high level implementation plan.

Embracing Variability in Agile Project Development

"For a manufacturer, paradise is a world without variability. Such a world would be very hostile for a product developer, because variability is the ever present traveling companion of innovation. How does agile development deals with variability? Agile software developers already grasp the importance of responding to change….. But, what does this mean? Is there more to it than just saying, “I will respond to change.” Indeed, there is." Don Reinertsen

Knowledge Management in Agile Organization

In software development the most important asset is knowledge. Companies would want their performance to keep improving from project to project. They would want their workers to increment their own experience bank by adding new information that was gathered during  their last development and use it in their new development. Agile methodologies create organisational cultures that encourage cooperation and learning. It designs organisational work practices to include constant information sharing.  These practices help with transferring the tacit knowledge needed for improving performance .

How to do scrum in a team of one and why?

There may be cases in agile development where we want or need to develop a product in a form of one man scrum. There are more than just few reasons for doing that but mainly more questions of how should we address this issue. Here are some interesting reviews for professionals out on the field on why should we adapt this personal approach and if so, how?