Nguyen Bang Vu Supervisor: Pham Thuy Duong September 2018 High level requirements analysis and MoSCoW prioritisation Abstract This document will analyse and discuss an implementation of Agile method of management to the project which is DSDM Atern The report will include a management summary that fully analyse advantages and drawbacks of this method to see if it is appropriate to the scenario in the case study or not Any judgement made from this report will be backed up by evidences from the case study Chapter 1: Consideration for development method in W2L system developing process DSDM Atern Management summary DSDM Atern is one of the Agile methods that focus on the management of the whole project DSDM Atern is different from common Agile methods since it aims for the project life cycle rather than the software development stage It can make sure that the project benefits and solution are clear and feasible The basic concept of DSDM Atern is using timeboxing with iterative and incremental development until the feature reach an acceptable quality There are principles in DSDM Atern which will be discussed in the following sections to justify if the business is able to follow all principle or not because the largest drawback of this method is the strictness in these principles (Some principle might not be discussed if there is not enough associated information in the case study) Focus on Business Need is the first principle which require the customer to understand the true business priorities, establish a business case to establish business goal However, according to the case study, the customers in this scenario which is W2L does not understand high-level requirements and Scott team could not proceed if well defined goals could not be able to made at this stage It is clear that W2L has failed the first principle Deliver on time is the second principle that require the product need to be deliver on time because it can affect the success of the product “The CFO has set a target of getting the ecommerce system up and running within months, and a beta version of the centralised system within the subsequent months.” is a statement from the case study that mention about development time which is still a plan but hopefully W2L could achieve this deadline Collaborate is the third principle that require collaboration to encourages increased understanding, greater speed and shared ownership and get the project finished faster and more effective “However, one plan that the management team put forward – selling their health food and supplements range online to the general public – was not received with much enthusiasm, as the franchise owners felt this could impact their own sales.” from the case study show that there is disagreement between team members in some part of the project In general, there is collaboration in this project but it might not be very effective since there were some objections Never compromise quality is the fourth principle that require the quality of the project need to be agreed in the first place Even though there are discussion from participants in the workshop but the development team is not satisfy with the given requirements because it is not high-level This principle is highly dependant on principle so W2l did not have a solid agreement on quality in the first place The other principles are about development and managing process which are not mentioned in the case study so we assume that the company have the ability to achieve those principles If W2L is able to follow the principles, the advantages they would get are massive With on time development and iterative, incremental development, the project feature will be done in budget the results are constantly delivered to the owner while minimise the risk of misleading Also, the management system which received full support from participants will be effectively developed with users involvement since DSDM encourage interaction between users to deliver accurate results Overall, this method has potential to help W2L to deliver an accurate solution for the business needs About possible drawbacks of this method, it require large business which is not a problem to W2L because it is a large organization at the moment However, the largest problem with W2L to overcome is the failure in identifying high level requirements because this need to be done before the DSDM Atern start to launch Without specific requirements, the above advantages cannot be acquired since this method focus mainly on business requirements The E-commerce system met some obligations between members which can affect collaboration process in this part which may take more time and budget to complete Lastly, there is no alternatives in DSDM because it is restricted in principles which affect the success of the project and DSDM itself is a new concept and it is not common and hard to understand After considering all possible factors of W2L company, I think that W2L is not capable of implementing DSDM Atern because the most important factor needed before and during the development process is high-level requirement is currently not achieved W2l need to come with realistic business goals for this method to start taking place or it may have to consider another development methods which does not take business requirements as the goal ...Abstract This document will analyse and discuss an implementation of Agile method of management to the project which is DSDM Atern The report will include a management summary that fully analyse... clear and feasible The basic concept of DSDM Atern is using timeboxing with iterative and incremental development until the feature reach an acceptable quality There are principles in DSDM Atern... analyse advantages and drawbacks of this method to see if it is appropriate to the scenario in the case study or not Any judgement made from this report will be backed up by evidences from the case