# data[].attributes.body
Video 1:

SDLC: SDLC or the Software Development Life Cycle is a process that produces software with the highest quality and lowest cost in the shortest time. SDLC includes a detailed plan for how to develop, alter, maintain, and replace a software system.

There are seven phases in software development life cycle (SDLC)

1.     Planning

2.     Requirements/Analysis

3.     Design

4.     Implementation/Coding

5.     Testing

6.     Deployment

7.     Maintenance

Planning: To start of any project, it always has to start with the planning phase, in planning phase everyone agrees with an acceptable requirement and do the necessary changes if necessary.

Requirements/Analysis: Then we go to the Requirement phase where are the necessary steps are analyzed and justified what needs to be done and how the terms and conditions will be fulfilled both for the users and the system itself. After selecting the required documents, the requirement team will analyze and finalize the requirement.

Design: Design team takes all the requirement and starts to design the product. Design phase in concise of business rules, programming language to use, user interface layout, color schemas, frameworks, system-server design, database relationships, application architecture, mobile aspect, supported browsers and so on.

Implementation/Coding: Implementing phase is the phase when actual hands on work for the product starts when the developer team starts writing code and testers do the testing and gives feedback accordingly.

Testing: The work of the tester plays a crucial role in the quality of the software and its performance. Quality analysts use a variety of test case test software. Before the release, the product needs to be verified, including software testing and debugging by testers. When the testing department ensures that the software is error free, it goes to the next stage.

Deployment: Operation teams will end up nearing the staging or developments environment systems that been testing and get them ready for production. After all task is completed, the product will go live to the real users.

Maintenance: Maintain the system and improve the performance of system make it smooth and flexible for the user.

# data[].attributes.body
Video 2: Scrum Agile Development in 3 Steps

Scrum is a simple and effective way to have control over your development process and
ensure development is going according to plan.

Why do we need scrum?
When development first starts, the developer knows how the development will go, but in a few
weeks of development, the development process can become complex. As a result, it becomes
difficult to track the project progress. Delays will result in the project costing more
because payment for additional development time is required. This will displease your clients.

Scrum enables you to keep development transperant, allowing the team to know what is going on
and make adjustments to keep development moving forward.

With scrum, the team builds pieces of the software. This way, the client can experience
each part, and determine what they want next. This will help the team maintain control
over the progress of the project and the power to prevent delays.

The 3 steps are:

1. Create a backlog
A backlog is a list of all features the client wants to have in the complete product.
However, not everything in the backlog will be developed.
The backlog is created by the product owner, who represents the interest of the clients.

2. Prioritizion and Estimation
Prioritization focuses on what brings value to the business, this is done by the product owner,
who sorts the backlog by priority. The product owner picks features that should be in release,
then compiles them in a Release Backlog.

3. Sprint
A sprint is a development unit lasting 3-30 days. A project has several sprints during its
development. Before every sprint, the team will have a sprint planning meeting in which they will discuss
will meet with the product owner to determine what will be done in the next sprint.
During this meeting, the items with the highest priority are selected from the release
backlog. The product owner describes what is desired and the team decides how much of the
desired items can be completed.

The sprint meeting has 2 parts:
1. Spent with product owner to decide which features to develop
2 The team plans out the sprint

The selected tasks are placed into the Sprint Backlog and assigned to the team members.

Everyday, the team members meet for 15 mins for a daily scrum to answer 3 questions:
1. what have you done on this project since the last scrum meeting

2. what do you plan on doing on this project between now and the next scrum

3. what stands in your way to meet your commitments to this sprint and project

the purpose of daily scrum is to synchronize the work of all team members and
address all issues that might delay the work progress

in every sprint, the team must complete the work that was defined for this sprint
the bugs that were related to the features on the sprint backlog should also be fixed as
part of the sprint, at the end of each sprint, a sprint review meeting is held

in this meeting the team presents what was developed during sprint to product owner and
stakeholders

this meetings helps the team decide on what the tea should do next

