Scribd
Upload
258 views

DSDM Task

The document describes a Dynamic System Development Method for a multinational corporation (MNC). It outlines the key roles including CEO, clients, project manager, project leader, and team members. It then describes the activities and responsibilities of each role. It also outlines the typical DSDM phases of requirement analysis, software design, coding, and testing. Additionally, it describes the MoSCoW prioritization technique and provides a timebox/schedule example.

Uploaded by

Arjun Chaudhary
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
258 views

DSDM Task

The document describes a Dynamic System Development Method for a multinational corporation (MNC). It outlines the key roles including CEO, clients, project manager, project leader, and team members. It then describes the activities and responsibilities of each role. It also outlines the typical DSDM phases of requirement analysis, software design, coding, and testing. Additionally, it describes the MoSCoW prioritization technique and provides a timebox/schedule example.

Uploaded by

Arjun Chaudhary
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Dynamic System Development Method for MNC

1. Actors:

● CEO
● Clients
● Project Manager
● Project Leader
● Team members

2. Activities from the perspective of the roles:

CEO
He/She is the one who oversees the strategic direction of the organization. He/she brings
up the clients and makes business relationships with them. He/she implements the
changes and proposed plans and engages in the media obligations & public
relations.He/she also monitors the company’s employee performance and interacts with
the leading executives.

CLIENT
The client is the one who is looking for a company/organization or that can help them to
overcome the difficulties by providing the software requirements and assistance.

Project Manager
A project manager is one who takes tasks and information from the CEO and plans and
develops the project ideas. He/she creates the team and assigns a member to lead the
project to monitor the project’s progress frequently. They are also responsible for solving
the issues if anything arises at any moment, ensuring the stakeholder's satisfaction, and
also evaluating the project member performance.

Project Leader
A project leader is one who makes proper decisions regarding the project by assigning the
tasks to individuals and making the team work cooperatively. They are responsible for
developing the team scheduling and assisting in the successful completion of projects
with other individuals in the team.
Team Members
Team members are the ones who are at the ground level of each project phase by doing
tasks like coding, testing, building, etc.

3. DSDM Phases:

I. Requirement analysis and software specifications: This stage starts after


the feasibility phase is complete and the project is financially viable and
feasible. Requirements specification and analysis identify, analyze, and
model the functionality or “what's” of a prospective software system. The
requirements specification and analysis phase of a software project is the
most important phase of software development and should not be omitted
under any condition.
II. Software design: This stage is designed in a mechanism to transform user
requirements into some suitable form, which helps the programmer in
software coding and development. The process of envisioning and defining
software solutions to one or more sets of problems. One of the main
components of software design is software requirements analysis (SRA).
SRA is a part of the software development process that lists specifications
used in software engineering.
III. Software coding: This stage is usually defined after the designing phase. In
this phase, the developers must implement the software design practically.
Coding is the process of transforming the design of a system into a
computer language format so that software can be created to be sent to the
testing environment.
IV. Software Testing: This stage is the backbone of every software
development project. It doesnt matter which development method you use.
A set of general testing techniques is useful to deploy the software.

4. MoSCoW analysis:

Each letter in MoSCoW represents a separate layer for task prioritization: Must,
Should, Could, Won’t. By organizing tasks into these categories, a team finds clarity
around what it needs to work on right now and soon.
I. The musts include the primary reasons for the client to makeover the change. The
“must-have” category requires the team to complete a mandatory task. If you’re
unsure about whether something belongs in this category
II. The shoulds are things that need to be considered, secondarily after the must
items. They are essential to the product, project, or release, but they are not vital.
If left out, the product or project still functions. However, the initiatives may add
significant value.
III. Coulds are special things to add such as complex tasks make easy by creating a
simple way for the customer. Could-have initiatives are not necessary to the core
function of the product. However, compared with should-have initiatives, they
have a much smaller impact on the outcome if left out.
IV. Won’ts are things that just won't happen, given the overall constraints. The
category can manage expectations about what the team will not include in a
specific release (or another timeframe you’re prioritizing).

5. Timebox:

Task Activities Time No of Milestones


no required(Hrs) resources
1 Requirement to be gathered 2 2 Need to be
collected from
the client

2 Project creations and 3 1 Need to be


planning completed with a
structured
planning

3 Build user interface 20 Team of 5 Need to be


prototypes completed

4 Start the development stage 30 Team of 6 Need to be


completed

5 Testing 23 Team of 4 Need to be


completed

You might also like