DSDM Agile Project Development Framework - Coursework Example

DSDM Agile Project Development Framework Introduction The formulation of this report is in light of the system drawbacks facing yourorganization. The Office Supplies and Services Company is experiencing a number of problems with its ordering system. Upon the receipt of the request by the organization, I immediately started the investigation and analysis of the different software development project methodology that will adequately address the issues raised in the organization. My research is extensive and covers a lot of software development methodologies. The report is a reflection of the results of the analysis and evaluation of these methodologies and finally the singling out of the most suitable methodology for use by OSS. The DSDM agile project framework under agile project development is applicable to the situation in OSS. Findings of the Investigation The in-house software development expertise in OSS is not efficient and requires upgrading by use of an appropriate software development methodology The ordering system of OSS is majorly manually operated and needs to be automated to enhance efficiency The process of evaluating and analysing orders from franchisees is complicated for example when classifying orders either as “stock” or “non-stock” The current software development system in OSS does not have appropriate parameters that would lay down a basis for a Test-Driven design. Consequently, defects in the system is causing inefficiency within the organization OSS does not incorporate the ideas of all stakeholders in the execution of duties. The old system is solely run by the organization. Therefore, adequate consideration is not made to the client specification. DSDM Agile Project Framework After coming up with the above findings, the DSDM agile project management framework comes out as the most appropriate for addressing the problems found. Therefore it is first important for the organization to understand what the DSD framework is all about. DSDM is a project development and management framework that bases its operations on prioritization of certain requirements and a limited timeframe (Cantone & Marchesi, 2014, p. 2). Therefore, the important consideration in this case is ensuring that all the necessary requirements for the development project are available. The agile team and other personnel should also ensure that they work within the given timeframe that which means beating the set deadline. Before the commencement of the DSDM process, a feasibility or project practicality study must be conducted. The study involves ensuring that all the requirements are available and that the practicality of the DSDM methodology is guaranteed. In its operation, the DSDM methodology takes into account the requirements that MUST be there, those that SHOULD be there and those that have been ruled out. The classification of the requirements is based the MoSCoW technique. The “must have” requirements are essential for the success of the project and the development cannot take effect in the absence of these requirements. The “should have” requirements are also essential for the development project but the project would still proceed successfully in their absence. Finally, some requirements that are not necessary for the project are ruled out. The DSDM Project Framework Process The Project: Establishing an Online Ordering System for OSS After the analysis and clarification of the DSDM methodology, its practical approach in addressing the concerns in OSS is necessary. The project of establishing an online ordering system for the organization makes use of the DSDM methodology. Prior to the initiation of the software development project, the suitability of DSDM must be assessed. Rationale of Suitability of the DSDM the Situation in OSS OSS requires an efficient ordering system as soon as possible because any form of compromise to the operations that would inconvenience franchisees is undesirable. The DSDM methodology works over a specified timeframe and this ensures avoidance of delays because the personnel strive to beat the set deadline. A guarantee that the operations of OSS will not be suspended for a long time exists. The organization needs a development project that is elaborate and covers all their needs. The DSDM framework outlines all the requirements and classifies them according to urgency and advocates for the inclusion of all the requirements. Therefore, all the needs of the ordering system will be addressed and the coverage of the new ordering system will be comprehensive. Recommendations: How to Acquire the DSDM Methodology for Application Project Development OSS can acquire the Agile Development Methodology, in this case DSDM framework by approaching a relevant agile team. An agile team is the first source of information about agile modeling. The team has a person known as the product owner. Upon approaching reaching an agreement with the organization the team will take charge of representing the interests of OSS and its stakeholders. The work of the product owner revolves around the Disciplined Agile Delivery process outline (Collier, 2012, p.86). Therefore, for any information concerning DSDM methodology, OSS should consult a product owner who in turn develops an agile team. The following are the roles of the product owner: a) The product owner is the central source of information about DSDM methodology. b) Makes and deliberates on information concerning the project development c) Enlightens the agile team on matters to do with application of the DSDM framework in the business world d) Conducts the meetings for modelling the requirements of the project e) Plays a key role in the general modelling of the development project f) Constantly briefs the stakeholders on the status of the development g) Deliberates with the agile team on what requirements to prioritize, among other functions How to introduce the DSDM Methodology into OSS The introduction of the methodology is a process that involves the initiation of the software development project. In the case of OSS, the software to be developed is an online ordering system that is supposed to simplify the transactions between OSS, the franchisees and the suppliers. The implementation of the project comes after the setting up of objectives, analysis of the scope of the project and the identification of the possible difficulties that may arise in the course of the implementation. Identification of the benefits of the DSDM project in place is also vitals. The agile team should inform the managing body of OSS on the resources needed for the project and the responsibilities of the personnel should be clear. Appropriate communication systems should also be set up and the basis of the implementation should be on a relevant project delivery plan (El Sheikh & Alnoukari, 2012, p. 30). Steps involved in Introducing the DSDM Methodology into the Organization Setting up Objectives The following objectives are necessary for the development project: Automation of the ordering system to simplify the work of the workers in OSS thus eliminating the cumbersome system based on manual handling of orders from franchisees. Setting up a platform where the franchisee can easily place their orders and making the retrieval of such orders by the OSS personnel easy. Incorporation of an efficient franchisee support interface that is easily accessible to all the franchisees. Franchisee support ensures that complains and requests for instance when they want to place an additional order. Establishing an appropriate interface for analysing orders placed by customers. This aids in classifying orders and determination of the orders whose payments are still due the ones that are pending payment. Analysis of the Scope or Coverage of the DSDM Project The project aims at setting up a new and efficient ordering system that works on an online basis. Therefore, the proposed system will be making use of internet resources. The project’s scope is simply an outline of what the development project covers. In this case requirements are important to note. Below is a figure that illustrates the scope of the DSDM project (Cobb, 2015, p. 361). (Source: (Strickland, 2011, p. 145) Requirements for Setting up an Online Ordering System Appropriate number of personnel that would implement the project’s objectives. Adequate funding of the project. The provision of financial resources is the responsibility of the managing body of OSS Reliable internet service provision. This necessitates the incorporation of internet service providers into the project development process. Internet resources are vital for setting up online interfaces An efficient communication system to ensure the flow of vital information flows efficiently and consistently Equipment especially computer resources. The operation of the online system would not be possible without computers and the necessary computing knowledge (Tudor, 2010, p. 68) Difficulties that may arise during the Implementation Stage Communication problems. If such problems arise, coordination of activities in the development project will be compromised Lack of active participation of the major stakeholders. Most of the work may be left in the hands of the agile team and other stakeholders may not participate actively in the implementation. The personnel will have difficulties in discharging their duties as a result of the lack of the complementing responsibilities of other stakeholders System failures. The system of operation being used in implementing the project may experience operation difficulties as a result of system defects Failure to beat the deadline. If the project development project encounters a lot of difficulties including the ones stated above, delays will result. Consequently, the operations of OSS may top thus inconveniencing the franchisees. Inadequate expertise in the implementation stage. In the long run, some of the personnel implementing the project may prove to be incompetent. Therefore the productivity of the labour force will be reduced and quality will be compromised Some of the OSS workers may find the integration from the old to the new system difficult. As a result, more time has to be spent in training them to ensure conformity with the new system of placing orders (Moran, 2014, p. 36) Benefits of Applying the DSDM Methodology to the OSS situation The proposed online ordering system will simplify the process of order placement. Franchisees will only have to upload their orders and make follow-ups instead of making unnecessary calls to the organization. The work of analysing orders from clients will be easier because of the automation. Efficiency will in turn improve thus the quality of service delivery will be high The new system will incorporate an online customer support desk that will be receiving calls from clients who have certain concerns. If a franchisee finds it difficult to integrate into the system, the support team will always be there to guide them The improved order placement system will result into a better return on capital for OSS. For instance, efficiency improves the delivery of services hence more sales will be made. The new system will encourage the active participation by all stakeholders. It is necessary for all the stakeholders in the activities of OSS to familiarize themselves with the new system to avoid any inconveniences. The new system will provide a basis for adequately storing organizational information. The current system of storing information is scattered and is unreliable. Therefore, the new system will strive to remedy the current situation (Landry, 2011, p. 47). The Implementation or Delivery Plan During the implementation stage, it is important to ensure that all the requirements are available. Lack of a vital requirement will compromise the feasibility of the proposed project. Remittance of relevant information especially financial information to the management body is important. The information should entail the overall estimated cost of delivering the project successfully. This ensures that the resource requirements are availed in time. Adequate testing of the parameters devised in the project should be done to identify and rectify possible defects that may be in existence (Strickland, 2011, p. 145). The codes of operation should be determined come prior to the implementation of the project. This means that relevant guidance should be given to the agile team and other personnel. Any changes in the protocols that dictate operations should be communicated to the relevant parties in time (Russo, 2010, p. 80). For efficient delivery, the opinions of the OSS employees should be considered. The workers should be given a platform to express what they think should be incorporated into the system. If the system is tailored to meet the specifications of the workers who are going to run it, feasibility is guaranteed. Stakeholder opinions should also be collected from franchisees and suppliers since they play a major role in the operations being run by OSS. The incorporation of the stakeholders ensures the practicality of the project prevails. After meeting all the requirements, the new online ordering system can be integrated into OSS (Carugati & Rossignoli, 2011, p. 91). Bibliography Cantone, G., & Marchesi, M. (2014). Agile processes in software engineering and extreme programming: 15th International Conference, XP 2014, Rome, Italy, May 26-30, 2014. Proceedings. Rome: Springer. Carugati, A., & Rossignoli, C. (2011). Emerging themes in information systems and organization studies. Berlin, Physica-Verlag. Cobb, C. G. (2015). The project managers guide to mastering agile: principles and practices for an adaptive approach. Hoboken: John Wiley & Sons. Collier, K. (2012). Agile analytics: a value-driven approach to business intelligence and data warehousing. Upper Saddle River, NJ, Addison-Wesley. El Sheikh, A. A. R., & Alnoukari, M. (2012). Business intelligence and agile methodologies for knowledge-based organizations: cross-disciplinary applications. Hershey, PA: Business Science Reference. Landry, N. (2011). Iterative & agile implementation methodologies in business intelligence. Raleigh: Lulu Com. Moran, A. (2014). Agile risk management. Cham: Springer Science & Business Media Russo, B. (2010). Agile technologies in open source development. Hershey, PA, Information Science Reference. Strickland, J. (2011). Simulation Conceptual Modeling. Raleigh: Lulu.com Tudor, D. J. (2010). Agile project and service management: delivering IT services using ITIL, PRINCE2 and DSDM Atern. London: TSO. Read More