the client can see the project progress and submit feedback

this prevents the risk of developing features the client didnt ask for

also incase of a delay in the development process, the sprint will not be completed on time,
indicating that there is a problem and something needs to be done

repeat step 3 until all features on the release backlog are developed and product is ready
to be released

# data[].attributes.headline
Differences between Waterfall and scrum agile 

# data[].attributes.subject
Differences between Waterfall and scrum agile 

# data[].attributes.body
The waterfall model emphasizes that a logical progression of steps be taken throughout the software development life cycle (SDLC).

On the other hand, Agile model are all about being collaborative, flexible and adaptive.
And there are some differences between agile and waterfall model:

1- The software development process is divided into different phases in the Waterfall model while Agile methodology divide the tasks into modules to speed up the process.

2- The Waterfall model can be seen as a step-by-step process, however, the Agile methodology is a highly collaborative software development process, therefore it improves to lead to better team input and faster problem solving.

3- 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.

We prefer the Agile model because it provides a good relations between the developers, testers and end-users too. and it could provide better results since the end-user is monitoring the evolution of the software.

# data[].attributes.body
Ng Jing Keong 1151100169
Lee Aik Pheng 1141128118

# data[].attributes.body
7 steps in an waterfall model.

# data[].attributes.body
Software development life cycle (SDLC) contains few steps, which are Planning requirements, requirement analysis, design, implementation, testing,  deployment, and  maintenance.
In planing requirements, all desired requirements are stated and recorded. In second phase, which is requirement analysis, each requirements is analyzed carefully to make things clearer. In Design phase, the application interface and other aspect such as type of language to be used, is stated.
In the fourth phase which is implementation, the program is written out. Tester also shines in this phase. Tester will start to create test plans and start to test some parts of the software. At the next phase which is testing phase, the software should be able to run and tester will test the software thoroughly. They will try their best to find for any bugs and report it to any developer. On the next phase which is the deployment stage, the software will be deployed to the public. And then here comes the last stage, which is the maintenance phase. Any user reported error will be checked and if there is any bugs, developers will correct it.

# data[].attributes.body
Software Development Life Cycle(SDLC), that have 7 key point.

1. Planing:
- Customer and the project manger will out line the requirement of the project.

2. Requirement
- Customer must communicate with IT teams to communicate their requirements for new development and enhancements.

3. Design
-Software design is a major aspect of the software development cycle. The design should be creative and clear. It covers overall product design as well as data structure and database design. Software design uses many different strategies.

4. Implementation/ coding
- Developers begin writing and setting up physical hardware for the server.

5. Testing
-The work of the tester plays a crucial role in the quality of the software and its performance. Quality analysts use a variety of test case test software. Before the release, the product needs to be verified, including software testing and debugging by testers. When the testing department ensures that the software is error free, it goes to the next stage.

6. Deployment
Operation team will eventually be close to the upgrade or development environment system being tested and ready for production. After completing all tasks, the product will go live to the real user.

7. Maintainance
- To maintain the product, to make to run smooth for long time, and fix the problem from user.

# data[].attributes.body
1. Be more responsive

Scrum project management will improve your response times and productivity.

2. Planning and tracking becomes more accurate

When using Scrum, the tasks are split up into “Sprints” and these goals are delivered by project teams

3. Everyone is on the same page

While Scrum uses sprints to break up the overall project into smaller projects, the great thing about this development methodology is that it prioritizes individuals and interactions.

4. Arrange priorities as the project moves on

The best thing about Scrum is that you’re not only able to deal with challenges as they arise - you’re actually expecting changes. The system is set up with the understanding that no project, no matter how big or small, stays 100% true to the original plan.

5. Adjust short-term targets while sticking to overall strategy

Sitting down to plan a large-scale project will result in a clear goal or outcome. Whether it is introducing a new IT system or completely reforming your processes for a specific section of your business, the end goal should reflect what you want from this project

6. Added control

