memo

原典に当たるのが一番。

感動したのは、

The Manifesto struck a chord, and it led to many new Agile projects being started. As with any human endeavor, some succeeded and some failed.
But what was striking about the successes was how much both the business people and the technical people loved their project.
This was the way they wanted software development done. Successful projects spawned enthusiasts.

モノづくりの楽しさを感じられないような時に、
ここを思い出せたら。

Manifesto for Agile Software Development

We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on
the right, we value the items on the left more.

Principles behind the Agile Manifesto

We follow these principles:

Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.

Welcome changing requirements, even late in
development. Agile processes harness change for
the customer’s competitive advantage.

Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.

Business people and developers must work
together daily throughout the project.

Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.

The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.

Working software is the primary measure of progress.

Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.

Continuous attention to technical excellence
and good design enhances agility.

Simplicity–the art of maximizing the amount
of work not done–is essential.

The best architectures, requirements, and designs
emerge from self-organizing teams.

At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.

モスバーガーの店員だけど何か質問ある

モスバーガーの店員だけど何か質問ある？

133 ：名無しさん＠ローカルルール変更議論中：2005/12/30(金) 02:07:19 ID:MIxpzGW+
おい、>>1
モスバーガー共々　大　好　き　だぞ。
ファーストフード食べないようにしてるがモスには行ってしまうよ。
野菜がシャキシャキうまいよ。1もまあ、バイトだか社員だか何だか知らんが
体壊さん程度に頑張れ！ただでさえ好きなモスの社員が、1のおがげでさらにいいイメージ持った！
だからこのｽﾚが落ちても気にすんな！
じゃ！

135 ：１：2005/12/30(金) 02:37:49 ID:wB3O/GIH

133
深夜にニヤニヤさせないで下さいw
出来るだけシャキシャキなハンバーガー作れるように頑張るよwwwww

感動した。
保存した。
よだれ出た。
今週またいこう。