Agile Methodology for Software Development: Briefing and Recommendations

Executive Summary for Breifing
In the briefing below, we will look at two clients: Client A and Client B whom, we will be
collaborating with.
With Client A specializes in e-commerce device applications and web as a small start-up and has
its employees working within the one city. Client B being a large engineering-oriented company,
has its offices around the world difference in the size of the company, we will have to select a
suitable Agile development design.
This design will be based on the size of the organization. After consideration of all Agile
development methods, a suitable one will be selected.

Introduction
The process of coming up with a new software in the market can be time consuming. Finding a
suitable methodology that will allow change to the software as time goes by can prove difficult a
time. Using a reliable methodology can rescue you and save a lot of your time can prove very
helpful. A methodology of sort is Agile.
Body:
BREIFING
Big Four Software Development Supervisor
PURPOSE
The aim of this is to submit recommendations you are intending to make after conducting a
couple of audits and meetings with the clients.
BACKGROUND
In the meetings and audits with clients. With differences in field of expertise, they were both
running an e-business with most of their transaction being done through the internet.
It was clear that both Client A and Client B were growing in numbers and offices. Client A was
intending to expand to more new towns around the country while Client B was venturing into
new countries around the world. This means that their business activities are dynamic and would
shift from time to time with the shift in demand from consumers as well.
Overview of Agile Process.
Mostly used in the process of project management for software development. It is most
applicable in cases where there is continues evolution of demand and solution in an organization,
business or enterprise. It is mostly used to accomplish difficult projects because it easily adopts.
It insists on working together, being flexible, improving every time and high quality results. It
also entails 6 main deliverables.
Vision statement of Product: A summary of goals of the product
Roadmap of the product: Definition of requirement for achievement of the product
Backlog of product: A full list of does to achieve the product
Plan of product release: A schedule of achieving the product.
Sprint Backlog: User requirements.
Increment: A final working product.
It was designed to curb the short-comings and failures of traditional software development
methods like waterfall method. With the highly competitive market of software development
industry, that is caused by ever changing demand of consumer and continuous upgrades of

software. Developers have to keep at the peak of the market, hence, they have to continuously
innovate and also improve their products to remain at the peak of the competition.
This need or urge to remain at the top by developers could not be fulfilled if they opted for
waterfall approach method.
Agile was developed and its manifesto presented which contained values and principles.
Manifesto values of agile process
Interactions as well as Individuals over tools or/and processes
Having a working software instead of comprehensive documentation of a product
Customer collaboration instead of negotiation of contract
Change Response and overlooking following a plan
Manifesto principles of agile process
Satisfaction of Consumer: This is achieved through continuously delivering software early.
Accommodation of ever changing requirements during the whole development process
Delivering of a software that is working more frequently
Stakeholders and developers are expected to collaborate throughout the project
Involved personnel should be supported, trusted and motivated always
Interactions through face-to-face should be encouraged.
A working software can be used to measure the primary progress.
It supports a development pace that is consistent.
Has enhanced agility because of its attention to tiny detail and design
It entails simplicity
Great architectures, requirements, and designs is encouraged by self-organizing teams
Its need for effectiveness regularly encourages reflections on how to be more effective
Use of agile requires strict adherence to the values and principles.
Methodology for each client
Client A.
With the start-up being small and all staff in the same city, it is safe to assume they have
established themselves but have not grown well beyond the same town of establishment. With
this, considerations of using Agile Scrum Methodology could be advantageous to them.

The scrum framework can prove useful in managing iterative as well as incremental projects of
all types. With their vision to expand way beyond the city and at some point in the future,
beyond the country, the Agile Scrum Methodology will prove useful because of its proven
productivity, easiness and ability to include practices of other agile models.
The Client will have to work closely with us to identify and prioritize functionalities of the
system through Product Backlog, that is, anything that needs to be implemented to successfully
avail a functional software system, feature of the system and bug fixes.
Client B.
With its big clientele base around the world, the client needs the quality of software to be
improved and responded quickly to the ever changing requirements of a customer. Using
Extreme Programming, these two requirement can be achieved alongside high-quality software
and continuous speedy delivery.
It highly promotes involvement of customer, continuous testing of software, rapid feedback from
users, close teamwork and planning continuously to deliver software that are working,
frequently.
This method is based on simple values:
Simplicity
Communication
Feedback
Courage