The presentation covers one of the Agile Methodologies. Dynamic Systems Development Method (DSDM) is a framework based originally around Rapid Application Development (RAD).DSDM recognises that projects are limited by time and resources, and plans accordingly to meet the business needs.

1. Presented by
Meark Enterprise Private Limited
 Consulting, IT Products and Services organization
established in Feb 2016.
 ISO 9001 (Quality) and ISO 27001 (Information Security)
certified organization
Meark’s Vision
To provide significant value to our clients by
architecting optimized processes and systems
for efficient business functioning.
Sectors
 Agriculture
 Education and Skilling
 Public sector
 Retail
 Banking
 Insurance
 Healthcare
 Manufacturing
Our Focus
Solutions devoted to users not technologies.

2. Nithya Subramaniam
Managing Director
Meark Enterprise Private Limited
How Meark as an Enterprise Leverages DSDM?
Nithya has more than 16 years of experience and is a recognized expert in the software
business analysis and architecture field .
She currently leads the Exploration and Engineering teams of Meark to deliver Consulting, IT
Services and Products enabling clients to do business better by technology and process
changes.
Her earlier roles include
Consultant and Senior Manager for Innovations, Campus Management Corp.
Product Manager, NEC India
Practice manager for Higher Education Sector , Wipro
Multiple business analysis engagements in the retail sector, Wipro

3. How Meark as an
Enterprise Leverages
DSDM?
© Meark Enterprise Private Limited Document Classification: Restricted Sharing Organizers and Participants

4. Presented by
Agenda
Why DSDM?
Better Visibility
Freedom to Choose
Structured Reviews, No Surprises!
Performance
Concise Communication
Going Forward
© Meark Enterprise Private Limited Document Classification: Restricted Sharing Organizers and Participants

5. Why DSDM?

6. Presented by
Our Challenges
One
Hero
Analysis
Paralysis
Priority
Anchor
The right delivery
guy
Over-engineering Director
The Expert of Options
Safe
Commitmen
t Owner

7. Presented by
Why DSDM Framework?
Start-up
Model to follow
One ofAgile
And a proven model
Gain Compliance
For ISO and CMMI Standards
Easy to Communicate
Less documentation
Focus on Output
DSDM
(1994)
Iterative and Incremental
To provide more discipline to the
rapid application development .
IT and Non-IT Projects
Agile Manifesto
(2001)
Individuals and interactions
over processes and tools
Working software
over comprehensive documentation
Customer collaboration
over contract negotiation
Responding to change
over following a plan

8. Presented by
What is Dynamic Systems Development Method(DSDM)
Focus on the business need
Deliver on time
Collaborate
Never compromise quality
Build incrementally from firm foundations
Develop iteratively
Communicate continuously and clearly
Demonstrate control
Principles
Prioritisation Technique – MoSCoW
Must Have
60%
Should Have
20%
Could Have
20 %
Won’t Have
Timebox Plan
Iterative 4 Week
Sprints
Terms of
Reference
Benefit Assessment
8
6
Phases

9. Evolutionary Development : Exploration+ Engineering Sprints
Team Structure

10. Presented by
DSDM Timebox
A DSDM structured timebox
A free format timebox

11. Better Visibility

12. Presented by
Exploration to Engineering Execution
Prioritised Requirements List - Storyboard

13. Presented by
Traceability to User Guide

14. Presented by
Better Visibility
Missed components and priorities due to
definition misses.
[ One board]
Missed components and priorities due to
definition misses.
[ One board]
Better visibility for planning.
[Two boards – Exploration and Engineering]
Better visibility for planning.
[Two boards – Exploration and Engineering]
PC
Project Co-ordinator Before
Before After
After

15. Freedom to Choose within the boundary

16. Presented by
Engineering then Exploration Sprints

17. Presented by
DSDM - Prioritisation Technique
Prioritisation Technique – MoSCoW
Must Have
- 60%
Should
have - 20%
Could have
- 20 %
Won’t
have