Control is built into the core principles of Agile (Scrum). One of the main requirements of this methodology is to make different parts of the workforce come together on a project

7. Improve your estimates and timescales

One thing that large businesses find difficult is to stick to timescales. Sometimes, the sheer scale of a project can become overwhelming and lead to costly delays and issues. This impacts on your business as a whole and when you are dealing with logistical issues such as time differences across continents, you often find your ability to give customers an accurate picture is hampered.

# data[].attributes.body
Scrum Agile
How does Agile works
A whole software will be planned to be parts, while the product owner is able to experience each of it, thus determine the next step. By applying scrum, the developers may have control over the progress of the project, and ability of preventing delays.

Why do people choose it?
1. It provides a visible environment for everything the team plans to do
2. The flexibility of making adjustments to the project

There are 3 steps of doing scrum:
1.create a backlog
This step will requires end user's requirements about the software.
2. Estimate and prioritize
After gather the requirements, the team will estimate the time and cost of developing the requirements given. When estimation done, the team will make prioritization of the list according to the value it will brings to the company.
3. Sprint
The team will have a spring planning meeting , determining which requirements will be done in one sprint. The requirement will be done will based on the list after having prioritization. The team will have discussion will the product owner, and decide which should be chose for the project.

# data[].attributes.body
learn scrum development in 3 simple steps:
1. Create backlog that need by desired by customer.

2. Eliminate and prioritize:
Eliminate the features that difficult to developed or doesn't bring any value. And prioritize the features that bring most value.

3. Sprint:
- between 3 - 30 days.
- Sprint planning meeting.
- product owner describe what is desired.
- development team decide how much of what desired.

The team planning meeting:
- Spend with the product owner to decided the features.
- The team plan out the sprint.
- Features are assigned to respective members.
- Daily scrums meeting takes 15 minutes daily to get update from all members and address the issues that might delay the project.

# data[].attributes.body
There are 7 different phases in the Waterfall Model . Once the project started there are no phase for change the requirement .Project team only meet with client during requirement ,testing and maintainance team .Tester only can test the software after it is finish .

I prefer agile model because it involve with client along the process .So it would be easier for the team to change the requirement if needed by the client .Furthermore , agile team work faster because the project are managed by the entire team .So , there would be a lot of brainstorming and communication occurs between every department.

# data[].attributes.body
Reasons Scrum is needed in the first place:
1) Unpredictable cases happen during the development phase.
2) Difficulty on keep tracking the progress of the project.

- Scrums is a methodology that keep everything visible. It has a transparent environment which allows the team to know the progress of the project. By doing scrum, you will build the project pieces by pieces, a large project is chunked down into small pieces of tasks. During the development phase, the client can experience each part and communicate with the team on what to do next. This allows more control over the progress of the project.

How to Scrum? 3 Steps.
1) Create a backlog
The project backlog is a list of features that client would like to have as part of the complete product. The backlog is created by the Product Owner.

2) Estimate and Prioritize
After completion of backlog list, the product owner will determine the time required to complete each of the backlog task. Next, the product owner are required to set the prioritization of the features and include the backlog list into the release backlog.

3) Sprint
Sprint are development units that takes between 3 to 30 days. A project usually consist of several sprints.

Each sprint will start with a sprint planning meeting. In the meeting, the product owner and the team will sit down and decide shall be done in the new sprint. The team will choose the features/tasks that has the highest priority from the Release Backlog.

There are two parts of sprint planning meeting, the first part is the product owner decides what tasks shall be done in the new sprint. The second part will involves the team to assign tasks to each team members in the sprint backlog.

During the whole sprint, on every working day the team will hold a short 15 minutes meeting called "Daily Scrum". In this meeting, each team members are required to answers 3 questions. The team members needs to tell what have been done in the previous day, what he's going to work on for today, and what issues he faced while working on the tasks on the previous day.

In every sprint, the team must complete the work that initially planned during the sprint meeting. Bugs that are related to the features also required to be fixed during the sprint.

