Scribd
Upload
11 views

Unit 2

Uploaded by

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

Unit 2

Uploaded by

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

What is agile project management?

• Agile project management is an iterative approach


to delivering a project throughout its life cycle.
• Iterative or agile life cycles are composed of
several iterations or incremental steps towards the
completion of a project. Iterative approaches are
frequently used in software development projects
to promote velocity and adaptability since the
benefit of iteration is that you can adjust as you go
along rather than following a linear path.
One of the aims of an agile or iterative approach is
to release benefits throughout the process rather
than only at the end. At the core, agile projects
should exhibit central values and behaviours of
trust, flexibility, empowerment and collaboration.
Extreme Programming (XP)
• Extreme Programming (XP) is a method of
improving software quality and response to
changing needs through continuous delivery,
collaboration, and practices like test-driven
development. Its goal is to allow small to mid-
sized teams to produce high-quality software
and manage changing customer requirements
• What sets it apart from the other agile
methodologies is that XP focuses on the
technical aspects related to software
development. It is all about following the best
practices, as the right engineering practices
can go a long way in delivering high-quality
code at a sustainable pace.
Principles of Extreme programming

• Constant and early feedback: Feedback is a traditional


approach followed in the waterfall software
development methodology. XP embraces change, and
the teams strive to receive early and constant feedback.
If you need to change or redefine the existing
processes, you can do it as soon as possible.
• Feedback can come in many different ways. One such
instance is pair programming, where the vital
comments from your peers act as feedback for making
improvements. It is important to handle feedback
comments constructively
• Assumed simplicity: Developers need to focus on tasks
with the highest priority and maximum business impact.
• Incremental changes: It is about making small and iterative
changes to the product rather than building the entire
product in one go. When you perform incremental
changes, you get constructive feedback from the customers
that help you improve the existing product.
• Embracing change: It is all about considering the
customer’s viewpoints and opinions and then adapting to
the change. If a client thinks that a product functionality
needs to be changed, the development team should
support this decision and plan how to incorporate the new
requirements.
• Quality work: The team collaborates closely to deliver
quality output within stipulated timelines.
Basics of Software estimation – Effort and Cost
estimation techniques
• Estimation is the process of finding an estimate, or approximation,
which is a value that can be used for some purpose even if input
data may be incomplete, uncertain, or unstable.
• Estimation determines how much money, effort, resources, and
time it will take to build a specific system or product. Estimation is
based on −
• Past Data/Past Experience
• Available Documents/Knowledge
• Assumptions
• Identified Risks
• The four basic steps in Software Project Estimation are −
• Estimate the size of the development product.
• Estimate the effort in person-months or person-hours.
• Estimate the schedule in calendar months.
• Estimate the project cost in agreed currency.
Cost Estimation Models
COSMIC Full function points - COCOMO II
• COSMIC function points are a unit of measure of software functional
size. There are other ways to assess software size, but COSMIC Sizing
is the most universal, meaningful and useful approach. The
functional size is consistent regardless of the technology used to build
it. The size can be estimated, or if all requirements are available,
measured. Early estimation is very useful for planning and managing
software endeavours (projects or product management). The process
of measuring software size is called functional size measurement
(FSM).

• COSMIC functional size measurement is applicable to business


software, real-time software and infrastructure software at any level
of decomposition (from a whole software system down to a single re-
usable component or a user story). The functional size (inc COSMIC
Function Points – CFP) is independent of the technology or processes
used to develop the system. COSMIC is an ISO standard. It is a
refined improvement over its predecessors (IFPUG and Mark II FP).
The unit of size is the COSMIC Function Point or CFP.

You might also like