Manifesto for Agile Software Development
12 Principles of Agile Software
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
- Phase 1: Point out objects, and say the name.
- Phase 2: Point out objects, and say a name which is not what it is.
It looks silly, but it gives you flexibility.
Agile focuses not about what happened, about what is happening.
Responding to change over following a plan
I felt I was doing something wrong, but it was quite new experience, actually it was tough to think of the idea(different name).
- Close your eyes, speak following the instructor's voice.
Sorry, I couldn't understand how it works.
- Reply with YES and continue the conversation.
It tells you how to agree.
The manifesto says
Customer collaboration over contract negotiation
The principle says
Welcome changing requirements, even late in development.
- Structure(process, hierarchy, politics, payslips...) and Chaos(opportunity, uncertainty, divergence, inefficiency, complicity...)
- Creativity is from between Structure and Chaos.
I didn't get it, I guess it meant The Edge of Chaos
- WAAT
- Making stories by combining one word from each. (Once upon a time ...)
In this case, structure was English, Chaos was individuality. I haven't had enough English skill yet.
- Reply with NO and continue the conversation.
It's difficult to continue, because of answering NO. I think it's a good to know how NO works in a bad way.
- Create a container, it access the brain where you don't use normally
Expands your mindfield.
It's like brain storming, plus organizing ideas by myself.