At the end of each sprint, A sprint review meeting will be held. The purpose of the meeting is that the team will present what have been achieved during the sprint to the product owner. The meeting also helps to decide what the team should do next.

# data[].attributes.body
Agile is an iterative, team-based approach to development. This approach emphasizes the rapid delivery of an application in complete functional components. Rather than creating tasks and schedules, all time is “time-boxed” into phases called “sprints.” Each sprint has a defined duration (usually in weeks) with a running list of deliverables, planned at the start of the sprint. Deliverables are prioritized by business value as determined by the customer. If all planned work for the sprint cannot be completed, work is reprioritized and the information is used for future sprint planning.

While in a Waterfall development project, each of these represents a distinct stage of software development, and each stage generally finishes before the next one can begin. There is also typically a stage gate between each; for example, requirements must be reviewed and approved by the customer before design can begin.

# data[].attributes.body
Why Scrum ? In scrum, everything is visible, allowing all the team members know exactly what is going on. In addition, you have control over the progress of the project which also mean you can prevent delays of the project which cost more time and money.

How to Start ?
1) Create product backlog
- Product backlog is a list of feature that client would like to have in the desired system. However, not all features in the product backlog need to be realized.

2) Time estimation and
Prioritization
- There are different ways to estimate time needed to develop each feature.
- Prioritization refer to the process of sorting the features in a product backlog based on the priority of the feature forming Release Backlog.

3) Sprint
- In the very beginning of every sprint, there will be Sprint Planning Meeting. Where product owner and developer decide what can be done in the new sprint. Product owner will discuss about what is desired in the sprint and developer decide how much can be done on the desired sprint.

- Sprint Planning Meeting has two parts:
a) Meeting with product owner to decide what feature to develop
b) Meeting with team members to plan the sprint. Where the selected tasks are placed in the sprint backlog and assigned to the team members.

- Daily Scrum refers to a short 15 minutes meeting in which everyday the team members meet each other and answer these 3 questions:
a) What have you done on this sprint since last daily scrum meeting ?
b) What do you plan on doing on this project between now and the next scrum meeting ?
c) What stands in your way to meet your commitments to this sprint and this project?
The main purpose of this daily scrum meeting is synchronize the work of all the members and identify problem that might cause the delays.

Step 3 is repeated until all the feature in release backlog  are developed then the project is done.

# data[].attributes.body
Seven key points of SDLC:
1)Planning - Customer and the product owner will outline the requirements of the application. Multiple iterations of SDLC will be running to which new requirements and new features will be added.
2)Requirement Analysis - Developers, product owner and tester will meet up and define each outlined requirement and give more planning details.
3)Design -Takes all the requirement and starts to plan the product. The design phase will include the business rule, the user interface layouts, color schemes, programming languages to use, frameworks, system server design, database relationship, supported device and browsers and much more.
4)Implementation/ Coding - Operation team will setup physical hardware for the servers, developers start coding, designer continue planning the user interface and tester will analyze the requirements and start building test cases for their test plan.
5)Testing - Tester start testing and executing the test cases from the test plans that are created, validate all the requirements that have been met and make sure all the functionality is working as expected and find as many bug as possible for example a user interface bug or the user unable to logout or even register and more. After bug is found, it will be reported to the bug tracking system which is assigned to a developer and they will fix the bug and return it.
6)Deployment - Operation teams will end up nearing the staging or developments environment systems that been testing and get them ready for production. After all task is completed, the product will go live to the real users.
7)Maintainence - Monitor the load and stress coming to the servers so when many users logging in and using it will not bring down the system and decide whether larger server, databases or faster computers are needed. Read the user's complaint issue and get it resolved.

# data[].attributes.headline
1.	The software development process is divided into different phases in the Waterfall model while Agile methodology segregates the project development lifecycle into sprints2.	Waterfall is a structured software development methodology, and often times can be quite rigid, whereas the Agile methodology is known for its flexibility3.	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 team4.	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 completed5.	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 SDLC6.	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 programming7.	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 phase8.	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 solving9.	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 follow10.	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

