12 PRINICIPLES OF AGILE MANIFESTO
by-step approach for developing information systems
1. Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
2. Welcome changing requirements, even late in development.
3. Deliver working software frequently, from a couple of weeks to
a couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily
throughout the project.
5. Build projects around motivated individuals.
6. The most efficient and effective method of conveying
information to and within a development team is face-to-face
conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development.
9. Continuous attention to technical excellence and good design
enhances agility.
10. Simplicity–the art of maximizing the amount of work not done–
is essential.
11. The best architectures, requirements, and designs emerge
from self-organizing teams.
12. At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.
SYSTEMS DEVELOPMENT
Information systems –support structure for meeting the
company’s goal
Systems development life cycle (SDLC) - a structured step-
7 PHASES
a) PLANNING PHASE – determining a solid plan for developing
IS
Three primary planning activities:
1. Define the system to be developed
Critical success factor (CSF) - factor critical to your
organization’s success
2. Set the project scope
Project scope - defines high-level system requirements
Scope creep - scope of the project increases
Feature creep - add extra features that weren’t part of the req.
Project scope document - a written definition of the project
scope
3. Develop the project plan including tasks, resources, and
timeframes
Project plan - defines what, when, and who questions
Project manager - expert in project planning and management
Project milestones - represent key dates for which you need a
group of activities performed
b) ANALYSIS PHASE - gather and document the business
requirements
Two primary analysis activities:
1. Gather the business requirements
Business requirements - detailed set of knowledge that the
system must meet
Joint application development (JAD) - workers and IT
specialists meet to review the business requirements
2. Prioritize the requirements
Requirements definition document –places bus. Req. in a
formal comprehensive document
c) DESIGN PHASE - build a technical blueprint
Two primary design activities:
1. Design the technical architecture
Technical architecture - defines the hardware, software, and
telecommunications equipment
2. Design system models
Modeling - graphical representation of a design
Graphical user interface (GUI) - interface to an IS
GUI screen design - ability to model the IS
d) DEVELOPMENT PHASE - transform detailed design
documents into an actual system
Two primary development activities:
1. Build the technical architecture
2. Build the database and programs
e) TESTING PHASE - verifies that the system works
Two primary testing activities:
1. Write the test conditions
Test conditions - detailed steps the system must perform
2. Perform the testing of the system
Unit testing – tests individual units of code
System testing – verifies that the units of code function
correctly
Integration testing – verifies that separate systems work
together
User acceptance testing (UAT) – determines if the system
satisfies business requirements
f) IMPLEMENTATION PHASE - using the system to perform
their everyday jobs
Two primary implementation activities
1. Write detailed user documentation
User documentation - highlights how to use the system
2. Provide training for the system users
Online training - runs over the Internet or off a CD-ROM
Workshop training - held in a classroom environment and lead
by an instructor
Choose the right implementation method
– Parallel implementation – use both the old and new system
– Plunge implementation – discard the old system
completely and use the new
– Pilot implementation – start with small groups of people on
the new system and gradually add more users
– Phased implementation – implement the new system in
phases
g) MAINTENANCE PHASE - monitor and support new system
Two primary maintenance activities:
1. Build a help desk to support the system users
Help desk – group of people who responds to questions
2. Provide an environment to support system changes
SYSTEMS DEVELOPMENT METHODOLOGIES
• Waterfall methodology - process is performed sequentially
from planning through implementation
• Rapid application development (RAD) - user involvement
in the rapid construction of working prototypes
• Extreme programming (XP) - breaks a project into tiny
phases
• Agile methodology - a form of XP, aims for customer
satisfaction through early and continuous delivery
1. Insourcing - involves choosing IT specialists within your
organization
2. Outsourcing - the delegation of specific work to a third
party
Request for proposal (RFP) – outsourcing document that
informs vendors of your logical requirements
OUTSOURCING OPTIONS
1. Purchase existing software
2. Purchase existing software and paying the publisher to make
certain modifications
3. Purchase existing software and paying the publisher for the
right to make modifications yourself
4. Outsource the development of an entirely new and unique
system for which no software exists
There are three different forms of outsourcing:
1. Onshore outsourcing - within the same country for services
2. Nearshore outsourcing - nearby country
3. Offshore outsourcing - geographically far away
Business process outsourcing (BPO) - contractual service to
manage business process
Prototyping - the process of building a model
– Proof-of-concept prototype - used to prove the technical
feasibility
– Selling prototype - used to convince people