Agile201 for Users Click / tap to move through the presentation.

Slides:



Advertisements
Similar presentations
Communicate Coordinate Collaborate Hawaii Strategy Institute 2011.
Advertisements

10 Software Engineering Foundations of Computer Science ã Cengage Learning.
A Workbook to Accompany Getting Digital Marketing Right A Simplified Process For Business Growth, Goal Attainment, and Powerful Marketing Primal Digital.
SUCCESSFUL SERVICE DESIGN Turning innovation into practice READ MORE... USER GUIDE Read the “User Guide” to find out more about this site START Ready to.
IMS Systems Analysis and Design Communication and Documentation: Additional Notes on Written Reports.
Xtreme Programming. Software Life Cycle The activities that take place between the time software program is first conceived and the time it is finally.
Agile Design and SCRUM Brent M. Dingle, Ph.D. “For the last few centuries, … science has been attempting to break matter down into ever smaller bits, in.
© 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Deeper Dive Into: User Stories.
Alcatel-Lucent CDC Workshop, Coaching & Knowledge Transfer Project Management.
1 Staffordshire UNIVERSITY School of Computing Slide: 1 Prototyping Agile Software Development 1 Rapid Application Development (RAD) Iterative Prototyping.
Process is continuously improving Have Definition of Done (DoD) DoD achievable within each iteration Team respects DoD The bottom line Delivering working,
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 other methodologies 1 Method/Process = step-by-step description of the steps involved.
Software from Requirements Brent Haines April 12, 2007 Why Methodology Doesn’t Really Matter.
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
1 Multimedia Development Team. 2 To discuss phases of MM production team members Multimedia I.
P3 Business Analysis. 2 Section F: Project Management F1.The nature of projects F2. Building the Business Case F4. Planning,monitoring and controlling.
There’s no need to climb alone Spark Claims No Copyright, and encourages the use of any template, document or idea found on our website in the resolution.
How to use C OBI T implementation resources Brian Selby Director of C OBI T Initiatives ISACA.
Project Management The much neglected art of running a project to a successful completion 15/07/2016(C) Management Expert Academy1.
Project Management Software development models & methodologies
Phase-1: Prepare for the Change Why stepping back and preparing for the change is so important to successful adoption: Uniform and effective change adoption.
Insert name of presentation on Master Slide The Quality Improvement Guide Insert Date here Presenter:
Software Development - Methodologies
‘Tis Better to be Effective Than Efficient
Methodologies and Algorithms
EI Architecture Overview/Current Assessment/Technical Architecture
How to get good commercial software built
The Strategic Role of Information Development in Continuous Delivery
Continuous Delivery- Complete Guide
Top Ten List for Directors of Technology
Agile Training – Agile Overview
Extreme Programming.
Agile Scrum Management
It’s not all about the tool!
Building the Balanced Scorecard
Building the foundations for innovation
September 20, 2017 Agile Techniques Workshop Susan Futey
WebQuest: Where you design your own Space Exploration Mission
Methodologies By Akinola Soyinka.
Software Engineering and Best Practices
Information Technology Project Management – Fifth Edition
Information Technology Project Management – Fifth Edition
REQUIREMENTS ANALYSIS
Object oriented system development life cycle
Application Development Theory
Introduction to Tech Communication & Project Management Arthur C.M. Chen , Rm
1. Define a Vision & Identify Business Scenarios
Preparing for Agile201 Click / tap to move through the presentation.
Building the Balanced Scorecard
Methodologies For Systems Analysis.
Strategic Planning Setting Direction Retreat
Johanna Rothman Know What “Done” Means Chapter 11
Professional Certificate in Strategic Change Management
HELLO, WE’RE IMPLEMENT We are committed to:
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
The Agile Inception Deck
CATHCA National Conference 2018
Teaching slides Chapter 13
AD642 Project Communication: Intro
Agile Development – a new way of software development?
Measure Phase Wrap Up and Action Items
Rapid software development
How to deal with requirements in an Agile context?
Business Plan Basics This is going to be a quick identification of why you want a written plan and its constituent elements.
Time Scheduling and Project management
Affiliate Slide Show Guide to the Unique Selling Points
Project management Initiative & Self Learning Confidence in leadership
Product Development & Planning
Presentation transcript:

Agile201 for Users Click / tap to move through the presentation. For rights & permissions, see final slide.

What are the key components of Agile201? Welcome to Agile201 This introduction explains how to make the most of Agile201. What is Agile201 for? What are the key components of Agile201? Here are some of the questions it can help you to answer: How is Agile201 organised? How can I tell you what else I need to know? How can I find out more?

It gives you the complete Agile lifecycle. Right out of the box. What is Agile201 for? Agile is a naturally simple & lightweight route to delivery. But just because it’s simple, that doesn’t make it easy. Agile201 is unique. It gives you the complete Agile lifecycle. Right out of the box. That’s what Agile201 is for: to make Agile as easy as it’s simple. This presentation shows you how it does that – and how easy it is for you to work with Agile201.