# data[].attributes.subject
1.	The software development process is divided into different phases in the Waterfall model while Agile methodology segregates the project development lifecycle into sprints2.	Waterfall is a structured software development methodology, and often times can be quite rigid, whereas the Agile methodology is known for its flexibility3.	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 team4.	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 completed5.	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 SDLC6.	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 programming7.	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 phase8.	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 solving9.	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 follow10.	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

# data[].attributes.body
Scrum Agile
Agile needed for:
-Able to keep track the progress
-Client know better what have been done
-Control over project and prevent delay
Step for Agile development
1)Create a Backlog (incl demand features of clients) by product owner.
2) Estimate time to develop each item in list, set priority for features which more important and create Release Backlog.
3)Sprint (between 3 to 30 days).
3.1) Spend with product owner to decide which features to develop
3.2) Developer team plan out the sprint. Daily scrum for 15 min to discuss the progress and what to do next
3.3) Sprint backlog to record the progress and bug stated in backlog have to be fixed
3.4) Sprint meeting held to decide what the team to do next. Client can provide feedback.

Step 3 are repeated until all the features on release backlog are released.

# data[].attributes.body
he agile model is a collection of software developments that is iterative and increment. Firstly, we needed the scrum in the first place because  difficult to keep track of the project progress. Then, this will prevent the project delay, more cost and more time taken. this can also satisfy the client and requirement is met. Our team to know exactly what's going on and make adjustments to the project. When we use the scrum, first step we should create a backlog, it will list all the wish or requirement of the customers. In the Second step. we should estimate and prioritize the requirement. we will estimate the ways or how much the time to complete each feature, and don't want the unnecessary feature. Lastly, we should carry out the sprints, this process will spend a lot of the time. We should spent with the owner to decide which feature to develop and plan the sprint. After complete a feature, we can make a note about it is done in backlog.Repeat the sprint process untill the all feature is done in the backlog. I prefer the agile model because the scrum is simple and effective way in development process, it easy to use.

# data[].attributes.body
AHMED SAAD HUSSEIN HASSAN SAMAHA

# data[].attributes.body
Reasons why Scrum is needed:

To keep track of the project progress

To avoid delays that could cause the project to cost more time and money

To avoid clients from getting upset

Keeps the team updated about what is going on and make adjustments to the project

The client can experience each part

Having control over the project progress and power to prevent delays

Scrum Agile Development (3 Steps):

1. Create a Backlog

list of all features of clients' wishes

created by product owner

2. Estimate and Prioritize

Estimating time needed to develop each item

Sorts backlog items by priority and creates release backlog

3. Sprint

Development units between 3-30 days

Before a Sprint

With Product Owner-

Sprint Planning Meeting is held to decide what will be done in the next Sprint and select highest priority items from release backlog

The team plans out the sprint-

Tasks from the Sprint Backlog are assigned to team members

A short 15 minutes meeting daily called Daily Scrum:

Purpose:

To synchronize work

Address any issues

"What have you done on this project since the last daily scrum meeting?"

"What do you plan on doing on this project between now and the next scrum meeting?"

"What stands in your way to meet your commitments to this sprint and this project?"

After a Sprint

Sprint Review Meeting is held and the team presents what is developed

Decide what to do next

See the project progress

Submit feedback

# data[].attributes.body
Software Development Life Cycle has 7 stages:
1)Requirement Planing - define the requirements of system
2)Requirement Analysis - discuss the outlined requirements in a group of developers and clients. Discuss each requirements then define and add details to the each of the requirements.
3)Design - after gather all the requirements, start to decide which programming languages will be used, the layout of system, user interface, database entities relationship, the architecture of the system
4)Implementation - developer start to code the system program based on the design phase output and system requirements
5)Testing - start to test the system,write test plans and test cases.Finding bugs and errors by testing all possible inputs. Evaluate the output of system in each test cases.
6)Deployment - the product is tested thoroughly and ready to be used by real users and operate.
7)Maintenance -  maintain the system and improve the performance of system for larger user community. Fixing bugs found by users.

