Module 2
Module 2
(i)Organic Mode
E = 3.0 * (400)1.12=2462.79 PM
D = 2.5 * (4772.8)0.32 = 38 PM
Project Management Tools
Documentation Tools
Documentation in a software project starts prior to the software
th
Scrum is a framework that helps agile teams to work together. Using it, the team
lessons can be applied to all kinds of teamwork. Its policy and experiences is a reason of
to ship high quality, work faster, and more frequently. The sprints give them more
plan is to define what can deliver in the sprint. It also focuses on how the work will be
ways.
What is the product backlog?
A product backlog is a registered list of work for the development
team. It is driven from the roadmap and its requirements. The
essential task is represented at the top of the product backlog so
that the team member knows what to deliver first. The developer
team doesn't work through the backlog from the product owner's
side and product owner doesn't push the work to the developer
team. The developer team pulls work from the product backlog.
Backlog starts with the two "R"s
The fundamental product backlog is provided by a
team's roadmap and requirements. Roadmap repetition breaks
down into several epics, and each epic will have several
requirements and user stories.
The product owner organizes each of the customer stories into a
single list. This story is organized for the development team. The
product owner chooses to deliver first complete epic.
this visual team helps team members and stock members quickly to understand what the
team members pick up plans when they are ready. The committed point is a movement
Software metrics is a standard of measure that contains many
classified into three categories: product metrics, process metrics,
and project metrics.
Product metrics: describe the characteristics of the product such as
manager to check the project's progress. Data from the past projects are
used to collect various metrics, like time and cost; these estimates are used
as a base of new software.The project manager will check its progress from
Scope of Software Metrics
following
Cost and effort estimation
Data collection
Quantity models and measures
Reliability models