jaycross 's Library tagged → View Popular, Search in Google
The Agile Model of HR states that Human Resources job is not just to implement controls, standards and drive execution, but rather to facilitate and improve organizational agility.<br />This changes HR's mission and focus. Driving agility means driving programs which create adaptability, innovation, collaboration, and speed.
What I believe is most important is embracing agility, with strong influences from lean approaches. This applies more now than when I originally developed the idea of AID. Knowledge domains are changing and growing very rapidly and lessening rituals and focusing on what is important (for the now) is paramount to learning within the knowledge based economy.
The Agile Elearning Design Manual - Agile Re-explained<br />In my last post we looked at the problems with our existing approach to building elearning. In summary, the problems we noticed were:<br />A lack of shared understanding within the team, about the the customer's learning problem.<br />The high risk associated with not having generalists in the team.<br />The delay in seeing working pieces of elearning.<br />The time spent in creating documentation and in analysis.<br />The risk of endless reviews and amendments.
The first couple of responses to this month's LCBQ Addressing I Want it Now #LCBQ have come in and Kasper Spiro's caught my eye: On demand: agile e-Learning development #LCBQ. Like Kasper, I'm very familiar with Agile in software development. I was not as familiar with it in terms of eLearning development.<br /><br />
Building a learning ecology is a different exercise than building a training program. In lieu of top-down control, it relies on continuous experimentation and evaluation. It takes coordination, flexibility, and on-going conversation. These qualities are at the heart of the discipline of agile programming. Hence, I am exploring how well the principles of agile programming might be incorporated into a new framework for instructional design.
Design as knowledge creation<br />Several people have written about design as knowledge creation. Donald Reinertsen in his excellent book Managing the Design Factory discusses that a key output of design work is the knowledge that is gained. Philip Armour writes that what we really learn when we deliver the software is how to build the software we just delivered. A quick Google even turns up a company Knowledge Evolution, Inc. (which has a nearly empty website, sadly) whose sole purpose is to support this line of inquiry.
As I said in an earlier column, it’s not enough to slap the tile of Scrum Master or Agile Coach on a project manager, manager, or whatever other warm body happens by. It’s also not enough to look for the keywords “CSM” or “coach” on a resume.<br /><br />If you are serious about helping teams learn and thrive as self-organizing Agile teams, get serious about ScrumMasters and Agile Coaches. Start thinking about the work, the role, and the job–not just the job title.
WHAT IS THE ALLIANCE?<br /><br />The Agile Alliance is a nonprofit organization with global membership, committed to advancing Agile development principles and practices. Agile Alliance supports those who explore and apply Agile principles and practices in order to make the software industry more productive, humane and sustainable. We share our passion to deliver software better everyday.
Josh Kerievski
<br /><br /><br />For nearly a decade, our band of experts has helped enterprises around the globe step into their agile groove.<br /><br />Discover how we can help you improve the rhythm and beat of your software development process.
Agile has crossed the chasm and things are different over here. Really different. And not so good.<br /><br />It feels like we have landed at Dieppe (Canadian/British Military WW2 Failure). Not everybody's happy.
The bad news is that there is significant failure successfully adopting Agile. The good news is that we can recognize it and learn from it.<br /><br />Technology Adoption and The Chasm<br />Michael Moore’s crossing the chasm introduces the notion of phases in technology adoption.
Problems with the Agile Alliance ten years after. Some of the arguments are rather thin.
The Elephants in the Agile Room<br />FEBRUARY 13, 2011<br />An “elephant in the room” is a metaphor for the behaviour of people who deliberately ignore an impending issue. They are fully aware of some major issue that really must be tackled or decided upon, but everyone keeps busy tackling other, often small items, ignoring the big issue, pretending it does not exist, hoping maybe that it will vanish by magic or that someone else will take care of it; that one day the elephant will have left the room.<br /><br />During the 10 years agile celebration meeting in Snowbird, UT, organized by Alistair Cockburn on February 12, after covering the walls with a couple of hundred issues cards, David Anderson noted that there was “an elephant in the room”, a topic that few are willing to debate in the pen, namely the Agile Alliance (its role, mission, accomplishments, etc.). After the lunch, a small group gathered and identified a few other such elephants in the room, other topics that the agile community is not really willing to tackle for a variety of reasons. We ended up with a long list of about 12 such “undiscussable” topics (or at least not discussable in the open).
In light of Agile adoption failures and awareness of cultural challenges, the purpose of this post is to review current models that are applied to adopting Agile and transforming with Agile at organizations. Worthy background reading is Mike Cottmeyer’s post on Untangling Adoption and Transformation.<br /><br />It is worth noting that there is no widespread agreement about how to undertake agile adoption.<br /><br />A Tour of Adoption and Transformation Models<br />Below a number of models for Agile adoption and organizational transformation are shown.
Here is John Seddon’s (Vanguard) keynote speech presented at the Øredev 2010 conference in Malmö, Sweden. This should be required viewing for anyone who’s involved in building Information systems.
The Art of Agile Development<br /><br />Welcome to the The Art of Agile Development book site! Here, you'll find a cornucopia of bonus material, such as downloadable posters, behind-the-scenes material, and new insights.<br /><br />Starting in 2010, you'll also find the full text of the book, conveniently cross-referenced and hyperlinked. A new section will be released every Friday, starting with the practices in Part II.<br /><br />For bonus features and online text, follow the links in the table of contents. Sections that include full text are marked with a star .
In particular, agile development accelerates the delivery of initial business value, and through a process of continuous planning and feedback, is able to ensure that value is continuing to be maximized throughout the development process. As a result of this iterative planning and feedback loop, teams are able to continuously align the delivered software with desired business needs, easily adapting to changing requirements throughout the process. By measuring and evaluating status based on the undeniable truth of working, testing software, much more accurate visibility into the actual progress of projects is available. Finally, as a result of following an agile process, at the conclusion of a project is a software system that much better addresses the business and customer needs.
Great article
Selected Tags
Related Tags
Top Contributors
Groups interested in agile
-
Agile
Agile Programming and Process
Items: 21 | Visits: 73
Created by: Lakshminarayanan Venugopal
-
IT Management Conference & Expo in NYC Oct.14-16
http://www.manageit.me ---Th...
Items: 2 | Visits: 47
Created by: Jackie Fields
-
Lean SW Quality
Links and notes related to l...
Items: 247 | Visits: 40
Created by: juha riissanen
Diigo is about better ways to research, share and collaborate on information. Learn more »
Join Diigo
