Loading ...
Sorry, an error occurred while loading the content.

41842RE: [!! SPAM] RE: [scrumdevelopment] What does agile really mean?

Expand Messages
  • Roy Morien
    Oct 11, 2009
    Hi Pam,
    I like the paper and the endeavour that it descibes. I do have in mind applying 'agile thinking' more generally to the presentation of a subject, replacing the 12 lectures and a final exam style of T&L.
    I have attached 2 papers that I have presented  at conferences about student experience using agile. The papers are obviously very similar, but one is sort of Paper Number One: The Sequel.
    Roy Morien

    To: scrumdevelopment@yahoogroups.com
    From: pmrostal@...
    Date: Mon, 12 Oct 2009 03:08:06 +0000
    Subject: Re: [!! SPAM] RE: [scrumdevelopment] What does agile really mean?

    Hi Roy,

    For an example of agile practices, values, and principles being applied in a university setting, see http://www.infoq. com/articles/ NMHU-scrum- university- apprentice.


    ----- Original Message -----
    From: "Roy Morien" <roymorien@hotmail. com>
    To: scrumdevelopment@ yahoogroups. com
    Sent: Sunday, October 11, 2009 9:46:12 PM GMT -06:00 US/Canada Central
    Subject: RE: [!! SPAM]  RE: [scrumdevelopment] What does agile really mean?


    Well, Dan, I work in two arenas, developing software, and teaching about developing software, so I guess my main emphasis is on Agile Software Development, and my use of the term 'agile development' was mainly intended to be read in that context.  I am not sure as to the implications of you capitalising "Agile Software Development" however.
    But I wonder why you seek to make the distinction, and why my list is so 'narrow'?
    I have been toying with the idea, for a long time, that agile practices ought to be applied to teaching and learning. Each week is essentially an iteration, commenced with a lecture that provides students with an increment in their learning. If by the end of the week that is 'Done' (ie: well learned a understood) then the student can move on, evolving their knowledge further. As the learning period (semester term) proceeds new ideas emerge as students add to ther knowledge. Information is presented to the student 'just-in-time' to be applied to an ongoing learning exercise or project. I belive that the 'teacher' should be a facilitator and guide to what ought to be learned, rather than being the sole source of wisdom, by 'teaching' the subject matter. I like to see my lectures as signposts indicating a direction to take, and my lecture plans to be a road map of the learning terrain, which I hope the students will traverse in collaborative groups.
    I think the analogies are there and can be expoited for effective learning.
    Unfortunately, the common approach to teaching and learning is exemplified in the student complaint 'but you didn't tell us that in the lecture', and the student requirement of 'please give us some exam hints for the exam next week', and the habit of cramming and memorizing the day before the final exam. Memorizing but not understanding. I prefer the model where the students start learning on a continual basis from week 1, working in supportive study groups, so by the time they arrive at the final exam, their confidence is at its highest, not its lowest. (which seems to be another similarity to software projects done in  the traditional way, where the maximum level of angst and anxiey is just before that great Feast Day known an Implementation Day.
    Anyway, Thanks for you response, and maybe a further explanation of your comments.
    Roy Morien

    > To: scrumdevelopment@ yahoogroups. com
    > From: dan.rawsthorne@ drdansplace. com
    > Date: Fri, 9 Oct 2009 03:26:38 -0700
    > Subject: Re: [!! SPAM] RE: [scrumdevelopment] What does agile really mean?
    > Good list, Roy, but it's "Agile Software Development" you are describing
    > here... not "agile development"
    > Only the "Empirical and Adaptive" part is agile.
    > Dan Rawsthorne, PhD, CST
    > Senior Coach, Danube Technologies
    > dan@..., 425-269-8628
    > Roy Morien wrote:
    > >
    > >
    > > I have compiled a list of 'characteristics' of 'agile development' ,
    > > based partly on other attempts to define it. Here is that list.Maybe
    > > it can be a starting point for discussion. What it does clearly imply
    > > is that agile is more than 'rapid application development' : more than
    > > 'software prototyping' , but it does, I think,subsume those prior terms
    > > and practices.
    > >
    > >
    > >
    > > Drawing on a variety of sources [1, 2, 3, 4] and synthesising the
    > > definitions and suggested characteristics in those sources, Agile
    > > development is seen to have these characteristics:
    > >
    > > · *People Focused:* (1) Collaborative: collaboration between
    > > developers and clients is continuous and continual, (2)
    > > Self-Organizing and Self-Managing Teams: Significant responsibility is
    > > handed to the team members, rather than a Project Manager, to decide
    > > on the work to be done in the next iteration.
    > >
    > > · *Empirical and Adaptive:* Project management practices that have
    > > been published to support ‘agile development’ practices are described
    > > as ‘empirical’, ‘adaptive’, ‘evolutionary’ or ‘experiential’ rather
    > > than ‘prescriptive’, or ‘pre-planned’.
    > >
    > > · *Iterative:* Development is achieved through a series of short
    > > iterations each of which produces a useable enhancement to the system.
    > > This provides a frequent and regular feedback cycle, and opportunities
    > > for validation and verification of successful progress.
    > >
    > > · *Incremental* : Development is achieved through a series of
    > > delivered increments to the system, each of which produces a fully
    > > developed, fully tested and certified extra feature or component of
    > > the system.
    > >
    > > · *Evolutionary* : the system grows in size, the requirements /in
    > > detail/ are continuously discovered, and are continually evolving
    > > during the development period.
    > >
    > > · *Emergent*: the whole of the system is greater than the parts. The
    > > characteristics of the system emerge as parts are added.
    > >
    > > · *Just-in-Time Requirements* * Elicitation* *:* Requirements are
    > > stated in detail ‘just in time’ to develop them, in the iteration in
    > > which those requirements will be implemented.
    > >
    > > · *Knowledge-Based: * Development activity is decided upon by the
    > > knowledgeable, self-managing members of the team, with continual
    > > knowledge sharing about the product, the technology and the progress
    > > of the project. Learning and knowledge sharing are emphasized.
    > >
    > > · *Client Driven, ‘*Pull-Based’ development: Only develop what is
    > > asked for by the Client, and when the Client asks for it.
    > >
    > > Agile methods emphasize project transparency, continual communication
    > > and collaboration between project partners.
    > >
    > >
    > > I have also attempted to draw in support for agile methods by defining
    > > various management practices as being reference disciplines for agile.
    > > I will be publishing this paper at a conference in Bangkok at the end
    > > of this month. If you are interested, I can post that paper here for
    > > critical discussion and as a contribution to the field.
    > >
    > > Regards,
    > > Roy Morien
    > > ------------ --------- --------- --------- --------- --------- --------- ------
    > > To: scrumdevelopment@ yahoogroups. com
    > > From: joshua.partogi@ gmail.com
    > > Date: Fri, 9 Oct 2009 11:31:31 +1100
    > > Subject: [scrumdevelopment] What does agile really mean?
    > >
    > >
    > > I found it these days that the terms 'agile' is kind of overstated.
    > > Especially by managers or end-users that does not really know what
    > > agile in software development practice really is. I also see this in
    > > some software framework marketing when a framework is said to be agile
    > > it means it can produce a software in a blink of an eye. To some
    > > people agile means deliver something fast, but in scrum and
    > > extreme-programming practice it not merely about delivering software
    > > quickly, but it's a mean to be able to adapt with the rapid changes in
    > > user requirement. It also means it delivers the functionality that is
    > > relevant for the user's current needs. It might require pulling of
    > > some requirement to the next iteration.
    > >
    > > Now, let's take an example the practices in XP like unit-testing and
    > > refactoring, this require some time to do and doing this practice not
    > > guarantee the product will be delivered faster than if not doing it.
    > > Pair programming and continuous build also is not a mean to produce
    > > the software faster, but it will produce a software that is less
    > > error-prone.
    > >
    > > What is your experience as a Scrum Master or Coach when dealing about
    > > this perception from someone that does not really understand what
    > > agile in software development really means? Is agile in software
    > > development really mean to deliver a software real fast? Or is this a
    > > misperception from some people when translating the word agile in
    > > software development? Or perhaps I am the one that got the wrong
    > > perception about what agile really means?
    > >
    > > Thanks for your insights.
    > >
    > > Kind Regards.
    > >
    > > --
    > > Certified Scrum Master
    > > http://twitter. com/scrum8 <http://twitter. com/scrum8> |
    > > http://blog. scrum8.com <http://blog. scrum8.com/> |
    > > http://jobs. scrum8.com <http://jobs. scrum8.com/>
    > >
    > >
    > > ------------ --------- --------- --------- --------- --------- --------- ------
    > > Find out how here Get Hotmail on your iPhone
    > > <http://windowslive. ninemsn.com. au/article. aspx?id=845706>
    > >
    > ------------ --------- --------- ------
    > To Post a message, send it to: scrumdevelopment@ eGroups.com
    > To Unsubscribe, send a blank message to: scrumdevelopment- unsubscribe@ eGroups.comYahoo ! Groups Links
    > <*> To visit your group on the web, go to:
    > http://groups. yahoo.com/ group/scrumdevel opment/
    > <*> Your email settings:
    > Individual Email | Traditional
    > <*> To change settings online go to:
    > http://groups. yahoo.com/ group/scrumdevel opment/join
    > (Yahoo! ID required)
    > <*> To change settings via email:
    > mailto:scrumdevelop ment-digest@ yahoogroups. com
    > mailto:scrumdevelop ment-fullfeature d@yahoogroups. com
    > <*> To unsubscribe from this group, send an email to:
    > scrumdevelopment- unsubscribe@ yahoogroups. com
    > <*> Your use of Yahoo! Groups is subject to:
    > http://docs. yahoo.com/ info/terms/

    Check out The Great Australian Pay Check Take a peek at other people's pay and perks

    Check out The Great Australian Pay Check Take a peek at other people's pay and perks
  • Show all 15 messages in this topic