Scribd
Upload
11 views22 pages

Sepm IA 2

The document outlines the Agile process, emphasizing its adaptability to changing requirements and the interleaving of design and construction. It lists 12 agility principles from the Agile Alliance that prioritize customer satisfaction, collaboration, and sustainable development. Additionally, it touches on topics related to software project management, including project management life cycles, categorization of software projects, and the comparison between traditional and modern project management processes.

Uploaded by

ankitha90355
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
11 views22 pages

Sepm IA 2

The document outlines the Agile process, emphasizing its adaptability to changing requirements and the interleaving of design and construction. It lists 12 agility principles from the Agile Alliance that prioritize customer satisfaction, collaboration, and sustainable development. Additionally, it touches on topics related to software project management, including project management life cycles, categorization of software projects, and the comparison between traditional and modern project management processes.

Uploaded by

ankitha90355
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 22

SEPM IA-2 ANSWER

MODULE-3
1)define Agile process and agility principle
Any agile software process is characterized in a manner that addresses a number
of key assumptions [Fow02] about the majority of software projects:

1. It is difficult to predict in advance which software requirements will persist


and which will change. It is equally difficult to predict how customer priorities
will change as the project proceeds.

2. For many types of software, design and construction are interleaved. That is,
both activities should be performed in tandem so that design models are proven
as they are created. It is difficult to predict how much design is necessary before
construction is used to prove the design.

3. Analysis, design, construction, and testing are not as predictable (from a


planning point of view) as we might like.

Agility Principles :
The Agile Alliance (see [Agi03], [Fow01]) defines 12 agility principles for
those who want to achieve agility:

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. Agile processes


harness change for the customer’s competitive advantage.

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. Give them the environment and
support they need, and trust them to get the job done.

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. The sponsors, developers,
and users should be able to maintain a constant pace indefinitely

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.

2)with the neat diagram explain extreme programming


3)write a short note on scrum and crystal
4)explain core principle and practices of software
engineering
MODULE-4
1)what is software project management ?explain project
management life cycle?
2)list and explain categorizing software projects
3)explain traditional vs modern project management
process

4)how to assess project success and failure in software


project management

You might also like