Why Blue Bank needs to go for Agile Methodology, this focuses client

process. So, it makes sure that the client is continuously involved during every
stage.

The terms of Agile are extremely motivated and self-organized in compare to

Agile software development for Blue Bank method will assure that quality of
the development is maintained and the process will completely based on the
incremental progress. Therefore, the client and team know exactly what is
complete and what is not. This reduces risk in the development process.

This includes various methodologies in itself. Agile methodologies like Scrum, FDD, etc. are
all part of the agile manifesto and these will help Blue Bank to develop, agile methodology is
often compared with the waterfall model in the software development industry. However,
approach of agile is considered to be better.
This will have the incremental approach where a sample prototype for Website/Mobile
application is properly discussed with the customer. The prototype helps in understanding
the key aspects, including the requirements/ possible challenges / user needs / training
modules etc. The consecutive prototypes reflect the changes done in the previous
prototypes. This loop will happen till the customer is satisfied, providing better end-product
to the customer. The idea is to maintain product’s quality in the entire phase of
development.
While comparing the Waterfall model and the agile methodology, we can conclude that:

Each phase is a result of the process of previous steps

The process should be repeatedly checked for consistency

A single iteration would not give a clear picture of the process.

What things will have to change on how this team operates and how key stakeholders interact or
engage on this project? (Hint: as you have learned, for agile to be successful there are certain
prerequisites and it poses certain challenges for leadership/business stakeholders as well)

Blue Bank has always used the traditional waterfall method to deliver IT projects. Harold
Johnson and the company leadership have suggested that you also use traditional methods to
build the software. You have a different idea. You think agile would be better for this situation.In
the space below, make a case to Harold as to why we should switch to agile (explain why using
agile is a better choice for this project/situation). Be sure tosupport your argument by referring
back to the case study text.lue Bank has always used the traditional waterfall method to deliver
IT projects. Harold Johnson and the company leadership have suggested that you also use
traditional methods to build the software. You have a different idea. You think agile would be
better for this situation.In the space below, make a case to Harold as to why we should switch to
agile (explain why using agile is a better choice for this project/situation). Be sure tosupport your
argument by referring back to the case study text.Our main agenda is to develop an mobile
application that is customer-friendly and while keeping in mind the project estimates. Blue bank
has always been using traditional methods like waterfall because it is easy to manage due to
rigidity andat each phase has specific deliverables and a review process. Phases are processed
and completed one at a time. The main problem with this model is its inability to make changes
after the process is halfway through and dependency on the phase as you cannot move to the next
phase before completing the current phase. In this case, it is better to switch to agile because we
are digitalizing all our checks tobe deposited. The benefit of agile over waterfall is the ability to
change dynamically to the customer's wants and needs. A focus on the features that are
thehighest value to the customer. A short-fixed timeline that allows for immediate feedback from
the customer and the ability to move deliverables into production. Soour new service could be
stable, secure, and ease to use. This also assures the loss of younger customers to much quality
and customer service is the key. Agile works well with small dedicated team members and lets
the team load balance workloads. We currently have 4 developers, 2 testers who can easily
utilize the process without any work pressure. So I request Harold to consider these points
andswitch to agile.Assume Harold liked your argument and agreed to proceed with agile on this
project. In his reply, Harold asked for further guidance on how to move forward. Please reply
back with the following:What things will have to change on how this team operates and how key
stakeholders interact or engage on this project. (Hint: as you have learned, for agile to be
successful there are certain prerequisites and it poses certain challenges for leadership/business
stakeholders as well)The team is new to Agile and based on prerequisites for agile to be
successful, please specify if you and your team need any help or training etc. If none, please state
that.As of my knowledge, our team members have some experience in web development but
none in mobile development. Nobody on team has performance testing experience or User
experience expertise. People with an open mindset are the only key pre-requisite for the
successful implementation of an Agile method. In fact, I would not suggest that you add too
many tools to a team that is not used to them. Instead, if the team has the open mindset and the
requisite attitude then train and start them on an Agile method. Any Agile method will do -
Kanban, XP, Scrum. Most of the developers and testers have offices on different floors of the
building and generally work in their office. Since the team is scattered then some amount of
technology needs to be taken upfront. The most important aspects of good agile project
management is judgement and responding to change. With judgement, I mean the ability to see
risks(good perception and listening skills) before they become issues and coming up withgood
strategies to mitigate these risks. Having the courage to accept that you do not have all answers
are a prerequisite for Agile to be successful. If everyone just applies common sense in thinking
value of incremental change the right tools will automatically get commissioned on the way. Our
Business stakeholders who wrotethe high level vision for the mobile application are going to
help refine or define

1. Some things to change to

Why Agile?
 Agile Methodologies have overcome the traditional methods of waterfall model by
