https://aznot.com/index.php?action=history&feed=atom&title=OpenWest_2014%2FAgileOpenWest 2014/Agile - Revision history2026-04-30T05:52:31ZRevision history for this page on the wikiMediaWiki 1.41.0https://aznot.com/index.php?title=OpenWest_2014/Agile&diff=54&oldid=prevKenneth at 01:14, 12 May 20142014-05-12T01:14:01Z<p></p>
<p><b>New page</b></p><div>by Hala Saleh, Dir. Product Management, Rentlr<br />
<br />
<br />
Agile Manifesto - http://agilemanifesto.org<br />
* Individuals and interactions - over processes and tools<br />
* Working software - over comprehensive documentation<br />
* Customer collaboration - over contract negotiation<br />
* Responding to change - over following a plan<br />
<br />
<br />
Agile Principles principles<br />
* Collaboration<br />
* Continuous feedback and improvements<br />
* Self-organizing teams<br />
* Simplicity<br />
* Retrospectives<br />
* Frequent and Continuous delivery<br />
* Inspect-adapt cycle<br />
* Sustainable pace<br />
* Timeboxing<br />
<br />
<br />
Agile development - iterative and incremental approach to developing software that incorporates continuous feedback loops, adaptability and collaboration<br />
<br />
But agile is not only for software<br />
<br />
<br />
Ready to work?<br />
* Step 1: Identify the Problem<br />
* Step 2: Is Agile the Answer? Is your culture compatible? Start with processes and implement incremental changes.<br />
** book "Becoming Agile in an Imperfect World" by Smith and Sidky<br />
<br />
<br />
Conclusion:<br />
* Agile can't make you a better executive (it is not a silver bullet)<br />
* Learn it, Live it, Do it<br />
* Learn from others<br />
* Cultivate a tolerance for Failing Fast<br />
<br />
---<br />
<br />
Agile Principle 1: Satisfy the Customer<br />
Agile Principle 2: Embrace Change<br />
Agile Principle 3: Frequent Delivery<br />
Agile Principle 4: Cross-Functional Collaboration<br />
Agile Principle 5: Support and Trust<br />
Agile Principle 6: Face-to-Face Conversation<br />
Agile Principle 7: Working Software<br />
Agile Principle 8: Sustainable Pace<br />
Agile Principle 9: Technical Excellence<br />
Agile Principle 10: Keep it Simple<br />
Agile Principle 11: Self-Organization<br />
Agile Principle 12: Inspect and Adapt<br />
<br />
---<br />
<br />
<pre><br />
Principles behind the Agile Manifesto<br />
http://agilemanifesto.org/principles.html<br />
<br />
We follow these principles:<br />
<br />
Our highest priority is to satisfy the customer<br />
through early and continuous delivery<br />
of valuable software.<br />
<br />
Welcome changing requirements, even late in<br />
development. Agile processes harness change for<br />
the customer's competitive advantage.<br />
<br />
Deliver working software frequently, from a<br />
couple of weeks to a couple of months, with a<br />
preference to the shorter timescale.<br />
<br />
Business people and developers must work<br />
together daily throughout the project.<br />
<br />
Build projects around motivated individuals.<br />
Give them the environment and support they need,<br />
and trust them to get the job done.<br />
<br />
The most efficient and effective method of<br />
conveying information to and within a development<br />
team is face-to-face conversation.<br />
<br />
Working software is the primary measure of progress.<br />
<br />
Agile processes promote sustainable development.<br />
The sponsors, developers, and users should be able<br />
to maintain a constant pace indefinitely.<br />
<br />
Continuous attention to technical excellence<br />
and good design enhances agility.<br />
<br />
Simplicity--the art of maximizing the amount<br />
of work not done--is essential.<br />
<br />
The best architectures, requirements, and designs<br />
emerge from self-organizing teams.<br />
<br />
At regular intervals, the team reflects on how<br />
to become more effective, then tunes and adjusts<br />
its behavior accordingly. <br />
</pre></div>Kenneth