Scrum in your personal life
•
0 likes•129 views
This document discusses how to apply Scrum principles to personal goals and projects. It outlines the Scrum roles, events, and tools that can be used to "scrumify" a personal goal. Applying Scrum through story point estimation, daily stand-ups, sprint planning, reviews and retrospectives can help achieve goals in a structured way. Some benefits mentioned are increased productivity, cost savings, a sense of achievement and improved well-being.
Report
Share
Report
Share
Download to read offline
Recommended
TBCunCon: Power Networking by Ashley Rudolph
The document outlines a 4 step guide to power networking with the goals of expanding one's network and exploring opportunities. The steps are to research your interests and others beforehand, introduce yourself, discuss topics of mutual interest by learning about the other person and sharing an overview of yourself and goals, and avoid being discourteous by managing anxiety, being on time and prepared. The guide was presented by Ashley Rudolph at the UNCON 2012 conference on power networking.
Rethink & Challenge - How to reach goals on time
3 tips on how to form goals and reach them on time. At Minc Malmo for the E.ON Agile accelerator, 2016.
SCRUM: An Agile Methodology
Scrum is an agile methodology for project management derived from rugby. It uses short "sprints" typically 2-4 weeks to incrementally develop a product. The core roles are the Product Owner who manages requirements, the Scrum Master who facilitates the process, and a self-organizing Team. Each sprint involves planning, daily stand-ups, a retrospective, and a review where the working product is demonstrated.
From a drop to the river -- the evolution of some Scrummy Stuff!
1) The document summarizes the evolution of Scrum from its origins in 1986 to recent changes in 2013. It discusses how Scrum has been defined and implemented over time.
2) Key topics covered include the timeline of Scrum, debates over terminology like "Scrum" vs. "scrum," the removal of concepts like "tips" and "velocity" from the Scrum guide, and changes between the 2011 and 2013 versions of the guide.
3) The presentation emphasizes that there is no single "correct" way to implement Scrum and that teams should focus on the core roles, events, and artifacts rather than optional practices.
Agile creativity games
The document describes an Agile creativity workshop led by Mariya Breyter. The workshop includes warm-up games like having participants express creativity through images and challenging assumptions about restaurants. The main activity is an Agile storytelling game where participants write and unfold stories collaboratively. They then provide solutions. Additional proposed games include alphabet improv and creating Agile role descriptions in a catalog style. Takeaways highlighted are that creative play helps new perspectives, manages risk, unleashes potential, and is fun.
Agile Games - Playful approaches to agile principles
I facilitated this workshop during the 2nd Holtzbrinck Publishing Group's International CTO Conference 2013 in Berlin.
It's about Agile Games and how they revolutionise the way we train Agile Teams.
Short scrum games the efficient way to produce team cohesion
The document discusses using short Scrum games to build team cohesion. It provides examples of games that can be used such as the "Yes and, Yes but" game to convince others of using Agile games, the 6 hats brainstorming technique, introducing yourself and rumors about "Mr. Agile", writing goodbye or admiration letters, and having team members count to 40 as fast as possible by saying numbers in any order. The purpose of these games is to encourage interaction, communication, learning, breaking routine, motivation, and challenge to produce a cohesive team that can be highly productive.
Time management
This document discusses time management and provides tips for effectively managing one's time. It emphasizes setting goals and priorities, analyzing how time is currently spent, creating a time table, delegating tasks, focusing on important tasks, setting daily deadlines, developing skills, self-discipline, and managing one's speed and pace. The overall message is that time management is key to success and everyone has 24 hours each day, so using time judiciously through planning and organization can help achieve one's goals.
Recommended
TBCunCon: Power Networking by Ashley Rudolph
The document outlines a 4 step guide to power networking with the goals of expanding one's network and exploring opportunities. The steps are to research your interests and others beforehand, introduce yourself, discuss topics of mutual interest by learning about the other person and sharing an overview of yourself and goals, and avoid being discourteous by managing anxiety, being on time and prepared. The guide was presented by Ashley Rudolph at the UNCON 2012 conference on power networking.
Rethink & Challenge - How to reach goals on time
3 tips on how to form goals and reach them on time. At Minc Malmo for the E.ON Agile accelerator, 2016.
SCRUM: An Agile Methodology
Scrum is an agile methodology for project management derived from rugby. It uses short "sprints" typically 2-4 weeks to incrementally develop a product. The core roles are the Product Owner who manages requirements, the Scrum Master who facilitates the process, and a self-organizing Team. Each sprint involves planning, daily stand-ups, a retrospective, and a review where the working product is demonstrated.
From a drop to the river -- the evolution of some Scrummy Stuff!
1) The document summarizes the evolution of Scrum from its origins in 1986 to recent changes in 2013. It discusses how Scrum has been defined and implemented over time.
2) Key topics covered include the timeline of Scrum, debates over terminology like "Scrum" vs. "scrum," the removal of concepts like "tips" and "velocity" from the Scrum guide, and changes between the 2011 and 2013 versions of the guide.
3) The presentation emphasizes that there is no single "correct" way to implement Scrum and that teams should focus on the core roles, events, and artifacts rather than optional practices.
Agile creativity games
The document describes an Agile creativity workshop led by Mariya Breyter. The workshop includes warm-up games like having participants express creativity through images and challenging assumptions about restaurants. The main activity is an Agile storytelling game where participants write and unfold stories collaboratively. They then provide solutions. Additional proposed games include alphabet improv and creating Agile role descriptions in a catalog style. Takeaways highlighted are that creative play helps new perspectives, manages risk, unleashes potential, and is fun.
Agile Games - Playful approaches to agile principles
I facilitated this workshop during the 2nd Holtzbrinck Publishing Group's International CTO Conference 2013 in Berlin.
It's about Agile Games and how they revolutionise the way we train Agile Teams.
Short scrum games the efficient way to produce team cohesion
The document discusses using short Scrum games to build team cohesion. It provides examples of games that can be used such as the "Yes and, Yes but" game to convince others of using Agile games, the 6 hats brainstorming technique, introducing yourself and rumors about "Mr. Agile", writing goodbye or admiration letters, and having team members count to 40 as fast as possible by saying numbers in any order. The purpose of these games is to encourage interaction, communication, learning, breaking routine, motivation, and challenge to produce a cohesive team that can be highly productive.
Time management
This document discusses time management and provides tips for effectively managing one's time. It emphasizes setting goals and priorities, analyzing how time is currently spent, creating a time table, delegating tasks, focusing on important tasks, setting daily deadlines, developing skills, self-discipline, and managing one's speed and pace. The overall message is that time management is key to success and everyone has 24 hours each day, so using time judiciously through planning and organization can help achieve one's goals.
Ggc scrum i jun14 slides
This document provides an introduction to the Scrum framework presented by Céline Dedaj to the Geek Girls Carrots group. The workshop goals are to understand what Scrum is, how it works, why it is used, and get participant feedback. Scrum is explained as an iterative process involving sprints, daily stand-up meetings, sprint planning, reviews and retrospectives. Key Scrum roles of Product Owner, Scrum Master and cross-functional team are also outlined. The workshop concludes with a hands-on activity mimicking a sprint goal and process.
How to survive the zombie scrum apocalypse
A couple of years ago Christiaan Verwijs and Johannes Schartau coined the term ‘Zombie-Scrum’. What's it all about?
Well, at first sight Zombie Scrum seems to be normal Scrum. But it lacks a beating heart. The Scrum teams do all the Scrum events but a potential releasable increment is rarely the result of a Sprint. Zombie Scrum teams have a very unambitious definition of what ‘done’ means, and no drive to extend it. They see themselves as a cog in the wheel, unable and unwilling to change anything and have a real impact: I’m only here to code! Zombie Scrum teams show no response to a failed or successful Sprint and also don’t have any intention to improve their situation. Actually nobody cares about this team. The stakeholders have forgotten the existence of this team long time ago.
Zombie Scrum is Scrum, but without the beating heart of working software and its on the rise. This workshop will help you understand how to recognise the symptoms and cuases of Zombie Scrum and what you can do to get started to combat and treat Zombie-Scrum. Knowing what causes Zombie Scrum might help prevent a further outbreak and prevent the apocalypse
The Formula For Implementing Ideas - Montana College Access Network Conference
The document outlines a simple 5-step strategic planning process: 1) Focus on what needs to happen and how success will be measured; 2) Identify limiting factors; 3) Prioritize objectives and tackle the linchpin objective first; 4) Brainstorm solutions to limiting factors; 5) Implement the plan by starting small, reviewing progress daily, and maintaining relentless follow through. It emphasizes the importance of clarity on goals, obstacles, and next steps for overcoming stuck points to achieve success through diligent work and preparation.
Scrum and My ADHD Brain
In my software development career, some of my most productive work experiences happened while practicing Scrum. Scrum events & practices can help mitigate the challenges presented by the ADHD brain (or at least it has in my case).
Learn more about ADHD, Scrum, and how Scrum can help the ADHD brain. Even if your team doesn't practice Scrum, you will still find ways to improve your own performance.
Start Now Right Here - 10 stages of productivity
Not getting things done the way you could? Want to be more productive? And less stressed? Here is what you can do, how you get it to work and why it works this way!
My name is Chris, I'm a corporate psychologist. My job is to help people to live up to their potential. The 10 stages in this booklet summarize what my clients found the most helpful advice to get organized.
Scrum Master as a Facilitator
Slides from Scrum Master as a Facilitator. During this workshop we learn and practice some basic meeting facilitation skills, focus on tips and tricks for Scrum ceremonies, and simulate a Scrum cycle using our learning
Sprint calendar
This document provides a sample sprint calendar that outlines common scrum events over the course of two weeks. It includes sprint planning, daily scrum of scrums, story review, sprint review, and sprint retrospective. The calendar shows when these events would occur each week to help the team plan and coordinate their work.
Agile retrospectives
The document discusses the importance of the retrospective meeting in Scrum. It notes that early versions of Scrum did not include retrospectives and that they are important for teams to inspect and adapt their processes. Retrospectives provide an opportunity for teams to reflect on what went well and what can be improved in the last sprint and develop an action plan to become more effective. They should be time-boxed, focus on constructive feedback rather than blame, and actively engage the whole team, Scrum Master, and Product Owner to drive process improvements.
Project Managers, our World is Changing!
LET'S TALK LEADERSHIP!
As more and more organisations are adopting Agile software development practices, many project managers may be asking themselves how to adapt to this new trend. Becoming a Scrum Master might be the obvious solution, but are there other roles in the Agile frameworks that are suitable for a Project Manager to adopt? Should they become Product Owners?
WHAT YOU WILL LEARN
PALO IT shared its experience in running Agile projects, including the differences between Project Managers, Scrum Masters, and Product Owners. We covered the scope of each role, the required skills and mindsets and how these affect the relationship with the broader development team. We also rovided insight on how to effectively transition from a classical Project Manager role to an Agile one.
Audience
> Project Managers & Senior Managers
> Scrum Masters & Product Owners
> Developers
> HR Professionals
> Anyone with experience of working with a development team.
1- Scrum Insights.pptx
Time-boxing is a Scrum strategy that involves completing activities within a fixed, limited time period. It helps ensure teams focus only on priorities and don't overthink tasks. While difficult at first, time-boxing becomes easier with discipline. Scrum recommends time-boxing several events, such as daily stand-ups lasting 15 minutes, 1-month sprints, and planning and retrospective meetings lasting a few hours each.
How to get things done & take control of time, tasks, & priorities
The document provides tips for improving productivity and time management. It emphasizes setting goals and priorities, planning your day, focusing on one task at a time without distractions, creating systems and processes to simplify tasks, and achieving a state of "flow" at work by fully immersing yourself in your tasks. It also stresses the importance of distinguishing between tasks that are truly important versus less important, and focusing your efforts on what really matters.
Ggc scrum i jul14 slides
This document provides an introduction to the Scrum framework for agile software development. It describes Scrum roles like the Product Owner, Scrum Master, and Team. It outlines Scrum events like the Sprint Planning meeting, Daily Scrum, Sprint Review, and Sprint Retrospective. It also gives an example of running a mini-Sprint with the goal of moving balls of toilet paper between bags to demonstrate how Scrum works in practice.
TIME MANAGEMENT swaraj.pptx
This document discusses time management and its importance. It defines time management as managing one's own time without wasting it and also managing others' time. Good time management is important for better stress management and a smoother life. The process involves costing time, tracking activities, setting goals, planning, scheduling and prioritizing. Techniques include setting reminders, creating a daily planner, time limiting tasks and blocking distractions. Mistakes include failing to prioritize, improper planning and overcommitting. Advantages are achieving goals faster and completing tasks on time while disadvantages include missed opportunities and increased stress from poor time management.
Time management
This document provides an overview of a time management training program. It discusses the importance of time management and introduces three skills for prioritizing effectively: 1) create a master plan that captures all tasks, 2) schedule important "big rock" tasks and don't get bogged down by less important "gravel" tasks, and 3) protect your plan by pausing to evaluate what is truly important when new tasks arise. The training aims to help participants better manage their priorities and focus on the things that matter most through applying these time management skills back in the workplace.
Scrum101
This document provides an overview of Scrum, an agile framework for managing product development. It discusses the Scrum roles of Product Owner, Team, and Scrum Master. The key Scrum ceremonies are planning, daily stand-ups, sprint reviews, and retrospectives. Scrum uses short iterations called sprints to incrementally deliver working software. The document recommends starting with a short initial sprint length and identifying the Product Owner, Scrum Master, and cross-functional Team.
Scrum Training for Key Ingredient Employees
The document provides an overview of Scrum training. It defines Scrum as an iterative and incremental Agile project management framework. It describes the roles in Scrum including Product Owner, ScrumMaster, and self-organizing cross-functional teams of 7 plus or minus 2 members. It also outlines the core Scrum ceremonies like sprint planning meetings, daily standups, sprint reviews, and retrospectives. Finally, it discusses estimating techniques, common Scrum artifacts, best practices, and challenges of implementing Scrum.
Increasing your productivity
1. The document discusses improving productivity by planning tasks, taking action to complete tasks, motivating oneself, and avoiding procrastination and stress.
2. It recommends making lists of prioritized tasks with timeframes, doing important tasks when energy is highest, and rewarding oneself for completing tasks.
3. Avoiding distractions, owning responsibility, and changing reactions to stressors can help boost productivity.
Dev o'Clock: wdrożenia e-Commerce - Agile in e-Commerce projects
Więcej informacji o meetupie na:
- https://www.meetup.com/pl-PL/Dev-oclock/
- https://www.facebook.com/XCodingITStudio/
Time Management In The Office And Out On
This document discusses time management and provides tips for improving time management skills. It begins with several quotes about time and discusses the 80:20 rule, which is that 80% of effort only generates 20% of results. It then lists the top 10 time wasters and provides assessments and articles on goal setting, prioritization, procrastination, scheduling, and managing distractions. The document stresses the importance of managing time effectively and provides strategies for doing so, including setting goals, prioritizing tasks, avoiding multitasking, and reducing stress.
More Related Content
Similar to Scrum in your personal life
Ggc scrum i jun14 slides
This document provides an introduction to the Scrum framework presented by Céline Dedaj to the Geek Girls Carrots group. The workshop goals are to understand what Scrum is, how it works, why it is used, and get participant feedback. Scrum is explained as an iterative process involving sprints, daily stand-up meetings, sprint planning, reviews and retrospectives. Key Scrum roles of Product Owner, Scrum Master and cross-functional team are also outlined. The workshop concludes with a hands-on activity mimicking a sprint goal and process.
How to survive the zombie scrum apocalypse
A couple of years ago Christiaan Verwijs and Johannes Schartau coined the term ‘Zombie-Scrum’. What's it all about?
Well, at first sight Zombie Scrum seems to be normal Scrum. But it lacks a beating heart. The Scrum teams do all the Scrum events but a potential releasable increment is rarely the result of a Sprint. Zombie Scrum teams have a very unambitious definition of what ‘done’ means, and no drive to extend it. They see themselves as a cog in the wheel, unable and unwilling to change anything and have a real impact: I’m only here to code! Zombie Scrum teams show no response to a failed or successful Sprint and also don’t have any intention to improve their situation. Actually nobody cares about this team. The stakeholders have forgotten the existence of this team long time ago.
Zombie Scrum is Scrum, but without the beating heart of working software and its on the rise. This workshop will help you understand how to recognise the symptoms and cuases of Zombie Scrum and what you can do to get started to combat and treat Zombie-Scrum. Knowing what causes Zombie Scrum might help prevent a further outbreak and prevent the apocalypse
The Formula For Implementing Ideas - Montana College Access Network Conference
The document outlines a simple 5-step strategic planning process: 1) Focus on what needs to happen and how success will be measured; 2) Identify limiting factors; 3) Prioritize objectives and tackle the linchpin objective first; 4) Brainstorm solutions to limiting factors; 5) Implement the plan by starting small, reviewing progress daily, and maintaining relentless follow through. It emphasizes the importance of clarity on goals, obstacles, and next steps for overcoming stuck points to achieve success through diligent work and preparation.
Scrum and My ADHD Brain
In my software development career, some of my most productive work experiences happened while practicing Scrum. Scrum events & practices can help mitigate the challenges presented by the ADHD brain (or at least it has in my case).
Learn more about ADHD, Scrum, and how Scrum can help the ADHD brain. Even if your team doesn't practice Scrum, you will still find ways to improve your own performance.
Start Now Right Here - 10 stages of productivity
Not getting things done the way you could? Want to be more productive? And less stressed? Here is what you can do, how you get it to work and why it works this way!
My name is Chris, I'm a corporate psychologist. My job is to help people to live up to their potential. The 10 stages in this booklet summarize what my clients found the most helpful advice to get organized.
Scrum Master as a Facilitator
Slides from Scrum Master as a Facilitator. During this workshop we learn and practice some basic meeting facilitation skills, focus on tips and tricks for Scrum ceremonies, and simulate a Scrum cycle using our learning
Sprint calendar
This document provides a sample sprint calendar that outlines common scrum events over the course of two weeks. It includes sprint planning, daily scrum of scrums, story review, sprint review, and sprint retrospective. The calendar shows when these events would occur each week to help the team plan and coordinate their work.
Agile retrospectives
The document discusses the importance of the retrospective meeting in Scrum. It notes that early versions of Scrum did not include retrospectives and that they are important for teams to inspect and adapt their processes. Retrospectives provide an opportunity for teams to reflect on what went well and what can be improved in the last sprint and develop an action plan to become more effective. They should be time-boxed, focus on constructive feedback rather than blame, and actively engage the whole team, Scrum Master, and Product Owner to drive process improvements.
Project Managers, our World is Changing!
LET'S TALK LEADERSHIP!
As more and more organisations are adopting Agile software development practices, many project managers may be asking themselves how to adapt to this new trend. Becoming a Scrum Master might be the obvious solution, but are there other roles in the Agile frameworks that are suitable for a Project Manager to adopt? Should they become Product Owners?
WHAT YOU WILL LEARN
PALO IT shared its experience in running Agile projects, including the differences between Project Managers, Scrum Masters, and Product Owners. We covered the scope of each role, the required skills and mindsets and how these affect the relationship with the broader development team. We also rovided insight on how to effectively transition from a classical Project Manager role to an Agile one.
Audience
> Project Managers & Senior Managers
> Scrum Masters & Product Owners
> Developers
> HR Professionals
> Anyone with experience of working with a development team.
1- Scrum Insights.pptx
Time-boxing is a Scrum strategy that involves completing activities within a fixed, limited time period. It helps ensure teams focus only on priorities and don't overthink tasks. While difficult at first, time-boxing becomes easier with discipline. Scrum recommends time-boxing several events, such as daily stand-ups lasting 15 minutes, 1-month sprints, and planning and retrospective meetings lasting a few hours each.
How to get things done & take control of time, tasks, & priorities
The document provides tips for improving productivity and time management. It emphasizes setting goals and priorities, planning your day, focusing on one task at a time without distractions, creating systems and processes to simplify tasks, and achieving a state of "flow" at work by fully immersing yourself in your tasks. It also stresses the importance of distinguishing between tasks that are truly important versus less important, and focusing your efforts on what really matters.
Ggc scrum i jul14 slides
This document provides an introduction to the Scrum framework for agile software development. It describes Scrum roles like the Product Owner, Scrum Master, and Team. It outlines Scrum events like the Sprint Planning meeting, Daily Scrum, Sprint Review, and Sprint Retrospective. It also gives an example of running a mini-Sprint with the goal of moving balls of toilet paper between bags to demonstrate how Scrum works in practice.
TIME MANAGEMENT swaraj.pptx
This document discusses time management and its importance. It defines time management as managing one's own time without wasting it and also managing others' time. Good time management is important for better stress management and a smoother life. The process involves costing time, tracking activities, setting goals, planning, scheduling and prioritizing. Techniques include setting reminders, creating a daily planner, time limiting tasks and blocking distractions. Mistakes include failing to prioritize, improper planning and overcommitting. Advantages are achieving goals faster and completing tasks on time while disadvantages include missed opportunities and increased stress from poor time management.
Time management
This document provides an overview of a time management training program. It discusses the importance of time management and introduces three skills for prioritizing effectively: 1) create a master plan that captures all tasks, 2) schedule important "big rock" tasks and don't get bogged down by less important "gravel" tasks, and 3) protect your plan by pausing to evaluate what is truly important when new tasks arise. The training aims to help participants better manage their priorities and focus on the things that matter most through applying these time management skills back in the workplace.
Scrum101
This document provides an overview of Scrum, an agile framework for managing product development. It discusses the Scrum roles of Product Owner, Team, and Scrum Master. The key Scrum ceremonies are planning, daily stand-ups, sprint reviews, and retrospectives. Scrum uses short iterations called sprints to incrementally deliver working software. The document recommends starting with a short initial sprint length and identifying the Product Owner, Scrum Master, and cross-functional Team.
Scrum Training for Key Ingredient Employees
The document provides an overview of Scrum training. It defines Scrum as an iterative and incremental Agile project management framework. It describes the roles in Scrum including Product Owner, ScrumMaster, and self-organizing cross-functional teams of 7 plus or minus 2 members. It also outlines the core Scrum ceremonies like sprint planning meetings, daily standups, sprint reviews, and retrospectives. Finally, it discusses estimating techniques, common Scrum artifacts, best practices, and challenges of implementing Scrum.
Increasing your productivity
1. The document discusses improving productivity by planning tasks, taking action to complete tasks, motivating oneself, and avoiding procrastination and stress.
2. It recommends making lists of prioritized tasks with timeframes, doing important tasks when energy is highest, and rewarding oneself for completing tasks.
3. Avoiding distractions, owning responsibility, and changing reactions to stressors can help boost productivity.
Dev o'Clock: wdrożenia e-Commerce - Agile in e-Commerce projects
Więcej informacji o meetupie na:
- https://www.meetup.com/pl-PL/Dev-oclock/
- https://www.facebook.com/XCodingITStudio/
Time Management In The Office And Out On
This document discusses time management and provides tips for improving time management skills. It begins with several quotes about time and discusses the 80:20 rule, which is that 80% of effort only generates 20% of results. It then lists the top 10 time wasters and provides assessments and articles on goal setting, prioritization, procrastination, scheduling, and managing distractions. The document stresses the importance of managing time effectively and provides strategies for doing so, including setting goals, prioritizing tasks, avoiding multitasking, and reducing stress.
Similar to Scrum in your personal life (20)
The Formula For Implementing Ideas - Montana College Access Network Conference
The Formula For Implementing Ideas - Montana College Access Network Conference
How to get things done & take control of time, tasks, & priorities
How to get things done & take control of time, tasks, & priorities
Dev o'Clock: wdrożenia e-Commerce - Agile in e-Commerce projects
Dev o'Clock: wdrożenia e-Commerce - Agile in e-Commerce projects
Scrum in your personal life
- 5. SCRUM
- 6. HOW?
- 7. GROUND RULES Follow 5 Events Timeboxing
- 8. SCRUM ROLES Scrum Master Product Owner ScrumTeam
- 9. TOOLS Virtual board and physical board
- 11. 1. SPRINT PLANNING Story Point Estimation Set Commitment
- 12. 2. DAILY STAND UP
- 14. 3. BACKLOG GROOMING 2 Remove tasks as much as possible Assign to her Place Sprint Retro Items into Backlog 1
- 15. 4. SPRINT REVIEW Appreciation Velocity Go for dinner
- 16. 5. SPRINT RETRO Appreciation Velocity Go for dinner What went well What didn’t Action points
- 17. CHALLENGES 1. Constantly act as an evangelist 2. Bring in variety Lack of motivation
- 18. BENEFITS SAVE $$ Achievements Peaceful Happier
- 19. SCRUMIFY
- 20. SCRUMIFY
- 21. SCRUMIFY
- 22. SCRUMIFY NOTES Review and measure velocity Estimate Efforts towards the goal
- 23. “What kind of personal goals can be scrumified?”
- 24. SUMMARY Why I started scrumification in my personal life? How did I implement? How to scrumify and achieve any personal goal? Benefits of to scrumification
- 25. SCRUMIFY A PERSONAL PROJECT
- 26. THANKS FROM SAFIQUE A FARUQUE Product Manager, iMoney Group