Reminder define a methodology

1
Reminder define a methodology

• an explicit way of structuring ones thinking
  and actions 1 and
• A collection of procedures, techniques ,tools
  and documentation aids which will help the system
  developers in their efforts to implement a new
  information system 2

2
What is an agile methodology?

• Background
• Reaction against the SSADM type methodologies
• Impatience with the length of time taken to
  deliver projects
• Concern that (heavyweight) methodologies did not
  deal with change adequately
• Impact of web developments

3
What is an agile methodology?

• Also
• 4GL other developments
• Disposable programmes
• Commercial pressures
• Time pressures
• Not entirely new can see connections with RAD
  and other prototyping approaches

4
Manifesto for Agile Software Development

• Came out of a meeting in Feb 2001
• Participants included -
• Aim need for an alternative to documentation
  driven,heavyweight software development
  processes (see attached manifesto)

5

• We plan, but recognize the limits of planning in
  a turbulent environment. Those who would brand
  proponents of XP or SCRUM or any other agile
  Methodologies as hackers are ignorant of both
  the methodologies and the original definition of
  the term hacker
• //agilemanifesto.org/history.html

6
Extreme Programming

• Early delivery to get feedback and credibility
• Teamwork
• Changing environment
• Testing starts at the beginning (tests are
  created before code is written) and is a
  continuing activity. The emphasis on testing is
  one of the defining characteristics of XP
• http//www.extremeprogramming.org/rules.html

7
SCRUM

• Iterative incremental process for developing any
  product or managing any work
• http//www.controlchaos.com/
• Focus on teamwork and communication

8
SCRUM

• sprints (usually) month long iterations
• Projects are developed through sprints change
  is avoided during the course of a sprint
• Sprint planning meeting team selects from the
  project backlog the tasks that can be completed
  during the sprint
• Daily briefing meetings
• Sprint review meeting

9
Is there a continuum?

• Not a linear progression from heavyweight
  methodologies to lightweight methodologies
• SSADM XP
• Greatly over simplifies the process
• Overlooks project scope, type, technical
  developments
• Is not helpful

10
How do Methodologies develop?

• The Context of RAD
• Against the background of long development times
• Acknowledged difficulty of dealing with evolving
  user requirements
• New software 4GL, CASE etc
• Intended for I.S. type applications
• Increased user awareness and involvement
• Increased complexity of I.S. systems
• Prototyping developments of the late 80s

11

• One of the most urgent concerns in enterprises
  today is the need for I.S. organizations to
  create and modify applications much faster than
  with the traditional development lifecycle. If
  applications take two or three years to build and
  the application backlog is several years,
  businesses cannot create and react to competitive
  thrusts quickly enough. The vital ability for
  dynamic change is lost
• 3 Martin, 1991, preface

12
RAD Underlying principles

• No compromise between speed of development
  quality
• A different definition of quality quality is
  meeting business/user needs rather than
  conformity to the written spec
• Assumes that the shorter the elapsed time between
  design/the more likely the design is to be
  successful
• User involvement
• Small development teams
• Specifies methods and documentation

13
SUCCESSFUL RAD NEEDS -

• Heavy commitment in terms of user input. One
  reason why RAD sometimes runs into problems
• High level of communication and interpersonal
  skills
• The right people
• The right tools
• The right system?
• Can be difficult to scale

14
Benefits claimed for RAD

• Measurably improved productivity
• Flexible, adaptive methodology which encourages
  creativity
• Methodology has safeguards built into it to
  ensure delivery
• Increases user involvement/ownership so meets
  users needs more effectively
• More cost effective?
• Faster

15
Looking at Agile Methodologies

• What are the underlying principles?
• Do they specify methods as well an approach?
• What are the benefits?
• What is needed for a successful AM project?
• How does it work in practice?

16
References

• 1 Jayaratna Nimal (1994) Understanding and
  evaluating methodologies NIMSAD McGraw-Hill CA
• 2 Avison D.E., Wood-Harper T(1990) Multiview
  Waller UK
• 3 Martin J (1991) Rapid Application Development
  MacMillan N.Y