18. Presented by
Freedom to Choose within the boundary
Project Co-ordinator
1. Team’s identify component’s to built
1. Team’s identify component’s to built
1. Mark identified sprint components they
choose to do for the day
1. Mark identified sprint components they
choose to do for the day
Before
Before After
After

19. Structured Reviews, No Surprises!

20. Meark – Exploration Sprint
Sprint
Exploration Output Responsible Reviewer Output Responsible Reviewer
Week 1 UI Story(PRL) and
Wireframes
SAT Meeting PA, Email
TA
_ _ _
UI Draft UI SAT, TL _ _ _
UI Refinement UI, SAT Meeting PA, Email
TA
DB Design TL/TA TL/TA
UI Optimization UI, SAT Meeting PA, TA DB Review TL/TA PA
Week 4 MoSCoW,
Timeboxplan*
PC, PA EmailTA,
Developer,TL
SRS Document SAT PA
Engineering Output Responsible Reviewer Output Responsible Reviewer
Week1 Code with UI DEV, TL Prepare Test cases
and Test Data
SAT PA
Code with
SRS Document
DEV, TL _ _ _
Release emailfor testing DEV, TL, SAT _ _ _
Bug Fixing DEV, TL SAT Daily Buglist SAT DEV,TL
Release emailfor testing DEV, TL, SAT _ Test Report
Draft User Guide
SAT _
Retrospective Meeting,
Next Sprint planning
PC,ALL _ Timeboxreview
record*/Project
ReviewReport*
SAT,PC _
Output Responsible Reviewer Output Responsible Reviewer
Assemble Review
Deploy to UAT
TL,TA TA User Guide SAT PA
Deploy to Prod/Demo TL,TA TA End User Training SAT, PA _
Output Responsible Reviewer Output Responsible Reviewer
Business Case,
Priortized Requirements
List
PA _ Solution
Architecture
Definition
PA,TA PC
DeliveryPlan,
Management Approach
Definition
PC TA,PA Development
Approach Definition
TA PC
Legend
Reference for further reading: https://www.agilebusiness.org/
Feasibility Phase
Foundations Phase
Project Closure
Meark - Dynamic Systems Development Method(DSDM) - SDLC
Version 5.0
* represents Milestone
Products
SAT- Solution Analyst and Tester
UI-UI Developer
TL- Team Lead
DEV-Developer
PC- Project Co-ordinator
PA- Process Architect
TA- TechnicalArchitect
Pre-Project Phase Terms of Reference*
Feasibility Assessment (PC)*
Foundation Summary(PC)*
Deployment Phase
Week4
Week2,3
Code Review per
component by
TL/Dev
Weekly Code
Optimization by
TA
Post - Project Phase Benefits Assessment
DSDM Evolutionary Products (Optional)
Week4
Week 2,3
Evolutionary Development Phase - Exploration + Engineering
Draft
Refinement
Optimization
Exploration States
Sprint
Exploration Output Responsible Reviewer Output Responsible Reviewer
Week 1 UI Story (PRL) and
Wireframes
SAT Meeting PA, Email
TA
_ _ _
UI Draft UI SAT, TL _ _ _
UI Refinement UI, SAT Meeting PA, Email
TA
DB Design TL/TA TL/TA
UI Optimization UI, SAT Meeting PA, TA DB Review TL/TA PA
Week 4 MoSCoWComponent
List , Timeboxplan*
PC, PA, TA TL, SAT Validations,
Notiifcations, SRS
Document
SAT PA
Week 2,3
Evolutionary Development Phase - Exploration + Engineering

21. Presented by
Sample Tracking

22. Presented by
100+Components – Validation List is at One place