# data[].attributes.body
SDLC

7 stages of software development life cycle:
1. Planning:
Customer and the development team will outline and define the requirements for the project.
2. Requirement Analysis:
Discuss each requirements to add details into it. This ensures complete understanding of the requirements proposed by the customer.
3. Design:
Takes all the requirements and proceed to plan to product. This involves selecting which programming languages to use, implementing business rules, layout of the system, database and server design etc.
4. Implementation:
Developer starts to code and setup physical hardware for the servers.

Testers also starts building test cases for the test plan based on the requirements gathered.

5. Testing:
Test the system based on the developed test plan to help find bugs and error, and to validate that the system has met the requirements.
6. Deployment
Operation team will prepare the system for live users and make improvements on hardware if needed eg: servers, deployement of links etc.
7. Maintenance:
Provide long term support for the system to maintain the performance or fixing new issues reported by users.

# data[].attributes.body
There are 7 phases in the software development life cycle which are planing, requirement analysis, design, implementation/coding, testing, deployment and testing.

Steps
1. Customer choose a company to work with
2. He plans the requirements with the company's product owner
3. Define the requirements stated by discussed by customer
4. Product owner will take all defined requirements and put into a project management system as tickets
5. Design phase will discuss UI layouts, color schemes, programming languages used, frameworks, database relationships, etc.
6. Operation team set up hardware for the server
7. Development team will start coding
8. Design team will continue designing the UI
9. Testers will create test cases
10. Testing using test cases that has been created, validate that all requirements has been met, make sure all functions works as expected, find as many bugs as possible
11. If there is a bug, developers will be notified to fix it, then the product is sent back to the testing team
12. Operation team will create servers that are ready for production
13. Add new servers and databases if workload is too much
14. Users may feedback about any bugs they found and developers will have to fix it and deploy product to production again

# data[].attributes.body
Scrum Agile development is all about managing unpredictable requirements changes and makes everything visible for everyone in the development team which allows the team to know exactly what is happening. This could reduce development time and cost by avoiding delays.

-First step is to create a backlog with all the features that the clients wishes to have

-Next is to estimates development for each features and prioritize what brings the most value then transfer the most important to include in the release and transfer them to a release backlog

-Next step is sprint which is 3 to 30 days development units. Begins with sprint planning meeting. development team and client decides what should be included in the release and transfers them to sprint backlog from release backlog and later assigned to each team member. After that daily scrum is held which is a meeting between developers that will answer what has been done, what needs to be done and what are the issues in developing this current sprint. Every member must complete a sprint given to them including bug fixing. At the of a sprint a sprint review is done by presenting work done in the sprint to the client for feedback

Finally repeat sprint until all release backlog features are implemented.

# data[].attributes.body
SDLC has 7 phases which are :-

~ Planning
~ Requirement Analysis
~ Design
~ Implementation
~ Testing
~ Deployment
~ Maintenance

Customer chooses the developer to work with, afterwards the requirements is laid out to the Project Manager/Product owner after which both agrees on to which is to take .Then all the requirement is moved into requirement analysis phase, in which developers and tester meet and define the requirements and planning details. Design phase will take place where the UI, programming languages , hardware requirements are discussed. Operation team will set up hardware for the server, while developer team will do the coding works and design team will design the GUI. Tester will use Test cases to validate requirements, ensure the function works and try to find bug. Developer will be notified in bugs that has been found and it is now their job to fix it. Later on the product will be sent to testers . Operation team will then setup server , and the product will go live. More server and database will be added should there is there be problem such as heavy workload

# data[].attributes.headline
Differences between Waterfall model and Agile model

# data[].attributes.subject
Differences between Waterfall model and Agile model

