Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Agile Project Management

No description
by

Kate Nesterov

on 9 October 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile Project Management

Responsible for bridging the gap between the customer, business stakeholders, and the development team. This person is an expert on the product and customer's needs and priorities. The product owner makes sure that the right features are put into the product backlog, helps sets the direction of the product, and works with the development team daily to help clarify requirements. Sometimes called a
History
What is agile?
ag·ile

Agile Project Management
/'ajel/
adjective
1. able to move quickly and easily
"Ruth was as agile as a monkey"
2. relating to or denoting a method of project management, used especially for software development, that is characterized by the division of tasks into short phases of work and frequent reassessment and adaptation of plans.
"agile methods replace high-level design with frequent redesign"
In 2001, a group of 17 software developers decided to create a modern and more effective workflow. They created twelve principles
and a manifesto.
Principle: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software [design].
Often the main point of the delivery is sidetracked. The highest priority is for the end user to perform tasks that they could not do before, solve a problem, do their job better and be more efficient.
How can this principle be applied?
Shorten the time between the early planning of the project and client feedback. This will give an opportunity to steer in a more suitable direction in the early stages to prevent bulkier revisions later on in the project.
Principle: Welcome changing requirements, even late in development. Agile process harness change for the customer's competitive advantage.
Implement changes now. No need to wait for whole system [design] redesign.
How can this principle be applied?
Shorten time between realizing and materializing important change. Even if it's in late stages of development process.
Principle: Deliver working software frequently, from a couple of weeks to a couple of months, which a preference to the shorter timescale.
Older methods focused a lot on piles of documentation in the beginning and also end of the project - sometimes with nothing to show for it.
How can this principle be applied?
Shorten time between planning and delivery. Focus more on creating rather than planning. This will improves efficiency and effectiveness of the work.
Principle: Business people and developers must work together daily throughout the project.
If the two sides co-exist together and are in sync they will understand each other and lead to more productive and rewarding work.
How can this principle be applied?
Co-location between the business people and developers and implementing communication tools for remote workers.
Principle: Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
There should be no micromanaging of the teams in agile project management.
How can this principle be applied?
Trust in your team to complete project's objectives.
Principle: The most efficient and effective method of conveying information to and within development team is face-to-face conversation.
Shorten the time between questions and the answer. Another great reason for co-locating the teams and having the remote work done during the same hours. When everyone works together under the same "virtual" roof, it is much easier to collaborate in terms of asking questions making suggestions, and communicating.
Principle: Working software [design] is the primary measure of progress.
The primary metric of agile project management is whether the software [design] is working. If it is not working, then how many hours have been worked or bugs fixed is irrelevant.
Principle: Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
When working on a long project it is common to get burnout.
How can this principle be applied?
Work should be performed in short productive bursts. Excessive overtime will impact the overall quality of the project. There needs to be a right pace for the team members, where when leaving the office they will be tired yet satisfied.
Principle: Continuous attention to technical excellence and good design enhances agility.
Developers shouldn't wait to clean up the code.
How can this principle be applied?
Make the code better with each iteration. Performing this during the project will save a lot more time than cleaning up code late - which can also mean never.
Principle: Simplicity -- the art of maximizing the amount of work not done -- is essential.
Keep things simple and shorten time between comprehension and completion.
How can this principle be applied?
Keep track of the team, count the hours worked in a fun way by using project management tools such as:
Dashable
http://www.dashable.com/?utm_source=Hubspot&utm_medium=Blog&utm_campaign=12BasicPrinciples
Principle: The best architectures, requirements, and designs emerge from self-organizing team.
A great agile team takes it's own direction. Members don't need to be told what needs to be done -- they attack problems, clear obstacles, and find solutions.
Principle: At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Inspect and adapt.

If there is a better of moving the project forward, the team should implement adjustments.
Development Team
Product Owner
Scrum Master
This person is responsible for supporting the
development team
, clearing organizational roadblocks, and keep the agile process consistent. A scrum master is sometimes called a
So how exactly does agile project management work?
The group of people who do the work of creating the product. Programmers, testers, designers, writers, and anyone else who has hands-on role in product development.
customer representative.
project facilitator.
0:36
Scrum vs. Waterfall
Example Sprint Backlog
Each feature is placed on an index card or post-it. It is often written in a perspective persona.
As Mary, I can...so that I can..."
design/UX/website part
What is Agile Project Management?
Agile web development is not a specific process, action, or a daylong exercise. Agile is a mindset, an attitude with which a project is undertaken.

