Paper Writing Service http://StudyHub.vip/AGILE-PROJECT-MANAGEMENT 👈

1. AGILE PROJECT
MANAGEMENT
Deal with the challenges
Dr. Maria Fragkaki, 2016

2. CONCEPT: AGILE MANAGEMENT
Agile Management term
• Agile management, or agile
process management, or
simply agile refer to an iterative,
incremental method of managing
the design and build activities for
engineering, information
technology, and other business
areas that aims to provide new
product or service development in
a highly flexible and interactive
manner;
Iterative and Agile Methods
• Agile X techniques may also be called extreme
process management. It is a variant of iterative life
cycle[2] where deliverables are submitted in stages.
Both iterative and agile methods were developed as
a reaction to various obstacles that developed in
more sequential forms of project organization
• The main difference between agile and iterative
development is that agile methods complete small
portions of the deliverables in each delivery cycle
(iteration)
while
• iterative methods evolve the entire set of
deliverables over time, completing them near the
end of the project.

3. Adaptive Project life cycle
• Adaptive project life cycle, a project
life cycle, also known as change-driven
or agile methods, that is intended to
facilitate change and require a high
degree of
ongoing stakeholder involvement.
• Adaptive life cycles are also iterative
and incremental, but differ in that
iterations are very rapid (usually 2-4
weeks in length) and are fixed in time
and resources.[6]
• In project
management terminology, resources are
required to carry out the project tasks.
They can be people, equipment,
facilities, funding, or anything else
capable of definition (usually other
than labour) required for the completion
of a project activity. The lack of a
resource will therefore be a constraint on
the completion of the project activity.
• Resource scheduling

4. AGILE SOFTWARE DEVELOPMENT
Agile Software
Development: terminology
Agile software development is a set of
principles for software development in
which requirements and solutions evolve
through collaboration between self-
organizing,[1] cross-functional teams. It
promotes adaptive planning,
evolutionary development, early delivery,
and continuous improvement, and it
encourages rapid and flexible response
to change
Agile Methods
• Agile Methods- "Rolling Wave" approach to
schedule planning, which identifies milestones
but leaves flexibility in the path to reach them,
and also allows for the milestones themselves
to change
• Low Critically
• Senior Developers
• Requirements change often
• Small number of Developers
• Culture that respond to Change
• Very short feedback loop and adaptation
cycle

5. Agile Methods
• Agile methods are focused on different
aspects of the software development life
cycle. Some focus on the practices (e.g.
XP, pragmatic programming, agile
modeling), while others focus on
managing the software projects (e.g.
scrum). Yet, there are approaches
providing full coverage over the
development life cycle (e.g. DSDM, RUP),
while most of them are suitable from the
requirements specification phase on
(FDD, for example). Thus, there is a clear
difference between the various agile
methods in this regard.[39]
Agile Characteristics
• A common characteristic in agile is
the daily "stand-up", also known as
the daily scrum. In a brief session,
team members report to each other
what they did the previous day
toward their team's sprint goal,
what they intend to do today
toward their team's sprint goal, and
any roadblocks or impediments
they can see to their team's sprint
goal.

6. AGILE DEVELOPMENT
METHODOLOGY

7. AGILE SOFTWARE DEVELOPMENT
METHODOLOGIES
• is a splitting of software development work into distinct phases (or stages)
containing activities with the intent of better planning and management. It is
often considered a subset of the systems development life cycle. The
methodology may include the pre-definition of specificdeliverables and
artifacts that are created and completed by a project team to develop or
maintain an applic
• Common methodologies include waterfall, prototyping, iterative and
incremental development, spiral development, rapid application
development, extreme programming and various types of agile
methodology.ation.[1]

8. “SCRUM” THROUGH ACTION
RESEARCH
• Scrum is an iterative and
incremental agile software
development framework for managing
product development. It defines "a
flexible, holistic product development
strategy where a development team
works as a unit to reach a common
goal", challenges assumptions of the
"traditional, sequential approach"to
product development, and enables
teams to self-organize by encouraging
physical co-location or close online
collaboration of all team members, as
well as daily face-to-face
communication among all team
members and disciplines in the project.
• A key principle of scrum is its
recognition that during production
processes, the customers can change
their minds about what they want and
need (often called requirements
volatility, and that unpredicted
challenges cannot be easily addressed
in a traditional predictive or planned
manner. As such, scrum adopts
an empirical approach—accepting
that the problem cannot be fully
understood or defined, focusing instead
on maximizing the team's ability to
deliver quickly, to respond to emerging
requirements and to adapt to evolving
technologies and changes in market
conditions.

9. SCRAM FRAMEWORK: AN AGILE
PRODUCT BACKLOG
• The agile product backlog (apothem)
in Scrum is a prioritized features list,
containing short descriptions of all
functionality desired in the product.
• The Sprint Backlog is the output of
the sprint planning meeting that it is
time frame worked (discovering and
setting of tasks)through a daily process
• An Agile retrospective is a meeting
that's held at the end of an iteration in
Agile software development (ASD ).
During the retrospective, the team
reflects on what happened in the
iteration and identifies actions for
improvement going forward.

10. SCRAM FRAMEWORK-KEY ROLES
• The framework involves three key roles:
• 1. The product owner is an expert on the product
being developed. He or she represents key
stakeholders, customers, and end users, and is
responsible for prioritizing the project and getting
funding.
• The product owner describes how people will use the
final product, communicates customer needs, and
helps the team develop the right product. His or her
expertise also helps combat scope creep.
• 2. The scrum master is responsible for managing the
process. This person solves problems, so that the
product owner can drive development, and
maximize return on investment. The scrum master
ensures that each sprint is self-contained, and that it
doesn't take on additional objectives.
• The scrum master oversees communication, so that
stakeholders and team members can easily
understand what progress has been made.
• 3. The team is the group of professionals responsible
for turning requirements into functionality.
• The team will work on each project via "sprints" –
short phases of work which deliver completed,
tested, documented, and functioning products at
their conclusion.
• Each sprint begins with a sprint planning meeting.
Here, team members decide what they can deliver
within the agreed timeframe. They define the goal
and assign task responsibilities

11. SCRAM PROCESS

12. • SAFE: Scale Agile Framework
• DAD: Discipline Agile Delivery
• NEXUS

13. MY ICT IDEAS FOR AGILE
DEVELOPMENT
Scrum framework development
via CRITICAL ACTION RESEARCH Scrum agile development via
easy accessible ICT Tools
 Flipping Activities setting the problem and the tasks of
the project (sgile product backlog) through video-
capturing (panopto video)
 Agile product backlog (apothem) is a prioritized features
list, containing short descriptions of all functionality
desired in the product (scrum test board through Padlet,
Shared docs)
 Sprint Backlog is the output of the sprint planning
meeting that it is time frame worked (discovering and
setting of tasks)through a daily process (Google groups,
shared syghronus douments)
• Agile retrospective is a meeting that's held at the end of
an iteration in Agile software development (ASD ). During
the retrospective, the team reflects on what happened
in the iteration and identifies actions for improvement
going forward (inspiration, free-mind)