Web Based Agile Software Development - PowerPoint PPT Presentation

1 / 24
About This Presentation
Title:

Web Based Agile Software Development

Description:

How geographically distributed development environment meet the business market ... enchantment have fixed time to development. ... – PowerPoint PPT presentation

Number of Views:32
Avg rating:3.0/5.0
Slides: 25
Provided by: tcs7
Category:

less

Transcript and Presenter's Notes

Title: Web Based Agile Software Development


1
Web Based Agile Software Development
  • Mikio Aoyama, Niigata Institute of Technology
  • Area Agile Software Development
  • Presented by Tong Santee

2
Problem
  • geographically distributed software development
    environment increase development cycle.
  • How geographically distributed development
    environment meet the business market today that
    demands even more quickly deliver software
    product and also quick accommodate the
    requirement during development .

3
Answer for problem
  • Agile software process ( ASP ) develop
  • software quickly while maintaining the
  • flexibility needed to respond to
  • changing requirements in
  • geographically distributed nature.

4
Brief history
  • Since 1993, the ASP (agile software process )
    has been used in a large-scale communications
    software project at Fujitsu.
  • The author form Japan and did large research in
    the concurrent development process model .

5
Agile software process( software process is
segmented so that team can work on different
release concurrently)
6
What is enhancement
  • Enhancement
  • - requirements are divided or integrated
    into a unit . a unit that comprise multiple
    functions or modules.
  • enchantment have fixed time to development.
  • - Multiple enhancements can be developed
    concurrently and integrate as a system , and then
    delivered to custom as a release.
  • - An enhancement must be completed within a
    single release.
  • major enhancement part of software tightly
    coupled
  • minor enhancement part can divide between
    teams.

7
ASP Alter traditional management principle
  • 1) The process architecture shifts from
    massive to modular.
  • from the architecture view point , ASP
    consists two parts.
  • upper stream process
  • Lower stream process
  • several concurrent software process assigned to
    upper stream and lower stream across multiple
    teams.
  • each team iterates the 2 part, upper and lower
    stream release cycle.

8
ASP Alter traditional management principle
  • The ASP changes the underlying process model from
    a staged model to concurrent asynchronous.

9
ASP is iterative with fixed cycle time. So large
volume development can be divided into multiple
release then they can be development
incrementally and concurrently .
  • 1 group of functions incrementally developed in
    a series of release.
  • 2 design and implementation is iterated until
    the sub-system come to an acceptable level of
    functionality.

10
Current development process two concurrent
multiple enhancements, multiple releases

11
Managing in Real Time (to manage concurrent
development successfully )
  • Fixed cycle time is the Key to the ASP.
  • Mandate projects processes have fixed cycle time
    development
  • Set of concurrent process is regularly enacted
    over multiple release with a fixed time cycle.
  • Mandate right information to right people at a
    short time cycle.

12
ASP management hierarchy ,distributed flat across
the organization , and vertically down through
the project, team, and personal levels.
13
The methods ASP use
  • time based process en-action model
  • Just in time process management
  • These methods are play central role in managing
    ASP, and embedded into
  • 1) Prime (Process Information Manager )
  • 2) Web-based information sharing environment
  • 3) WAIN (Wide-Area information Network )

14
ASP environment each layer of the framework
related directly to one of three major issues(
collaboration, information sharing, and
distributed computing)
15
ASP environment vertically integrated a wide
variety of components at three level, support
process and product management.
16
for operation layer ( use Client-Server
platform)
  • client Individual developer and team leader
    access it .
  • Team server Team leader and project leader
    access it.
  • Project server Project leader and upper-level
    management access it.
  • every clients and servers database is build
    use the schema structure. Use SQL operation and
    Unix machines for server, Microsoft Window for
    client.

17
the information layer ( use Wide Area Information
Network )
  • WAIN is designed to manage the structured,
    semi-structured , and unstructured design
    documents.
  • use web and e-mail system.
  • Encapsulate the structure of various design
    documents and provide uniform access methods to
    the documents.
  • Enable developers to navigate across the
    distributed environment.

18
the collaboration layer ( use Prime --Process
Information Manager)
  • Support planning and execution of whole software
    process
  • in time guidance of individual developers
    software process.
  • Prime collects test results through the extranet
    from the distributed team server. Then generates
    the daily progress and bug charts at the team and
    project level.

19
An example use PRIME
20
Experience and Lesson Learned
  • use distributed continuous integration to avoid
    integration headaches
  • Have each site send ambassadors to the other
    sites
  • Use test scripts to help understand the
    requirements
  • Use short iterations
  • Separate team by function not activity

21
Comparison of the Water-fall Process and the ASP
22
Scope of research
  • Major reason why organization have problem with
    adopting agile methods -------- dont
    underestimate culture change.
  • The benefit of the agile from the client.
  • The future of offshore and agile.

23
References
  • 1. M. Aoyama, Concurrent-Development Process
    Model, IEEE
  • Software, July 1993, pp. 46-55.
  • 2. M. Aoyama, Agile Software Process and Its
    Experience, Proc.
  • 20th ICSE, IEEE Computer Soc. Press, Los
    Alamitos, Calif., Apr.
  • 1998, pp. 3-12.
  • 3. Mike Cohn and Doris Ford, Introducing an
    Agile Process to an Organization IEEE Computer
    Society , 2003
  • 4. Martin Fowler, Using an Agile Software
    Process with Offshore Development , September
    2003 First published
  • 5. Forrester Research, Inc. the Total Economic
    Impact TM of Using ThoughtWorks Agile
    Development Approach January 26. 2004

24
.
  • thank you
Write a Comment
User Comments (0)
About PowerShow.com