-
Be able to discuss Agile Development amongst developers and potential employers
-
Be able to write effective User Stories for a new project
-
Be able to use Trello to organize User Stories using Agile principles
-
What is Agile Development?
-
Why use Agile Development?
-
Agile vs. Waterfall Methodology
-
Roles Within Agile Development
-
User Stories
-
A Software Development Methodology
-
Introduced by the Agile Manifesto in 2001
-
Focused on Customer Satisfaction with Early & Continuous Delivery
-
Requirements and Solutions Evolve Through Collaboration
-
Promotes Early Delivery
-
Continuous Improvement via Iteration
-
Enables Rapid Response to Change
-
17 software developers met at the Snowbird resort in Utah on February 2001.
-
They met to discuss lightweight development methods.
-
The outcome was a publication named the Manifesto for Agile Software Development.
-
They said that by uncovering better ways of developing software by doing it and helping others do it, they have come to value...
Agile Development prioritizes the satisfaction of the customer through early and continuous delivery of valuable software.
- Risk
- Workflow
- Change
- Quality
- Product Vision/Direction
- Documentation
After five minutes, be prepared to share your thoughts...
-
Product Owner: The person responsible for bridging the gap between the customer, stakeholders, and the development team.
-
Stakeholders: Anyone with an interest in the project.
-
Development Team: The group of people who do the work of creating a product. Programmers, testers & designers.
-
Scrum Master: The person responsible for supporting the development team and keeping the agile process consistent.
-
Agile Mentor: Someone with experience implementing agile projects and can share that experience with a team.
-
A sprint is a single iterative cycle that:
- Begins with initial planning
- Ends with potentially deployable/shippable enhanced working software
-
Typically two to four weeks in duration...
-
Short Duration (up to 15 minutes)
-
Each Participant Answers Three Questions:
- What did you accomplish yesterday?
- What are you working on today?
- What obstacles/challenges are you faced with?
-
Duration is still up to 15 minutes
-
But, each Student answers these questions:
- What are you working on?
- What are you struggling with?
- What are you excited about?
-
Key component of the initial planning for an Agile project
-
Defines small chunks of business value which can be implemented in a period of days to weeks
-
Captures what a user does or needs
-
Commonly formulated by questioning the customer/user
-
Often initially written on 3x5 index cards
-
NOT a programming To-Do List
-
What is Trello?
-
Register Your Account (free)
-
Using Trello for Agile
-
Managing User Stories
-
Exercise - Enter User Stories
-
Free, flexible, visual way to manage projects and organize anything
-
Used by millions of users
-
Trello's Structure:
- Boards (main containers)
- Boards contain Lists
- Lists contain Cards
- Cards may have a Description, Comments, Members, Labels, a Checklist and Attachments
Go to
https://trello.com/
to sign up
-
Create a Board for your Project
-
Real-world projects could have the following Lists organized from left-to-right:
- Ice Box (aka Backlog)
- Current (aka Planned)
- Sprint (aka In Progress)
- Done
- Due to time limitations, you can organize your lists as:
- Ice Box
- MVP (aka Planned)
- Done
-
Each User Story will be a Trello Card
-
The User Story cards can contain:
- The details for the Story in the Description section
- Optional: You can document the Point value assigned to complete the story in parenthesis after the Title.
- Use the Checklist to track tasks or steps necessary to complete the story. When creating a checklist, you are given the opportunity to name it.
-
Ice Box: Put all of your ideas in here to start. Feel free to put in large features (epics) in here until they are broken down into user stories.
-
Current: Stories that make the cut are put here. You may choose to prioritize your stories from top to bottom. This is also a good place to put cards for bugs to be fixed.
-
Sprint: This list holds the user stories and bugs currently being developed.
-
Done: Done obviously holds the completed stories.