23. Presented by
Structured Reviews, Yet in any Order!
1. UI multiple-changes as Issue
2. Developers work on changing UI
1. UI multiple-changes as Issue
2. Developers work on changing UI
1. UI in Exploration Sprint
2. 3 level UI reviews yield best possible
design
3. Validations upfront
1. UI in Exploration Sprint
2. 3 level UI reviews yield best possible
design
3. Validations upfront
Before
Before After
After
PA
SAT
UI

24. Meark – Engineering Sprint
Sprint
Exploration Output Responsible Reviewer Output Responsible Reviewer
Week 1 UI Story(PRL) and
Wireframes
SAT Meeting PA, Email
TA
_ _ _
UI Draft UI SAT, TL _ _ _
UI Refinement UI, SAT Meeting PA, Email
TA
DB Design TL/TA TL/TA
UI Optimization UI, SAT Meeting PA, TA DB Review TL/TA PA
Week 4 MoSCoW,
Timeboxplan*
PC, PA EmailTA,
Developer,TL
SRS Document SAT PA
Engineering Output Responsible Reviewer Output Responsible Reviewer
Week1 Code with UI DEV, TL Prepare Test cases
and Test Data
SAT PA
Code with
SRS Document
DEV, TL _ _ _
Release emailfor testing DEV, TL, SAT _ _ _
Bug Fixing DEV, TL SAT Daily Buglist SAT DEV,TL
Release emailfor testing DEV, TL, SAT _ Test Report
Draft User Guide
SAT _
Retrospective Meeting,
Next Sprint planning
PC,ALL _ Timeboxreview
record*/Project
ReviewReport*
SAT,PC _
Output Responsible Reviewer Output Responsible Reviewer
Assemble Review
Deploy to UAT
TL,TA TA User Guide SAT PA
Deploy to Prod/Demo TL,TA TA End User Training SAT, PA _
Output Responsible Reviewer Output Responsible Reviewer
Business Case,
Priortized Requirements
List
PA _ Solution
Architecture
Definition
PA,TA PC
DeliveryPlan,
Management Approach
Definition
PC TA,PA Development
Approach Definition
TA PC
Legend
Reference for further reading: https://www.agilebusiness.org/
Feasibility Phase
Foundations Phase
Project Closure
Meark - Dynamic Systems Development Method(DSDM) - SDLC
Version 5.0
* represents Milestone
Products
SAT- Solution Analyst and Tester
UI-UI Developer
TL- Team Lead
DEV-Developer
PC- Project Co-ordinator
PA- Process Architect
TA- TechnicalArchitect
Pre-Project Phase Terms of Reference*
Feasibility Assessment (PC)*
Foundation Summary(PC)*
Deployment Phase
Week4
Week2,3
Code Review per
component by
TL/Dev
Weekly Code
Optimization by
TA
Post - Project Phase Benefits Assessment
DSDM Evolutionary Products (Optional)
Week4
Week 2,3
Evolutionary Development Phase - Exploration + Engineering
Code
Review
Release
Engineering Output Responsible Reviewer Output Responsible Reviewer
Week 1 Code with UI DEV, TL Prepare Test cases
and Test Data
SAT PA
Code with
SRS Document
DEV, TL _ _ _
Release emailfor testing DEV, TL, SAT _ _ _
Bug Fixing DEV, TL SAT Daily Bug list SAT DEV,TL
Release emailfor testing DEV, TL, SAT _ Test Report
Draft User Guide
SAT _
Retrospective Meeting,
Next Sprint planning
PC,ALL _ Timeboxreview
record*/Project
ReviewReport*
SAT,PC _
Week 4
Week 2,3
Code Reviewper
component by
TL/Dev
Weekly Code
Optimization by
TA
Engineering States

25. Presented by
Structured Reviews, Yet in any Order!
1. Daily Dependency on Architect in
Development
1. Daily Dependency on Architect in
Development
Only reviews and logic complexity requires
intervention of technical architect.
Only reviews and logic complexity requires
intervention of technical architect.
Before
Before After
After
TA
TL, DEV

