Introducing 

Prezi AI.

Your new presentation assistant.

Refine, enhance, and tailor your content, source relevant images, and edit visuals quicker than ever before.

Loading content…
Loading…
Transcript

Plan-driven and agile development:

How does it work?

Scrum:

Plan-driven development

Agile development:

Difficulties:

General software process model

-Software specification

-Development

-Validation

-Evolution

-All processes and activities are planned in advance

-Progress is measured against the plan

-Separate stages in software process with associated output

-Product iterations occur within the activities

-Handles changing requirements

-Good for fast moving business environments

-High degree of customer involvement

-People focused rather than process

-Continual product iterations

-Commonly associated with web-design/-development

Typically used with the incremental development model

-Development team

-Develops the product

-Responsible for delivering functioning chunks

-Self.organizing

-Cross skill platform

Plan-driven:

-Rigid structure

-Difficult to change user requirements (without damaging plan

-Depends on clear procedures

-Very management oriented, less people oriented

Agile:

-Difficult to assess effort required in large projects

-Very little documentation

-Less finished deliverable parts during process

-Project can easily be taken off track (if customer is not clear in their wishes)

-Requires senior knowledge to perform proper assessments

Agile development tool.

Contains three roles:

-Product owner

-Stakeholders

-"Voice of the customer"

-Ranks the user needs

-Decides what goes into

backlog

-Scrum master

-Accountable for keeping the

team in optimum working conditions

-Not a traditional team leader

-Buffer between team and distracting

influences

Sprint:

-Defined period of time (7-30 days)

-Work-to-be-done selected

-Sprint backlog defined (time assigned to each task)

-Identify work capabilities during sprint

Daily meeting:

-Entire team gives update on their current work situation

(yesterday -> today ->tomorrow)

End meeting:

-Review of the sprint

-Completed work (PSPi) is shown

Product backlog:

-What MUST be delivered in final product

Waterfall model is an example of this:

Learn more about creating dynamic, engaging presentations with Prezi