Running head: QUESTION AND ANSWERS    1
Whyis defining the proper scope for a project so important? What are thedangers a project can face if the scope is not tied down?
Thescope of the project is essential for successful projects. Mostprojects fail due to poor project scope defining the project scopeensures that one knows for certain the deliverables expected at theend of the project. As such, a robust project scope is an essentialarmory that enhances the project success through projected timescale,costs and quality. A good project scope definition entails explainingthe project objectives, desired outcomes, dependencies andconstraints. A poor project scope leads to poor project managementand resource utilization. Project fails due to lack of an effectivescope that is capable of accommodating change.
Commondangers of poor project scope are scope creep in which the projectdeals with extra work obfuscating the main objective. A project mayfail to attract sponsor’s approval when the project scope sidelinessponsor’s change requests. In most cases, project administratorsfail to consider request changes from relevant users, stakeholders orsponsors, and this leads to project failure in garnering requiredsupport for sustainability. In addition, the project scope that isnot well-defined leads to inflated budgets and might extend beyondrequired schedule (Whitten,Lonnie& Dittman,2003). Therefore, before any project activity begins, it isimperative to have a well-defined project scope that covers allaspects of the project resources use, timeframe, activities,deliverables expected and room for in eventualities.
Discussthe approaches used by at least two methodologies to cover the scope,feasibility, and requirements generation portion of the SDLC. Whatare some strengths and weaknesses of each approach?
Thisapproach relies on a step by step strategy in system building movingfrom one development stage to the other in SDLC. In this approach,the customer submits deliverables approval for each phase before thenext phase is started. However, the structured design approach alsohas two distinct approaches used in the covering the scope andfeasibility of SDLC. For instance, within the structured designapproach is process centered strategy that aims at completing workfrom existing processes in the system. The other approach isdata-based strategy that shifts the focus to consumer data use insystem development. In this case the waterfall model and the paralleldevelopment model are used. The waterfall model entails a step bystep approach in software development in a consistent manner from onephase to another in SDLC. The parallel development model, on theother hand, breaks down the entire project into small projects thatare in turn covered separately. This approach strength is that it isrigorous and accomplishes projects in a disciplined manner.Structured design approach is vulnerable to changes as it isdifficult to restart or make changes along the development phase.Furthermore, it takes a long time before expected deliverables arepresented to the users (Whitten,Lonnie& Dittman,2003).
Object-orientedanalysis and design Approach
Thisapproach solves the problem of project scope incompatibility withrising changes. Object-oriented approach breaks down all projectparts in the system in data and processes. Developers in SDLC thusfocus on object parts and distinct processes. The aim is to avoiddata-centric or structured processes in system development. As such,this approach is incremental and iterative new development phasescan be incrementally added to existing SDLC plan (Whitten,Lonnie& Dittman,2003). The object-oriented approach is time-consuming and may lead tocomplexities arising from extra work.
Thereare a number of different software development methodologies. Oneother very popular methodology today is the agile developmentmethodology.Do you think the agile method is better than thewaterfall method?
Thewaterfall and the agile development methodologies are popular in themodern technology development. The waterfall methodology isconsidered a traditional approach that utilizes a ten step strategyin software development where development takes place in phases. Theagile methodology, on the other hand, is considered among theadvanced SDLC tools aimed to adjust and improve the SDLC phases.Nonetheless, the two methodologies are usable and mature technologiesthat have been used to develop software for long. The waterfallmethod utilizes a step by step approach in SDLC process and has beenassociated with the inability to meet the desired SDLC requirementseffectively.
Thewaterfall methods lack sufficient customer specifics requirementdocumentation leading to the development of software that does notmeet clients’ specific needs. In some cases, the waterfall methodis rigid and closed clients cannot see the expected deliverables ormake changes along the way. As such, the agile methodology appears toclose limitation gap. Agile approach breaks down the SDLC processinto functional tasks referred to as ‘sprints’ that have distincttime frame. Customers can see the project development and determinechanges. Unlike the waterfall method, clients in the agile methodhave sense of object ownership and work directly with project teams(Whitten,Lonnie& Dittman,2003). Furthermore, agile method is the best since development isuser-oriented. In this way, considering the project size, customerpreference, market time, level of change integration and complexityfactors agile methods is better in SDLC process.
Whatare some other things you can utilize to increase the chances of asuccessful project?
Thesuccess of SDLC project lies with the project scope. Regardless ofthe type of SDLC project it is important to have a well-definedproject that encompasses the expected deliverables, objectives,timeframe and resources available. As such, it is imperative tobrainstorm adequately with the client and technical experts on allmodalities related to the project before it starts. In SDLC,customers’ needs, requirement and system usability are the maindriving issues in any SDLC system development. For a successfulproject, expansive questioning needs to be done on system needs,feasibility factors and unforeseeable eventualities, all zeroing tosystem design and architecture as per customer’s requirement.However, to achieve these aspects a well-defined development phasesmust be laid down through planning, analyzing, designing andimplementing the decisions on the product development (Whitten,Lonnie& Dittman,2003). Furthermore, it is imperative to balance between competinginterest of clients, limited resources, changing technologies andrisks for a successful project. Nonetheless, effective projectsuccess depends on the following
A well-defined project success criteria
Proper identification of project constraints and drivers
Negotiate and deliberate on achievable deliverables.
Plan and Manage risks
Monitor and evaluate work progress
Learn for the future and have contingency buffers
Have adequate estimation techniques
Conduct regular project retrospective in different phases of SDLC.
Whitten,Jeffrey L., LonnieD. Bentley & KevinC. Dittman. (2003). SystemsAnalysis and Design Methods(6th edition). New York: McGraw-Hill Press.