26. Presented by
Meark -Sample Monthly Sprint Planner and Tracker
Sprint Items Responsible Duratio
n
in Hrs
Planned
Work
Dates
Responsible
Person
Completion
Status
Overall
Status
Tester
Confirmatio
n
Technical
Review
and
Dependency
Functional
Review
and
Dependency
Organization Registration Public Page -
Resolving Duplicate Registration Issue CR -
SCR -USR- ORS-014
Dev A 4 7 Completed Completed Completed NA Completed
Manage GST and Fee – SCR -USR- ORS-012 Dev A 6 7 Completed Open Completed Completed Completed
Manage Subscription – SCR-VMS–SUB -002
Dev B
24
Open Open Completed Completed Completed
View Subscription Packs – Public page -
SCR-VMS–SUB -002 Dev A 24 15,22,29
Completed Open Completed Completed Completed
Payment Registration and Integration for
Sports 2.
with Receipt Generation Dev C 8 8,15,22,1
Open Open
Pending Completed Completed
Website update – Inclusion of New content
page SCR-WES–POR -034 Dev C 4 22 Completed Completed NA NA Completed
Available duration for Sprint
in hours starting 1st Dec
160

27. Performance

28. Presented by
DSDM Principals

29. Presented by
Meark – Performance - Sample View of a Month
SN Key Performance
Areas (KPA)
Key Performance Indicator (KPI) Max
Score
Associate
Score
Associate
Score
Associate
Score
Associate
Score
Associate
Score
Sprint PerformanceProject Team Performance as determined by Quality of Sprint Deliverables
or Opportunities created/capitalized.
50 30 49.5 30 42 49.5
1Deliver on Time 1a. Focus on business priorities. Guarantee Minimum Usable Subset.
1b.Always hit deadlines. Ability to stretch when work is incomplete/ required for business by self or as requested.
2a. For Dev and SAT: Occurrences of missing requirements as identified in testing/review. Pro-active scheduling of
Review/UAT with Manger/customer and ensuring sign-off.
Zero delays.
10 6 10 5 9 10
2Never Compromise
Quality
1. Adherence to provided formats for Email Signature, Release emails.
For Developer: Code Conventions, Quality of code as identified in review by TL/TA.
For SAT : Quality of requirement and test document with coverage of scenarios, as reviewed by PA/PM/Client.
2. For Developer: Defects/unresolved issue re-opened by tester and manager.
For SAT: Defect identified by manger/customer post system release.
10 8 10 8 8 9.5
3Embrace Change,
Experiment and
Learn
1a. Instances of Exploration and Implementation of new UI pattern/Technology component/ New Applications/
Application Improvements.
1b. Accept change positively and handle changing workloads in response to changing circumstances.
2a. Learning sessions participated at least 6 hrs.
2b. Learning conducted/showcased at least 1, min of 30 mins. Willingness to learn new skills, attend self-improvement
training.
10 5 9.5 6 8 10
4Collaborate,
Communicate
Continuously
and Clearly
1a. Participation is delayed/absent in meetings/ Sprint sessions.
1b. Pro-active scheduling of required reviews/meetings. Pro-active transparent communication of a) change in time, in
case of delay, b) change in task from what is planned on daily/given task. Number of times follow-up email where
received.
2a. Daily update in Kanban and email without follow-up. Appropriate Response for query post in email within 30 mins
during work hours. Clear and independent communication without grammatical errors. When Associate/Manager is not
available for immediate clarification for doubt, has mail been sent out immediately.
For SAT includes: Presence in project kick-off call with TA.
2b. Early communication of leave request, permission requirement. Maximum of 2 permission per month.
10 7 10 7 8 10
5Initiatives Initiatives as recognized by the Manager 10 8 10 8 9 10
Total 100 64 99 64 84 99

