ABSTRACT. The stated, accepted philosophy for systems development is that the development process is a well understood approach that can be planned, estimated, and successfully completed. This has proven incorrect in practice. SCRUM assumes that the systems development process is an unpredictable, complicated process that can only be roughly described as an overall progression. SCRUM defines the systems development process as a loose set of activities that combines known, workable tools and techniques with the best that a development team can devise to build systems. Since these activities are loose, controls to manage the process and inherent risk are used. SCRUM is an enhancement of the commonly used iterative/incremental object-oriented development cycle.
Quite often people struggle with giving and receiving feedback.
The basic method to apply when expressing feedback is to separate feelings and needs from observations.
This is a structured 4 step approach to express feedback in a non-violent way:
1. OBSERVATIONS = FACTS
What I observe.
"When I (see, hear) ...
2. FEELINGS = EFFECTS
How I feel.
"I feel ..."
3. NEEDS = MOTIVATION
What I need or value.
"... because I need/value ..."
4. DIALOGUE + ACTION (= suggestions)
The concrete actions I would like taken (by the other person)
... Would you be willing to ... ?
What are your experiences? Have you tried to communicate in this way?