Agile Project Methodology

1. Agile Project Methodology

2. Housekeeping • Rules for OKCU Facility: • Attendees are NOT to access the building till 8:30 am.  This is when the facility opens their door for business. • Attendees are NOT to walk around the building or use the stairs, except for using their restroom. Some OMES staff did not adhere to this rule at previous trainings/meetings. Just like OMES, OKCU is a secure building and need to be able to protect their member's financial information. The stairwell is only for emergency use. • OKCU is no longer able to provide beverages for a price from their refrigerator. With the large groups and frequency they just aren’t able to maintain the drinks. • Coffee is complimentary, but please show appreciation by putting some money in their donation cup located in the refrigerator • Lunch • Lunch – Planned for 11:30 to 12:30

3. Introduction to Agile Video

4. Why Agile? • The Agile Manifesto and the Twelve Principles of Agile Software were the consequences of industry frustration in the 1990s. The enormous time lag between business requirements (the applications and features customers were requesting) and the delivery of technology that answered those needs, led to the cancelling of many projects. Business, requirements, and customer requisites changed during this lag time, and the final product did not meet the then current needs. The software development models of the day, led by the Waterfall model, were not meeting the demand for speed and did not take advantage of just how quickly software could be altered. (https://www.smartsheet.com/comprehensive-guide-values-principles-agile-manifesto)

5. Benefits of Agile Reduced Delivery Risk Demand driven development Benefits realized early Embraces ambiguity and uncertainty

6. Agile vs. Waterfall

7. Agile Roadmap to Success Preparation Execution Stage 4: Sprint Planning Stage 1: Vision Description: The goal for the product (What &Why) Owner: Product Owner Description: Establish specific Sprint goals & tasks Owner: PO & Team Stage 5: Daily Stand-Up Stage 2: Product Roadmap Description: Holistic view of product features that create the product vision Owner: Product Owner Description: Coordinate priorities of the day Owner: PO & Team 24 Hours Stage 3: Release Planning Stage 6 & 7: Sprint Review & Retrospective Description: Release timing for specific functionality Owner: Product Owner Description: Demo working product & Team refinement of environment and processes to optimize efficiency Owner: PO, Users & Team Agile Sprints

8. Traditional Project Framework Concept Updated Portfolio (Cost > $15,000) Name, Description, Initial Benefit, Initial Scope Initiation Updated Portfolio-Scorecard +/- 50% Milestone Plan Business Case Risk Assessment Monitor and Control Planning Updated Portfolio-Scorecard +/- 10% Milestone Plan Updated Business Case Updated Risk Assessment Execution Updated Portfolio-Scorecard Monthly Status Close Updated Actuals Updated Business Captured Metrics

9. How does Agile Fit? Iteration 0 Retrospective

10. Agile Mindset Individuals and interactions Processes and tools OVER Working Software Comprehensive documentation Customer collaboration Contract negotiation Responding to change Following a plan While there is value in the items on the right, we value the items on the left more.

11. Agile Mindset Deliver value rapidly and consistently Collaborate courageously Iterate to learn Simplify to avoid waste Consider context and adapt to realities Reflect on feedback and adapt product and processes Produce the highest quality products

12. Deciding which to use Determining which to use is a TEAM decision.

13. Product/Process vs. Project A Product is a particular application used by the agency to support agency programs. A Process in state government is the business method used by the agency to serve its clients / customers, and may or may not involve using a product. Products and Processes are used continuously by the agency to provide services to the citizens of Oklahoma. A Project is a way to implement changes to a product, improve processes, introduce a new product, or retire an old product. It is time-limited (has a start / end point).

14. Terminology Let's get some terminology out of the way.

15. Agile Flavors

16. Scrum High performing, cross functional teams.

17. Scrum Video

18. Kanban Real-time, visual communication and transparency of work. Work items are represented visually on a Kanban board, allowing team members to see the state of every piece of work at any time.

19. Sprint A set period of time during which specific work has to be completed and be made ready for review. Usually 2-4 weeks in length

20. User Stories User stories are used to convey a customer requirement. A representation of the customer need in a small concise statement of a feature needed to deliver value.

21. Elaboration Visioning Roadmap Development Release Planning Sprint Planning Sprint In Action

22. Backlog • Product Backlog • Prioritized list of requirements, features, defects and other work items (complete to do list) • Sprint Backlog • A subset of requirements from the product backlog that contains the planned scope for a specific sprint or iteration (current work item list)

23. Minimal Viable Product The smallest set of features or requirements to deliver value to the stakeholders and satisfy early adopters in the shortest time possible.

24. Stand Up • A daily meeting, also known as a daily scrum • Typically held in the same location and at the same time each day • No more than 15 minutes • Not used as problem solving meetings, but rather each team member answers the following questions • What did you do yesterday? • What will you do today? • Are there any impediments in your way? • Can include a 16th minute at the end of the meeting for longer discussions between team members to get additional information or solve problems

25. Burndown/Burnup Charts Simple graphical representation of the work presented to the team.

26. Velocity Velocity is how many “points” can your team get done in a Sprint Effort User Story Backlog Effort Story 5pts Add User 13pts Add Table to DB 1pt Add Dropdown 20pts Setup Security …. …. 5pts Test for acceptance 8pts Demo to users 110pts Sprint 1 Sprint 2 Sprint (n) Time Sprint is an Iteration of time your team commits to getting all assigned work done

27. Retrospective A time for team members to get together at the end of a sprint to celebrate team success and reflect upon what can be improved.

28. Definition of Done

29. Agile Project Methodology Initiation Phase

30. Initiation for Agile Projects • Set expectations • Role of Product Owner, Scrum Master, Business Analyst • Introduce idea of Agile project to the business • Develop Personas • Identify Themes and Epics • Prioritize Themes and Epics • Develop Roadmap In most circles this is called iteration zero.

31. Agile Roles

32. Agile Roles Defined

33. Scrum Master role in Initiation Facilitating meetings Coaching team members Mediating through conflict Helping to make decisions Helping to write personas Helping to write product visions (with Product Owner) Helping team get rid of impediments Really anything that will help the team meet their goals

34. Product Owner Role 6 Responsible for the product success Cares about user needs and business goals “Own” the Product on behalf of business owners Maintain stakeholders vision while developing the product Good team player- Collaborates with the development team and stakeholders Guide the development of the Product Backlog

35. The BA Role in Agile From a practical standpoint, the BA still does many of the same functions, just at a different point in the project and with different deliverables. Be the “value consciousness” of the team. Facilitate conversations, not write large documents (conversation over documentation).

36. Where does the analyst fit? Two views on the BA role.

37. The BA Role in Agile Taken from a presentation at the Project World BA Summit Conference Feb. 2016 by Ryland Leyton; full presentation can be found here: Agile Analysis Planning - R. Leyton , Used by Permission

38. The BA Role in Agile Taken from a presentation at the Project World BA Summit Conference Feb. 2016 by Ryland Leyton; full presentation can be found here: Agile Analysis Planning - R. Leyton, Used by Permission

39. Assign Roles In Your Team • Within your teams, assign the roles of • Product Owner • Scrum Master • Business Analyst • Team Members • Create name tags for each person • Time 10 Minutes

40. The role of documentation in Agile Agile methodologies are not as “anti-documentation” as we sometimes hear (fear), but it takes planning and advocacy not to feel like an afterthought.

41. Agile Documentation = Deployments

42. Agile Documentation • Continuous Documentation • Getting technical writers involved early is a great way to get feedback back on your design. • If you documentation team can’t figure out a feature, your customers probably won't either. • Everyone contributes to the documentation effort • Getting additional detail in the user stories or asking developers to add comments as they go provides more complete documentation at the end. Every little bit helps. • A point person who manages the documentation effort • They get the information and merge it into a cohesive document. • A tech writer with development experience can save some time on explaining established technologies.

43. Agile Documentation in Practice

44. Tools • High-Technology Tools: • Top Team • TFS – Team Foundation Server or VSTS – Visual Studio Team Services (now also known as Azure Devops) • Low-technology or Commonly Available Tools: • Sticky notes/paper Kanban boards on a wall • Whiteboards • Tracking tasks assigned to whom (Kanban style board) • Documenting / Diagramming process flows and architecture • Microsoft Office – Excel, PowerPoint and Word

45. Project Charter • Locate the Agile Project Charter template in eclipse. • Agile Project Charter • Scaled down version of the project charter as it applies to Agile Projects • Includes: • Project Vision Statement • Problem Statement • Project Roles • Road Map • Release Plan • Features List • Definition of Done • Note: The BA is not “responsible” for this deliverable but may help the Scrum Master/PM put it together.

46. Agile Communications Plan

47. Write a Project Charter & Communications Plan Complete a Project Charter for your product Complete a Communications Plan for your product Time – 1 Hour

48. Product Visioning Visioning is used to determine the desired outcome for an initiative worded in a concise and approachable manner. The elevator speech.

49. Product Vision • Consists of five interrelated parts: • Target Group – identifies for whom the product will be mainly built • Goals – identifies what the target group wants to achieve and the relationship of these goals to the product • The Needs – identifies needed objectives and tasks to achieve the goals • Value – identifies the value the target group expects to receive from the product • Key Features – identifies the key features of the product needed to meet the goals

50. Creative Idea for Developing Product Vision • Product Box Exercise • Facilitated session (usually by BA or PM) • Executive project team and stakeholders • Basic Concept: • If your product was marketed in box (like cereal or consumer electronics) what would be the marketing copy on the box. • What top product features, benefits, and attributes would you highlight on the box that would attract shoppers and convince them to buy your product? • This exercise can result in a product name, a graphic that would highlight the wonderful characteristics of the new product and some of the catchy phrases that encapsulate the benefits of using the proposed system.