30. Presented by
Team Performance Ratings – In Sprint too!
1. 6 months feedback meetings on 10
competencies
2. Yearly appraisals
1. 6 months feedback meetings on 10
competencies
2. Yearly appraisals
1. Monthly Feedback Emails and Awards
2. Rated based on 5 points by PA/TA
3. Yearly appraisals
1. Monthly Feedback Emails and Awards
2. Rated based on 5 points by PA/TA
3. Yearly appraisals
Before
Before After
After
Team

31. Concise Communication

32. Presented by
DSDM – Detailed in 2 Pages
Our workplan
and output for
each week of the
month sprint and
increment
RACI Matrix
For each output
Responsible, Accountable,
Consulted, Informed

33. Output Responsible Reviewer Output Responsible Reviewer
Wireframes SAT Meeting PA, Email
TA
_ _ _
UI Draft UI SAT, TL _ _ _
UI Refinement UI, SAT Meeting PA, Email
TA
DB Design TL/TA TL/TA
UI Optimization UI, SAT Meeting PA,Email
TA
DB Review TL/TA PA
MoSCoW,
Timeboxplan*
SAT,PA EmailTA,
Developer,TL
_ _ _
Sprint In Output Responsible Reviewer Output Responsible Reviewer
Week 1 Code with UI DEV, TL SRS Document SAT PA
Code with
SRS Document
DEV, TL Prepare Test cases
and Test Data
SAT PA
Release emailfor testing DEV, TL, SAT _ _ _
Bug Fixing DEV, TL SAT Daily Bug list SAT DEV,TL
Release emailfor testing DEV, TL, SAT _ Test Report
Draft User Guide
SAT _
Retrospective Meeting,
Next Sprint planning
PC,ALL _ Timeboxreview
record*/Project
ReviewReport*
SAT,PC _
Output Responsible Reviewer Output Responsible Reviewer
Assemble Review
Deploy to UAT
TL,TA TA User Guide SAT PA
Deploy to Prod/Demo TL,TA TA End User Training SAT, PA _
Output Responsible Reviewer Output Responsible Reviewer
Business Case,
Priortized Requirements
List
PA _ Solution
Architecture
Definition
PA,TA PC
Delivery Plan,
Management Approach
Definition
PC TA,PA Development
Approach Definition
TA PC
Evolutionary Development Phase
User Interface
Post - Project Phase Benefits Assessment*
DSDM Evolutionary Products (Optional)
Week 4
Feasibility Phase
Foundations Phase
Project Closure
Meark - Dynamic Systems Development Method(DSDM) - SDLC
Version 4.0
Pre-Project Phase Terms of Reference*
Feasibility Assessment (PC)*
Foundation Summary (PC)*
Deployment Phase
Week 4
Week 2,3
Code Reviewper
component by
TL/Dev
Weekly Code
Database
SN DSDM Phase Project Activities PC PA TA SAT UI TL/DEV
1 Pre-Project Phase Terms of Reference* I RA C I - -
2 Feasibility Phase Feasibility Assessment (PC)* RA C C C - -
3 Foundation Summary Foundation Summary (PC)* RA RA C C - -
4 Foundation Summary Provide Functional requirements I RA I C - -
5 Foundation Summary Delivery Plan RA C C C - -
6 Evolutionary Development Phase UI - Wireframes I A C R - -
7 Evolutionary Development Phase UI - Draft I I I AC R -
8 Evolutionary Development Phase UI- Refinement I C C AC R -
9 Evolutionary Development Phase UI - Optimization I C C AC R -
10 Evolutionary Development Phase DB Design I C RA C - -
11 Evolutionary Development Phase DB Review I C RA C - -
12 Evolutionary Development Phase Provide Component IDs (Screens/Reports/APIs) I C I RA - -
13 Evolutionary Development Phase SRS Document I C I RA - -
14 Evolutionary Development Phase Review SRS I RA I C - -
15 Evolutionary Development Phase Write SRS Requirements with DB Table names I I C RA - -
16 Evolutionary Development Phase Write Scripting in Json templates (if required) I I C RA - I
17 Evolutionary Development Phase Identify TL/DEV, Plan Sprint,MoSCoW,Timebox plan* RA C C C I I
18 Evolutionary Development Phase Team Specific Sprint Meetings and daily progress update RA C C C I I
19 Evolutionary Development Phase Provide KT to Developer I C I RA - I
20 Evolutionary Development Phase Dev Kickoff call I - RA C - C
21 Evolutionary Development Phase Prepare Test cases and Test Data I C I RA - -
22 Evolutionary Development Phase Code with UI I C C C C RA
23 Evolutionary Development Phase Code with SRS Document and Unit Test I C C C C RA
24 Evolutionary Development Phase Provide Functional clarification to developers I C C RA C I
25 Evolutionary Development Phase Provide Technical clarification to developers I - RA C C C
26 Evolutionary Development Phase Review development progress in Daily Sprint calls RA I I C - C
27 Evolutionary Development Phase Release Multiple Cycles - Release Email I I C I - RA
28 Evolutionary Development Phase Test Multiple Cycles -Smoke Test Accept/Reject, Daily Bug list I I I RA - C
29 Evolutionary Development Phase End of Sprint - Retrospective Meeting, Next Sprint planning RA C C C C C
30 Evolutionary Development Phase Timebox Review Record* C C RA I I I
30 Deployment Phase Project Review Report* RA C I I I I
31 Deployment Phase Assemble Review Deploy to UAT I I C I - RA
32 Deployment Phase User Guide I C I RA - C
33 Deployment Phase Conduct UAT and get Sign-off I C I RA - -
34 Deployment Phase End User Training I C I RA - -
35 Deployment Phase Deploy to Prod I I C I - RA
36 Post - Project Phase Benefits Assessment* C RA I C - -
37 Any Phase- Evolutionary Products Business Case, Priortized Requirements List I RA C C - -
38 Any Phase- Evolutionary Products Delivery Plan, Management Approach Definition RA C C C - -
39 Any Phase- Evolutionary Products Solution Architecture Definition C A R I - -
40 Any Phase- Evolutionary Products Development Approach Definition C C RA I - -
Legend:
* represents Milestone products
Responsible Those who do the work to complete the task
Accountable One ultimately answerable for correctness and completion
Consulted Those whose opinions are sought
Informed Those who are kept up-to-date on progress
DSDM RACI Matrix
Version 4.0
RACI