It means streamlining the project, taking away time-sucks, performing frequent sanity checks, and making sure that you’re not spending excessive time on things that don’t add value to the project
Increments
&
Iterations
Get frequent feedback from the client/users. Carbon 5's "5 on Friday"
Adapt the design to match the feedback.
Repeat.
"[agile project management] is all about how quickly we can learn whether we've got a good idea..."

-Phil Barett, Deloitte Digital
Most of the changes made to a project after launch are made due to unmet or unforeseen user requirements.
Waterfall vs. Scrums

Another way of working in projects was by using what is called the Waterfall method. This method is a traditional approach to product development. It is carried out sequentially and some people argue that it is a more rigid and a less effective approach.

Waterfall
The way the Waterfall approach works is that first you discover/plan, then design, then develop, then review, then you are done.
Sprints
Within the Scum process there are these cycles of work called Sprints. Sprints are short duration milestones. The Sprints allow for teams to tackle a small and manageable chunk of the project and get it to a ship ready state which basically means that chunk is completed by again, taking small parts of the final project and discovering, designing, developing, and testing these small chunks of the final project in increments. The goal of each Sprint is to have a shippable product all done at the end of each Sprint. Then you repeat the Sprints until you finish the entire project.

How does an Agile workflow look like in a practical situation?

Agile Project Management Process
A Product Backlog is a list of all the features known as User Stories that could be in the final product.

Product Backlog
These User Stories are a way of describing a feature set. These features are prioritized usually by the
Product Owner.
Sprint Planning
Product Owner,
Scrum Master
, and
Team
discuss the top priority features in the Product Backlog and determine what can go into the
Sprint Backlog.

Sprint backlog
Consists of a board where the features that are going to be part of the product are organized by how long it will take to complete. For each feature on the list the team needs to estimate how long it will take to complete.
Daily Scum Meeting
The
Daily Scum Meeting
is a like a standup. The Scrum meeting is led by the Scrum Master, who is like the Project Manager. She/He facilitates the meetings and makes sure that everyone has the tools they need to get their job done and facilitates release planning. Here the team discusses what has been completed and what will be worked on for the next Sprint and anything that could impede progress on any given task.

Burndown Charts
As the tasks get completed they are crossed from the
Burndown Charts.
Your goal is finish all the tasks from the Burndown Chart.
Repeat this process after every Sprint and you should have a
Potential Shippable Increment
. A Potential Shippable Increment means that a “slice of the entire product” is ready to be delivered.
So, how can agile project management can help you in your future project?
Let's take a look at the 12 agile principles and how they can be applied:
Resources:
1. http://webdesignledger.com/applying-agile-principles-to-design

2. http://webdesign.tutsplus.com/articles/a-designers-introduction-to-agile-methodology--cms-23349 

3. Youtube: Phil Barrett - The role of UX in the Agile product management process

4. Youtube: Mixing Lean UX and Agile Development by Courtney Hemphill

5. Youtube: Introduction to Scrum - 7 Minutes

6. http://sixrevisions.com/web-development/agile/

7. http://sixrevisions.com/user-experience-ux/agile-ux-design/

8. https://en.wikipedia.org/wiki/Agile_software_development#Agile_methods

9. http://blog.hubspot.com/agency/basic-principles-agile-project-management

10. http://www.agilemanifesto.org/

11. http://scrumtrainingseries.com/
Thank you for watching!
Sprint Review
At the end of all the Sprints there is a
Sprint Review
is where the team meets to show the
final product
to the
Product Owner.


And Voila, you have your product ready!

Manifesto of APM
Individuals and interactions
over processes and tools
Working software
over comprehensive documentation
Customer collaboration
over contract negotiation
Responding to change
over following a plan
That is, while there is value in the items on the right, we value the items on the left more."
"We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value:
design/UX
The 12 Principles of Agile Project Management
Full transcript