https://www.coursera.org/learn/agile-project-management/home/welcome [[17-04-2022]] # Agile Philosophy [[Agile]] ## Agile Manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan ## Agile Value Value 1: Individuals and interactions Value 2: Working software (Solutions) Value 3: Customer collaboration Value 4: Responding to change ^36a4e2 ## Agile 12 Principles 1. **Customer satisfaction through early and continuous software delivery** – Customers are happier when they receive working software at regular intervals, rather than waiting extended periods of time between releases. 2. **Accommodate changing requirements throughout the development process** – The ability to avoid delays when a requirement or feature request changes. 3. **Frequent delivery of working software** – Scrum accommodates this principle since the team operates in software sprints or iterations that ensure regular delivery of working software. 4. **Collaboration between the business stakeholders and developers throughout the project** – Better decisions are made when the business and technical team are aligned. 5. **Support, trust, and motivate the people involved** – Motivated teams are more likely to deliver their best work than unhappy teams. 6. **Enable face-to-face interactions** – Communication is more successful when development teams are co-located. 7. **Working software is the primary measure of progress** – Delivering functional software to the customer is the ultimate factor that measures progress. 8. **Agile processes to support a consistent development pace** – Teams establish a repeatable and maintainable speed at which they can deliver working software, and they repeat it with each release. 9. **Attention to technical detail and design enhances agility** – The right skills and good design ensures the team can maintain the pace, constantly improve the product, and sustain change. 10. **Simplicity** – Develop just enough to get the job done for right now. 11. **Self-organizing teams encourage great architectures, requirements, and designs** – Skilled and motivated team members who have decision-making power, take ownership, communicate regularly with other team members, and share ideas that deliver quality products. 12. **Regular reflections on how to become more effective** – Self-improvement, process improvement, advancing skills, and techniques help team members work more efficiently. ^9a433f ## Popular Agile Frameworks 1. [[Scrum]] 2. [[Kanban]] 3. [[Lean Software Development]] 4. [[XP]] VUCA - Volatility, uncertainty, complexity, and ambiguity --- # Scrum [[Scrum]] - Different roles of Product Owner, Scrum Master, Development Team ## Implementing Scrum https://scrumguides.org/scrum-guide.html#product-backlog ### Product Backlog - Single authoritative source for things that a team work on. Guide and roadmap for the product. - Living artifact - live document - Owned and adjusted by the product owner - prioritised list of features **Feature of a backlog** - Description - Essential details of an item. - Value - Value to user and team - Order - Rank them in orders of importance / prioritised - Estimate - Relative Effort Estimate ### [[User Stories]] ## Backlog refinement and effort estimation ### Estimates - How much effort needed to finish that task - Absolute Estimation - also call Time and Effort Estimation in traditional project management - Relative Estimation - Compare to another task - T-Shirt Sizes - medium size item. - subjective ranking, anchor item first, M size then compare.. on the effort needed for each task - Story points (Fibonacci) - Also subjective, but using the number scale, to estimate the difficulty and effort. Backlog refinement frequency depends on team. and mode of communication. [[Agile effort estimation techniques]] --- Creating a Sprint backlog - Based on points, - Current Sprint or Next Sprint. - Daily Stand Up. Daily Scrum. - What i worked on yesterday? - What i am working on today? - What are blocking me? - TIP "Hey, we will want to discuss the next item on the agenda, is it ok if we put a pin on it, and return to it if we got extra time, if not at the next meeting?" - At the end of the sprint, then a Sprint Review. 4 hours Each Sprint produce Product Increment, This work towards a Minimum Viable Product. [[Releasable Increment versus Minimum Viable Product]] --- ## The Sprint Retrospective 3 hours. - What's working or not team, people, processes and tools? - What improvements are worth exploring in next Sprint? - What improvement were put in place for the last Sprint? Were they helpful or not? why? Measures 1. Scrum value of respect, and blameless. 1. Create safe space, create awkwardness 2. Participation is key. 3. Balance the negative with the positive. 4. Act on it. If not talk for what. Scrum master need to build trust, safety, and communication. [[Sprint Retrospectives Pitfalls and best practices]] --- Burndown Chart - Keep team aware how they are doing against their goals - This is a method to Calculating progress and velocity - Each user story got points. - Velocity of a team (Points/Weeks) - Historical what the team can achieve - Cannot compare teams. Just different. - Velocity -- can calculate how much time needed to complete whole product backlogs. And estimate what will be delivered by x months. [[Interpreting velocity Dos and Donts]] --- ## Using Kanban Boards WIP limits - Work in progress limits Visualize progress, and get a sense of flow. - Each item is a Task --- # Tools for transparency and collaboration - Schedule and backlog management tools - Jira - Trello - Asana - Documentation - Google docs - Spreadsheets - Presentations - Communication collaboration - Video conference - Instant messages --- https://www.youtube.com/watch?v=502ILHjX9EE --- ?What is developing user stories in Agile. --- Value road map 1. Product Vision 2. Product Roadmap 3. Release plan [[Product Roadmaps. Benefits, pitfalls and best practices]] [[Responding to change over following a plan]] ## Change management. Facilitating organisational change - Organisational Culture, related to Value. - If do not consider the value, then it's difficult to change. - [[20210809 Work Culture]] - [[organisational culture]] - Agile is about having new values, and culture. - Take years to change culture. - Change takes patient persistence - Small change lead to big changes [[020.300 Solution Focused MOC]] [[HOW TO CREATE THE CHANGE (IMPLEMENT AGILE)]] 1. Create sense of ownership and urgency 1. Find executive sponsor who also feel a sense of ownership for the change you're creating 2. Having buy-in from someone at the top increases your changes of successfully driving any change in Organisational Culture 3. Ask, what is working and whats not working right now. 1. What is preventing us from providing the best possible product to our customers? 2. What is allowing our competitors to outperform us in this market? 3. How can we help our team become more productive and supported in the work? 1. Collect feedback before implementing change, and then after, to improve on the change process 4. Connect change to company's mission and values. [[The influencer change framework]] --- ## Coaching an Agile Team #mentor 1. Design the plays 1. Include the team to come out with the details. Even though you have the big picture. Detail how work gets done. 2. Provide Feedback 1. Big picture 1. Look for patterns 3. Celebrate Success 1. Acknowledge the effort. Good works. 2. Learn from mistakes. [[Coaching versus managing in Agile]] - Agile Scrum master are not managers, but coaches.. to support the scrum team to produce best work. - Reminded me of the [[020.300 Solution Focused MOC]] kind of ideas, that they have the resources and ability to problem solve.. --- # Agile team challenges Anticipate challenges in these 3 areas (based on agile principles) ## Value Delivery - Missing expected delivery dates - Burned out - Too many items "in progress" ![[Screenshot 2022-04-18 at 7.43.44 PM.png]] ## Business Collaboration ![[Screenshot 2022-04-18 at 7.45.30 PM.png]] ![[Screenshot 2022-04-18 at 7.46.11 PM.png]] - This is related to Change requests. Too many changes is frustrating. Control the flow of change requests. - Conducting a Solution Design Sprint is essentially, collecting requirements again.. What exactly are we trying to solve or build here. To clarify. ## Team dynamics and culture ![[Screenshot 2022-04-18 at 7.48.41 PM.png]] - ==Low Conflict is also a sign that there is not enough trust in the environment. Because people are afraid to disagree, and start a conflict.== Being Open and Courages is Agile Values. ^b57b31 ![[Screenshot 2022-04-18 at 7.50.47 PM.png]] Idea, write story of the best and worst team they work out. Create a Do and Don't list of how they should work together. ![[Screenshot 2022-04-18 at 7.51.11 PM.png]] Six Hats thinking technique - Each person got a role to play during sprint meetings. --- # Common Agile coaching challenges ![[Screenshot 2022-04-18 at 7.54.43 PM.png]] 1. Managing a stable product roadmap 1. Product Ambition 1. Product leadership is overly ambitious about what the team can realistically deliver 1. ![[Screenshot 2022-04-18 at 7.57.01 PM.png]] 2. Product Assumptions 1. Solutions and products based on certain assumptions. 1. Solution: Document the assumptions and make them transparent (confirm or check) 2. Solution: Unbiased user research 1. Surveys, Focus Groups, collect objective data 2. Incomplete implementation of Scrum 1. Loss of clear roles and responsibilities 2. Tempted to skip some events or blend them to save time 1. Could lead to reduce transparent 3. Not providing the team with scrum coaching needed 4. SOLUTION: Implement scrum completely 3. Lack of Team stability solutions 1. Solutions: Having a quick onboarding process 2. Use "Pair Programming" - new person pair with older person and learn on the job. 3. Have shorter sprints --- ## The Evolution of agile Product Centric Approach Blended approach is useful, Agile VUCA World Volatility, Uncertainty Complexity Ambiguity DevOps Framework- Another new framework. About developing software for world market. large scale https://devops.com/how-to-combine-devops-and-agile/ https://www.cmswire.com/information-management/agile-vs-devops-whats-the-difference/#:~:text=Fundamentally%2C%20DevOps%20brings%20together%20two,the%20ever%2Dchanging%20consumer%20needs.&text=%2Dbased%20Shiftleft%2C%20explained%20how%20both%20Agile%20and%20DevOps%20are%20managed https://www.scrum.org/resources/convergence-scrum-and-devops Business Agility - Organisation rethinking to be agile. Many industries are adopting agile framework, thinking to help company to be more agile in the VUCA world. - What about agile case management?! [[Scaling Agile]] Interesting! so many different framework, and ways of organising people to work. --- ![[Screenshot 2022-04-18 at 8.20.58 PM.png]] - Small changes lead to big change - introduce one solutions for the problem they faces now. ![[Coursera SRHFNCD2YKQH.pdf]]