becoming flexible, fast, lean, responsive, and consistent.
 Agile method focuses on people and is more communication-oriented
 Agile methods are tested in a dynamic environment and prove to be very flexible by
adapting to the change happening in the business.
 Agile methods include regular inspection in a disciplined manner, which
consequently improves the leadership qualities to boost the teamwork.
 Agile method follows best practices that help in getting high-quality software very
quickly.

Blue Bank has always used the traditional waterfall method to deliver IT projects. Harold
Johnson and the company leadership have suggested that you also use traditional methods
to build the software. You have a different idea. You think agile would be better for this
situation.In the space below, make a case to Harold as to why we should switch to agile
(explain why using agile is a better choice for this project/situation). Be sure to support
your argument by referring back to the case study text.lue Bank has always used the
traditional waterfall method to deliver IT projects. Harold Johnson and the company
leadership have suggested that you also use traditional methods to build the software.
You have a different idea. You think agile would be better for this situation. In the space
below, make a case to Harold as to why we should switch to agile (explain why using
agile is a better choice for this project/situation). Be sure to support your argument by
referring back to the case study text.

Our main agenda is to develop a mobile application that is customer-friendly and while
keeping in mind the project estimates. Blue bank has always been using traditional
methods like waterfall because it is easy to manage due to rigidity and at each phase has
specific deliverables and a review process. Phases are processed and completed one at a
time. The main problem with this model is its inability to make changes after the process
is halfway through and dependency on the phase as you cannot move to the next phase
before completing the current phase. In this case, it is better to switch to agile because we
are digitalizing all our checks to be deposited.

The benefit of agile over waterfall is the ability to change dynamically to the customer's
wants and needs. A focus on the features that are the highest value to the customer. A
short-fixed timeline that allows for immediate feedback from the customer and the ability
to move deliverables into production. So our new service could be stable, secure, and
ease to use. This also assures the loss of younger customers to much quality and customer
service is the key. Agile works well with small dedicated team members and lets the team
load balance workloads. We currently have 4 developers, 2 testers who can easily utilize
the process without any work pressure. So I request Harold to consider these points
andswitch to agile. Assume Harold liked your argument and agreed to proceed with agile
on this project. In his reply, Harold asked for further guidance on how to move forward.
Please reply back with the following:
What things will have to change on how this team operates and how key stakeholders
interact or engage on this project? (Hint: as you have learned,

I would like to thanks MR Harold for accepting the Agile Methodology to build the
platform for Blue bank

For agile to be successful there are certain prerequisites and it poses certain challenges
for leadership/business stakeholders as well,

The team is new to agile and some are not experienced as well to develop the mobile
application Agile software development refers to software development methodologies
centered round the idea of iterative development, where requirements and solutions
evolve through collaboration between self-organizing cross-functional teams. The
ultimate value in agile development is that it enables teams to deliver value faster, with
greater quality and predictability, and greater aptitude to respond to change. Scrum and
Kanban are two of the most widely used agile methodologies.

Via continuous interaction in Team will help members to develop the skill required to
develop the Web and mobile application for blue bank, from Requirement gathering to
final prototype product discussion will lead to successful project implementation.

Yes there will be challenges but by using the right technique like scrum and Kanban,
team can easily cope up with the things like more responsive to request, High value
feature, can deliver quickly with short cycles. Via Scum master team can track the day to
day work in daily meetings, as a team we can have the tremendous of Project status.

The person who is experience in certain field he/she can be the Product owner and owner
can help team mates to grow and learn certain things to do so.

Yes Team will require the Trainings like: To understand the Agile methodology with
Blue Bank’s way, those members which are having less experience Lead can arrange the
trainings for Web/Mobile application development for them.
 As of my knowledge, our team members have some experience in web development but
none in mobile development. Nobody on team has performance testing experience or
User experience expertise. People with an open mindset are the only key pre-requisite for
the successful implementation of an agile method. In fact, I would not suggest that you
add too many tools to a team that is not used to them. Instead, if the team has the open
mindset and the requisite attitude then train and start them on an Agile method. Any
Agile method will do - Kanban, XP, Scrum. Most of the developers and testers have
offices on different floors of the building and generally work in their office. Since the
team is scattered then some amount of technology needs to be taken upfront. The most
important aspects of good agile project management is judgement and responding to
change. With judgement, I mean the ability to see risks(good perception and listening
skills) before they become issues and coming up withgood strategies to mitigate these
risks. Having the courage to accept that you do not have all answers are a prerequisite for
Agile to be successful. If everyone just applies common sense in thinking value of
incremental change the right tools will automatically get commissioned on the way. Our
Business stakeholders who wrotethe high level vision for the mobile application are
going to help refine or define