How does Agile201 work? Agile201 organises Agile as a whole into a 3-tiered system of nested processes: Product, Release & Iteration Management. Product Management defines the strategic level of Agile delivery. This is a permanent function. It is designed to manage the product throughout its lifetime. Every product passes through multiple phases of Release Management. A release may deliver a new version of the product… …or smaller updates, localisations, new markets, platforms, fixes, etc. Each release is then divided into cycles of Iteration Management. Which is when the planned changes are actually implemented. And working software is delivered. Then repeat for the lifetime of the product. Iteration Iteration Iteration Iteration Working software Release Working software Product Working software Working software

Navigating Agile201.com Top-level menus cover every aspect of Agile delivery. Agile201.com is an easily-learned, menu-driven website that provides rapid access to every aspect of Agile with just a few clicks or taps. Drill down to the precise knowledge you need.

Navigating Agile201.com That’ll take you to a page that looks something like this… The complete end-to-end workflow This is a standard ‘practice’ page. It has 5 basic parts… A quick summary for experts Comprehensive detail for newcomers Full background to every task Expert advice for success Other pages have different structures, but we think they’re equally clear.

The Agile201 menu system You’ll also find another menu at the top of each page, designed to make managing Agile201.com itself easy. Talk to us directly. We’re more than happy to deal with any issues or ideas you want to raise. Facts. Thoughts. Opinions. Cartoons! Shortcuts to every page on Agile201.com. The Agile201 team. Real people. Access to the Agile201 community. Build your own teams & forums. The usual legal stuff. Terms of service, Privacy, Copyright, Distribution rights. Dull but important – please read. Quick answers to some of our most frequently posed questions.

The Agile menu A good place to begin for a really solid background to Agile itself. Agile’s ultimate ground rules. The practices that makes Agile different. The end-to-end delivery process. The Agile201 interpretation of Agile. What is the evidence? How the experts make the most of Agile. User guide to Agile concepts & language.

The Agile disciplines The practical foundations of an Agile culture. Agile201 walks you through you them all.

Manage medium-term delivery – objectives, epics, plan, prepare. The Agile201 menu system The next 3 top-level menu items organise Agile into a sequence of nested processes – Product, Release & Iteration Management. Control your team’s everyday work – schedule, implement, track, improve. Direct the long-term future of your product – vision, strategy, backlog. Manage medium-term delivery – objectives, epics, plan, prepare. In other words…

The Product menu Agile at its highest level – setting the overall vision, strategy, scope & plan for an integrated, multi-release programme of work as a whole. Translating the product backlog into action. What is a product? How does the product lifecycle work? Setting & refining the product’s long-term goals. Specifying what a successful product will look like.

The Release menu The release- or project-level layer of Agile – the domain of the Agile team – is fundamental for creating the conditions for successful delivery. Summary of the release management process, tasks & planning. Setting the ground rules for delivery. Selecting deliverables, mapping iterations, validating the plan. Breaking major components into manageable elements. Making sure we’re really ready to go.

The Iteration menu The iteration is the core of the Agile team’s everyday work. The Iteration menu provides detailed support at every step.

The Iteration menu Where delivery happens – setting up, running, tracking & controlling the flow of work. Selecting & scheduling the work to be done. Summary of iteration management as a whole. Tracking team effort. Taking the pulse of delivery. The daily cycle. Optimising the iteration’s scope & aims. Demonstrating the team’s achievements. Reviewing & tuning the team’s ways of working.

The Stories menu The story is the basic unit of Agile delivery, and Agile201 delivers a thorough approach to story creation & management. Understanding what stories are – and what they aren’t – why they’re important & how they work. How to capture & structure a story. Investigating issues, problems & opportunities in delivery. What will it take to deliver this story?

Core Team The People menu Governance Extended Team Extended Team The heart of the Agile organisation is the Core Team. Get this right, and almost everything else flows naturally. Get it wrong, and almost nothing can be achieved. Governance Extended Team Extended Team Product Owner And don’t underestimate how hard it is to align all these people! Core Team Iteration Lead Developer Developer User User Developer

The People menu More than almost any other methodology, Agile relies on people. The People menu explains how Agile201’s approach helps Agile to achieve its impressive results. How to set up your team. Setting up critical relationships & dependencies The core Agile roles. Agile201 pays close attention to the users, whose role is especially difficult but absolutely vital to Agile.

The Tools menu Agile has created or adopted dozens of innovative tools & techniques. The Tools menu explains what they are and how to use them. Which ones you need to pay special attention to depends on your role. But everyone should be aware of where each tool & each technique fits into the overall lifecycle.

The Tools menu This diagram shows the tools used in the Product & Release cycles.

The Tools menu And this diagram shows the main places where each tool & technique is used within individual iterations.

We always welcome feedback. Through the Agile201 Community & Forums. Directly, using the feedback page on Agile201.com. Or just email us at: support@Agile201.com This is probably quite enough to be getting on with! But if there’s anything more you’d like from Agile201, please don’t hesitate to tell us. It will go straight into the Agile201 backlog.

Rights & permissions: You may distribute, use & edit this presentation as you see fit, except that you may not remove the Agile201 logos, copyright statements & other Agile201 identifiers.