27. Team Structure
- Silo
- Clearly responsibility
credit-http://www.flickr.com/photos/stevensnodgrass/6117660537/
Thursday, May 9, 13
28. Team Discipline
• Document Oriented
• Timeline is king
• Each step has clearly definition of document
standard
credit-http://www.flickr.com/photos/stevensnodgrass/6117660537/
Thursday, May 9, 13
29. Individual Discipline
• Mostly make something “done” but not “right”
• Mostly said “please don’t change it”
• Mostly make it for last, not for change
http://www.flickr.com/photos/paul-w-locke/3529691660/in/photostream/
Thursday, May 9, 13
31. Finally
Poor Quality
Unpredictable
Lost In Translation
Burn out
Sad, Bad, ..... ?
http://intothetopcorner.files.wordpress.com/2012/05/ucl-final-25.jpg
Thursday, May 9, 13
36. We follow these principles:
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.
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.
Thursday, May 9, 13
37. 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.
Thursday, May 9, 13
39. Team Discipline
• User first with Good Experience
• Change is good
• Eliminate unchangeable modules
http://www.chrislabrooy.com/UX_design.html
Thursday, May 9, 13
40. Individual Discipline
• Super Clear and have to follow, Make it “RIGHT”
• Test : Code : Refactor
http://www.flickr.com/photos/amberdebruin/5657750874/
Thursday, May 9, 13
41. Agile is About
Adaptation OverAnticipation
http://www.flickr.com/photos/12463666@N03/7256710194/
Thursday, May 9, 13
43. Eliminate waste
Amplify learning
Decide as late as possible
Deliver as fast as possible
Empower the team
Build integrity in
See the whole
Thursday, May 9, 13
44. Start using agile
Start small
Solving problem one by one
http://www.flickr.com/photos/igal/7901479448/
Thursday, May 9, 13
