Running Head: DISCUSSION 1

Discussion Response

Student Name

Tutor’s Name

Date
DISCUSSION 2

Response 1

Agile methodology in SDLC is a blend of two distinct viewpoints. SDLC is a phrase

used mainly in waterfall to designate the process to move from requirements, via design,

development testing as well as then release (Brown & Mistrik, 2017). Using an agile

methodology or more importantly a mix of agile techniques, requirements, design, development,

testing and deployment are all worked together as a team using single piece flow to maximize

throughput and quality.

In agile, it is better to get one thing to a definition of done (The Definition of Done -

Manifesto) vs. getting many things started in work in progress. Many people incorrectly think

mini-waterfall is an agile methodology (Gerry Claps). By breaking up a unit of work into

smaller pieces, it does reduce risk. Yet, agile includes having multiple perspectives of a cross

functional team approaching the highest value item and delivering an increment of work to a

definition of done every iteration.

Response 2

Agile refers to is fast moving. This application development technique depends on

iterative as well as gradual model of programming advancement. There were sure standards on

which the coordinated model was to be based (Leffingwell, 2016). The most significant of the

standards is customer devotion by providing quick and nonstop delivery of small and valuable

software. Product development occurs at normal interludes instead of several months, which is

the case with the cascade model.

There is a ton of allowance for contribution between the agents as well as developers, as

the prerequisites proceeds arising from the businessmen at customary interludes. There is a lot of

emphasis placed on specific greatness and great structure of the software. The product
DISCUSSION 3

advancement group needs to amend normally to the evolving conditions. Agile modeling is an

approach, which utilizes exercise for representing and recording of software based systems.

Conventional modeling techniques in software development ventures have provided path to these

practices which are applied in an increasingly adaptable way.

DISCUSSION 4

Reference

Babar, Brown & Mistrik. (2017). Agile Software Architecture: Aligning Agile Processes and

Software Architectures. London, England: Newnes.

Leffingwell. (2016). Agile Software Requirements: Lean Requirements Practices for Teams,

Programs, and the Enterprise. Addison-Wesley Professional.