software process... the good parts
Post on 20-Aug-2015
1.694 Views
Preview:
TRANSCRIPT
Crystal
•Frequent Delivery
•Reflective Improvement
•Close or Osmotic Communication
•Personal Safety
•Focus
•Easy Access to Expert Users
•Automated Tests, Configuration Management and Frequent Integration.
Recipe for Success
•Focus on Quality
•Reduce Work-in-Progress
•Deliver Often
•Balance Demand against Throughput
•Prioritize
•Attack Sources of Variability to Improve Predictability
ARxTAWe believe Agile software development is being dumbed down, commodified, and is losing its spirit. We seek to replace the current name with one having two virtues: first, that it capture more exactly the attitudes originally behind Agile; second, that it be obscure enough that no one will assume they already know what it means and that—amazingly enough!—they are
"If you want to build a ship, don't drum up people to collect wood and don't assign them tasks and work, but rather teach them to long for the endless immensity of the sea." - Antoine de Saint Exupéry
6 Laws Of Reliability
Isolation
Concurrency
Failure Detection
Fault Identification
Live Upgrade
Stable Storage
says nothing about computers
Advocacy
• I really like kanban
• I really like XP technical practices
• focus on quality
• everything depends on context, but in context make policies explicit
• if something doesn’t feel right, you are doing something wrong, might be that thing, but might be you
• if you aren’t getting results, change something
• if you are changing too much too often, you won’t get good results
• measure
• process is a competitive advantage, passion is a competitive advantage, don’t let process kill passion
• smart people solve problems
top related