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 @ Nortwestern

No description
by

Gary Brown

on 25 March 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile @ Nortwestern

AGILE NORTHWESTERN
Manifesto for
Agile Software Development
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

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.
Enterprise Reporting & Analytics
(ERA) @ NUIT
What is AGILE?

How can you get here?


Here's how NUIT's
Enterprise Reporting & Analytics
(ERA) department does Agile....
Benefits of Agile
Stakeholder Engagement
Focusing on Business Value
Early & Predictable Delivery
Allows for Change
Improving Quality
Measurable Productivity
@
BACKLOG
DONE
The Agile movement proposes alternatives to traditional waterfall project management. Here's a typical software development waterfall:
IN PROGRESS
What's wrong
with this process?


Any better way?
TODO
Agile principles
The Agile Manifesto is based on twelve principles:

Customer satisfaction by rapid delivery of useful software
Welcome changing requirements, even late in development
Working software is delivered frequently (weeks rather than months)
Close, daily cooperation between business people and developers
Projects are built around motivated individuals, who should be trusted
Face-to-face conversation is the best form of communication (co-location)
Working software is the principal measure of progress
Sustainable development, able to maintain a constant pace
Continuous attention to technical excellence and good design
Simplicity—the art of maximizing the amount of work not done—is essential
Self-organizing teams
Regular adaptation to changing circumstances
Customer Request:

"I want a new report
for student applications
and admissions by year
and ethnicity."
Business Analyst: Analysis of
Admissions Data Warehouse to insure student applications and
admissions counts with year
and ethnicity dimensions.
Data Architect: Perform Source-
to-Target Database Mapping for
new ethnicity dimension.
ETL Developer: Develop Extract,
Transformation and Load of
new ethnicity dimension.
Cognos Developer: Add new ethnicity dimension to SES Admissions Package.
Business Analyst: Testing of new Ethnicity Dimension in SES Admissions Cognos Package.
Release Manager: Release Planning Session for new SES Admissions 3.1 RC1 - New Ethnicity Dimension.
Tech Team: Release to TEST of SES Admissions 3.1 RC1
SES Team: QA Testing of new Ethnicity Dimension in Cognos Package.
2-Week
Iterations (THU-WED)

Planning Sessions
Iteration Review/Kick-off
Daily SCRUM Meeting - 9:30 AM

Scoring Stories:

Story Points
Hours
Small/Medium/Large
Gary Brown
Applications Systems Manager
Enterprise Reporting and Analytics
Northwestern University Information Technology (NUIT)
OFFICE: (847) 467-0696 | MOBILE: (630) 660-8231
EMAIL: gary.brown@northwestern.edu
Questions?
Comments?
JIRA Agile Demonstration
NU Agile Scrum
Community of Practice
Our Experiences
Refine & Adapt the Process to Your Needs
Only commit to stories you can complete
If anything... commit to less and have team pull from Backlog as needed
Keep the Backlog Groomed & Prioritized
Don't plan around Support
Estimating Stories by Hours
Carryover/Incomplete Work Inevitable -- especially starting out -- but work hard to avoid... usually a result of underestimating, interruptions, low velocity or improperly "thin-sliced" stories (Epics)
It's difficult to frequently get customer's time for planning, review, and demonstration; Our Business Analysts are often making these decisions
Our customers still mostly "Waterfall" approach while we develop in "Agile"
Automated Testing is Crucial
Make Agile Meetings Mandatory
Keep Daily SCRUM Meetings SHORT
No dial-in; Just email updates if you can't attend in-person
Perform demonstrations whenever possible
Study or Train on Agile before beginning
Get Expert to Help When Getting Started
Give Iterations time to stabilize velocity and capacity numbers
Then, plan and track around these numbers
Steven Khars
I'm not an Agile expert. This is just my experience utilizing Agile in software development. Your mileage may vary.
Presented By: Gary Brown - Enterprise Reporting & Analytics (ERA)
NU-AGILE-COP@LISTSERV.IT.NORTHWESTERN.EDU
Full transcript