34. Going Forward

35. Going Forward
1. Attempt better Sprint Cycles for UI teams
2. Sprint Progress Based Morning Reports

36. What we do at Meark

37. Presented by
Meark Products
Visitark Stark Inspectark
Inspection Management
Spark
Devark
Sector
Specific
Sector
Agnostic
Skillar
Skill and Placements for
Skilling Sector
Agriark
Agriculture Produce
Aggregator
Visitor Management Guest Houses and Halls
Management
Alumni and Placement
for Education Sector
Event Management for
Education Sector

38. Presented by
Meark Services
Integration with
Enterprise and National
systems
Robotic Process
Automation
Reporting and Analytics
Mobile Apps in
Cordova / PWA
Website Development
Application Design &
Development

39. Our Clients and End Clients/ Users of Meark
Now Anthology
Talisma Corporation Pvt. Ltd
TNSDC
CET Maharashtra Directorate of
Technical Education,
Chhattisgarh
 Development partners Indian Center for Social Transformation, Tech Mahindra.
 Interfaces with IMD, ISRO, ICAR, DACFW, NWIC, CGWB
 End users Farmers, Farm Suppliers and Buyers

40. Ability to see vehicles on the Maps with statuses and geocoding
Vehicle Tracking
RFID based Bin Tracking -
Pharmacy Distribution Company