Software Design & Architecture

ASSIGNMENT WEEK 9 & 10

NAME: MOHSIN ASLAM

REG NO: F17-BCSE-186.
SECTION: BCSE 6B
Question:
Difference between traditional waterfall software development and Agile
Software Development.

1. e software development process is divided into different phases in the Waterfall model while
Agile methodology segregates the project development lifecycle into sprints
2. Waterfall is a structured software development methodology, and often times can be quite
rigid, whereas the Agile methodology is known for its flexibility
3. According to the Waterfall model, software development is to be completed as one single
project, which is then divided into different phases, with each phase appearing only once during
the SDLC. However, the Agile methodology can be considered as a collection of many different
projects, which are nothing but the iterations of the different phases focusing on improving the
overall software quality with feedbacks from users or the QA team
4. If you want to use the Waterfall model for software development, then you have to be clear
with all the development requirements beforehand as there is no scope of changing the
requirements once the project development starts. The Agile methodology, on the other hand,
is quite flexible, and allows for changes to be made in the project development requirements
even after the initial planning has been completed
5. All the project development phases such as designing, development, testing, etc. are completed
once in the Waterfall model while as part of the Agile methodology, they follow an iterative
development approach. As a result, planning, development, prototyping and other software
development phases can appear more than once during the entire SDLC
6. One of the major differences between Agile and Waterfall development methodology is their
individual approach towards quality and testing. In the Waterfall model, the “Testing” phase
comes after the “Build” phase, but, in the Agile methodology, testing is typically performed
concurrently with programming or at least in the same iteration as programming
7. While Waterfall methodology is an internal process and does not require the participation of
customers, the Agile software development approach focuses on customer satisfaction and
thus, involves the participation of customers throughout the development phase
8. The Waterfall model can be regarded as a stringently sequential process, however, the Agile
methodology is a highly collaborative software development process, thereby leading to better
team input and faster problem solving
9. The Waterfall model is best suited for projects which have clearly defined requirements and in
which change is not expected at all, while Agile development supports a process in which the
requirements are expected to change and evolve. Thus, if you are planning to develop a
software that would require frequent overhauls and has to keep up with the technology
landscape and customer requirements, Agile is the best approach to follow
10. The Waterfall model exhibits a project mindset and lays its focus strictly on the completion of
project development, while Agile introduces a product mindset that focuses on ensuring that
 the developed product satisfies its end customers, and changes itself as the requisites of
customers change

Question

Write a descriptive note on scrum methodology, its advantages & disadvantages

and its step involved in scrum process and tools used in scrum methodology.

What is Scrum Project Management?

Scrum is an agile project management methodology or framework used primarily for software
development projects with the goal of delivering new software capability every 2-4 weeks. It is one of
the approaches that influenced the Agile Manifesto, which articulates a set of values and principles to
guide decisions on how to develop higher-quality software faster.

Who Uses Agile Scrum Methodology?

Scrum is widely used by software development teams. In fact it's the most popular agile methodology.
According to the 12th annual State of Agile report, 70% of software teams use Scrum or a Scrum hybrid.
However, Scrum has spread to other business functions including IT and marketing where there are
projects that must move forward in the presence of complexity and ambiguity. Leadership teams are
also basing their agile management practices on Scrum, often combining it with lean and Kanban
practices (subgroups of agile project management).

What is Scrum in Relation to Agile Project Management?

Scrum is a sub-group of agile:

 Agile is a set of values and principles that describe a group's day-to-day interactions and

activities. Agile itself is not prescriptive or specific.

 The Scrum methodology follows the values and principles of agile, but includes further

definitions and specifications, especially regarding certain software development practices.

 Although developed for agile software development, agile Scrum became the preferred framework for
agile project management in general and is sometimes simply referred to as Scrum project management
or Scrum development.

Advantages of Scrum

Scrum framework is highly perspective. It has specific roles and ceremonies. Scrum has a lot of

advantages, some are listed here.

 Scrum has more transparency and visibility than any other methodology.

 It increases the team accountability.

 Scrum is easy with changes. It accommodates changes.

 Scrum is a cost saving development methodology.

Disadvantages of Scrum

Everything has two faces. When scrum has some benefits then it also has some disadvantages.

Scrum is a methodology for usually high level and experienced persons. Scrum disadvantages

are listed below.

 Scrum need to be experienced and high-level persons, lack of experienced persons scrum

process has some risk of scope creep.

 Scrum team requires experience and commitmented team.

 Less experienced scrum master can ruin the whole process of development.

 If the task is defined poorly then the project can be lead to inaccuracies.
 The Process

The project owner compiles the backlog -- the project requirements, listed by priority. A sprint planning
team goes to work on the top few priority items in the backlog. The team must work within a defined
deadline. Daily meetings allow the Scrum master to track progress and guide the team toward
completion of the sprint. Completion of the sprint results in a deliverable. A review of the completed
sprint precedes work on the next sprint, which will be for the next group of priority items. The process
continues until the team has worked through the entire backlog, or until a depleted budget or a
deadline ends the project.

Scrum Tools

 monday.com
 ProjectManager.com
 Jira
 Targetprocess
 ClickUp
 Vivify Scrum
 MeisterTask
 Axosoft
 Scrumwise
 Quickscrum