SECTION A
A1 MANAGEMENT SUMMARY OF DSDM ATERN
This management summary is about the problems at Clean Brite Company (CBC) Ltd after buying out their main rival, Scrubaway Allbright Ltd (SAL) and Dynamic Systems Development Method (DSDM) Atern, an agile development method, which has been proposed to management.
DSDM Consortium came up with a standard definition of Rapid Application Development (RAD). The main aim of RAD is quick system development process with the following techniques and tools used to attain the following (Avision & Fitzgerald, 2006, pp. 128 - 129)
• Acceptance that system requirements may change during development process whilst time and budget are fixed.
• User involvement throughout development process to ascertain that …show more content…
A1.2 DISADVANTEGS OF DSDM
The following are the disadvantages related to the case study:
• Requirements drift – DSDM may prove to be burdensome on the developers if there are uncontrolled requirements changes from the users.
• Expensive - DSDM is a costly methodology because it requires both developers and users to be trained to competently use it, this could pose a challenge for CBC because of the dissafication amongst staff. (Patel)
• User perception – DSDM enhances user involvement in the development process but the users may reduce system development to merely interface development.
• Cultural shift – DSDM creates a cultural shift for some users who participate in the development process that they might behave like they are no longer part of the organisations.
Looking at the advantages and disadvantages related to this case study, DSDM would be appropriate for use within CBC because users need to see the software products they want and help early delivery to help in the merger of CBC and …show more content…
If Must have exceed 60% of the total effort, the project will be delivered late and this can lead to over-shooting on the budget. (MoSCoW Prioritisation )
MoSCoW Rules and 80:20 rule
B2.1 HIGH LEVEL REQUIREMENTS PRIORITISATION
Given below are the definitions of MoSCoW (Tudor D & I, 2010, pp. 129 - 130):-
Must Haves – Provide the minimum usable subset of requirements and without these requirements the system will simply not work.
Should Haves – These are very important requirements for the system but can very painfully be omitted due to time constraints and the solution will still be viable.
Could Haves – These requirements enhance the system but are not vital and have less impact if omitted.
Won’t Haves – These are valuable requirements to the system that are out of current scope and the project team have agreed can wait until later.
The key that we shall use is below:-
M = Must Have
S = Should Have
C = Could Have
W = Wont Have for now
High Level Requirements list
1. Monitor customer orders for marketing purposes and statistical analyses. = S
2. Log telesales staff activity to ensure that they are effectively used. = C
3. A facility to compare revenue generated by different sectors. =
A1 MANAGEMENT SUMMARY OF DSDM ATERN
This management summary is about the problems at Clean Brite Company (CBC) Ltd after buying out their main rival, Scrubaway Allbright Ltd (SAL) and Dynamic Systems Development Method (DSDM) Atern, an agile development method, which has been proposed to management.
DSDM Consortium came up with a standard definition of Rapid Application Development (RAD). The main aim of RAD is quick system development process with the following techniques and tools used to attain the following (Avision & Fitzgerald, 2006, pp. 128 - 129)
• Acceptance that system requirements may change during development process whilst time and budget are fixed.
• User involvement throughout development process to ascertain that …show more content…
A1.2 DISADVANTEGS OF DSDM
The following are the disadvantages related to the case study:
• Requirements drift – DSDM may prove to be burdensome on the developers if there are uncontrolled requirements changes from the users.
• Expensive - DSDM is a costly methodology because it requires both developers and users to be trained to competently use it, this could pose a challenge for CBC because of the dissafication amongst staff. (Patel)
• User perception – DSDM enhances user involvement in the development process but the users may reduce system development to merely interface development.
• Cultural shift – DSDM creates a cultural shift for some users who participate in the development process that they might behave like they are no longer part of the organisations.
Looking at the advantages and disadvantages related to this case study, DSDM would be appropriate for use within CBC because users need to see the software products they want and help early delivery to help in the merger of CBC and …show more content…
If Must have exceed 60% of the total effort, the project will be delivered late and this can lead to over-shooting on the budget. (MoSCoW Prioritisation )
MoSCoW Rules and 80:20 rule
B2.1 HIGH LEVEL REQUIREMENTS PRIORITISATION
Given below are the definitions of MoSCoW (Tudor D & I, 2010, pp. 129 - 130):-
Must Haves – Provide the minimum usable subset of requirements and without these requirements the system will simply not work.
Should Haves – These are very important requirements for the system but can very painfully be omitted due to time constraints and the solution will still be viable.
Could Haves – These requirements enhance the system but are not vital and have less impact if omitted.
Won’t Haves – These are valuable requirements to the system that are out of current scope and the project team have agreed can wait until later.
The key that we shall use is below:-
M = Must Have
S = Should Have
C = Could Have
W = Wont Have for now
High Level Requirements list
1. Monitor customer orders for marketing purposes and statistical analyses. = S
2. Log telesales staff activity to ensure that they are effectively used. = C
3. A facility to compare revenue generated by different sectors. =