# data[].attributes.body
The Waterfall model is the traditional approach to software development and long term project planning with single timeline . In Waterfall model , the project team should make sure current phase had completed before proceed to next phase. Customer is typically involved only at the beginning and end of a project in waterfall model.

The Agile model is based on the adaptive software. Agile uses no detailed planning and there is clarity on future tasks only in respect of what features need to be developed. Besides, Agile is also suitable for fixed or changing requirements.

We prefer Agile Model if not handling complex dependencies.

# data[].attributes.headline
Plus, agile is a latest model compare to waterfall. It evolve to adapt the new environment in developers surrounding

# data[].attributes.subject
Plus, agile is a latest model compare to waterfall. It evolve to adapt the new environment in developers surrounding

# data[].attributes.headline
Differences between Waterfall and scrum agile

# data[].attributes.subject
Differences between Waterfall and scrum agile

# data[].attributes.body
In waterfall model, once the development process started, there is no scope of changing the requirement. In agile model, requirement is allowed to change during the development phase even after the initial planning has been completed. In waterfall model, testing is come after the implementation phase. In agile model, testing is typically performed concurrently with implementation. All the project development phases such as designing, development, testing, etc are completed once in waterfall model while as part of the agile model, they follow an iterative development approach.

We prefer use agile development, because it allow the development team to keep tracking the project to make sure the product quality. Other than that, It also help project team to deals with many common project pitfalls such as cost, schedule predictability and scope creep in a more controlled manner.

# data[].attributes.headline
Differences between Agile and Waterfall Model

# data[].attributes.subject
Differences between Agile and Waterfall Model

# data[].attributes.body
The traditional waterfall methodology for software development is rapidly losing its popularity as Agile methodology is now being increasingly adopted by companies worldwide for software development.

Waterfall basically is a sequential model where software development is segregated into a sequence of pre -defined phases – including feasibility, planning, design, build, test, production, and support. On the other hand, Agile development methodology follows a linear sequential approach while providing flexibility for changing project requirements, as they occur.

1.    The 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

# data[].attributes.attachment_link.title
Differences between Waterfall and Agile Model

# data[].attributes.body
Differences between Agile and Waterfall model is Agile follow an iterative development approach because of this planning, development, prototyping and other software development phases may appear more than once while all the project development phases like designing, development, testing, etc. are completed once in the Waterfall model. The Agile Team members are interchangeable, as a result, they work faster. There is also no need for project managers because the projects are managed by the entire team but in the waterfall method, the process is always straightforward so, project manager plays an essential role during every stage of SDLC. We prefer Agile because it is focused client process. So, it makes sure that the client is continuously involved during every stage.

# data[].attributes.headline
Difference between Scrum Agile and Waterfall Model

# data[].attributes.subject
Difference between Scrum Agile and Waterfall Model

# data[].attributes.body
We would prefer Scrum Agile because in scrum agile, there is a lot more communications between the different internal sectors of company. The developmental team as a whole talks and brainstorms together before going ahead and taking any steps, whereas in the waterfall model, every department has their own list of tasks and follows those tasks without any sort of communication outside of their own department. This causes problems because if there is an issue in one department, it isn’t relayed to the other departments which causes a domino effect.

# data[].attributes.headline
Differences between Waterfall and scrum agile 

# data[].attributes.subject
Differences between Waterfall and scrum agile 

# data[].attributes.body
waterfall has 7 phases which each phase  has  to be  completed to  proceed  next  phase. The  project  team  only  interacts with  product  owner  during  requirement, testing  and  maintenance phase. In  scrum, project  team  is  required  to  interact  with  product  owner  throughout  the  entire  development  process. product  owner  can  keep  track  of  the  progress  of  software  development. Scrum  would  be  better  since the complete  time  for  each  feature is  planned. And  priorization  of  features  is  taken which  can  ensure  all  important  features present  when  developing  time  is  a constraint .

# data[].attributes.attachment_link.title
Learn Scrum Agile Development in 3 Simple Steps

# data[].attributes.attachment_link.title
Software Development Lifecycle in 9 minutes!