You may have heard about the #NoEstimates movement, and even #NoProjects. Both of those concepts challenge the assumptions behind two key aspects of delivering software. But what about the process itself? Do we even need approaches like Scrum, Kanban or XP - let alone SAFe, LESS, NEXUS, DAD - in order to be successful? Is following a pre-defined process helpful at all? Is there a simpler way to be effective?
This session examines the two key principles common to all successful software delivery approaches and builds out based on the experience of the participants. Like #NoEstimates and #NoProjects, the name doesn’t really mean to eliminate process altogether, but rather to build a process that works for your team, in your business domain, with your technology stack.
Unless the systems you build are developed with concurrency in mind, they probably do not take full advantage of modern multi-core CPUs. Concurrent programming facilitates the use of multiple processors, but is difficult to implement using traditional approaches. Fortunately, new approaches taken by functional languages have begun to address these difficulties.
In this highly interactive session, volunteers from the audience will help present the classic problems with concurrent programming. Traditional solutions to these problems will be presented, as well as new approaches available from functional languages such as Erlang, Clojure, and Haskell. With this knowledge you will begin to think about software architecture differently, and may even decide to introduce concurrency into your next project.
Sounds like the start of a good story, right? The common problem facing Agile practitioners isn’t the basics – it’s how it all fits together. Is the team project focused or product focused? How does an Agile project get started? What is the value of sprint zero? How do you pull a sprint back from the brink of failure? How do we show sprint status? How do we know we’ll actually release on time? Let’s belly up to our favorite watering hole, Bar Agilicious, and commiserate through a typical Agile project. No Agile pain point is off limits - planning, epics, themes, user stories, backlogs, spikes, analysis, status, documentation and risk. Raise a glass to Agile and how the Business Analyst and Project Manager fit into Agile environments to add value and deliver a successful product, together.
Scrum is one of the oldest agile frameworks, and its set of practices are the ones most agile teams use today. For many people, Scrum is their introduction to agile.
Unfortunately, Scrum’s age and popularity have allowed a lot of misunderstandings to develop, which has resulted in some people not benefitting from the framework as much as they could.
As the Product Owner of the Scrum.org Professional Scrum courses, Steve Porter has broad experience educating people on the ins and outs of Scrum. From simple confusion about the size limits of a Scrum Team (there are none) to more complex issues around how much control a Development Team has over its work, Steve’s seen the many ways Scrum gets misinterpreted.
If you’re a beginner looking for ways to maximize the benefits you get from Scrum, this session will show you how to avoid the common pitfalls that could derail your efforts. If you’re a Scrum expert, you’ll gain new insights into this tried and true agile framework.
Too often teams spend more time choosing a “process” than working in it. They do research, debate, evaluate, etc., rather than just getting going. If you search on Scrum vs. Kanban, you will get hundreds of hits; however, it doesn’t have to be that way.
Scrum is a simple framework from which process evolves. Kanban is a strategy made up of a set of practices that helps workflow. Building a bridge between the two help teams deliver better products to market.
Join Steve Porter as he introduces Kanban practices that Scrum Teams can add to help improve their effectiveness and efficiency. During Steve’s session, you will learn how to use Kanban practices, including visualization of workflow, limiting work in progress (WiP), active management of work and many more to help continually inspect and adapt your workflow; all without losing the benefits of Scrum. You will leave understanding how building a bridge between Scrum and Kanban will help your team deliver better products to the market!
What does agile mean? Do you “do” agile or “be” agile? Which framework should you use? Can they be combined? Do I have to stand up and tell stories everyday? I will get down to the basics and help you wade through the alphabet soup of frameworks and certifications to understand what it really means to “be” agile: Collaboration, Transparency, Rapid Feed, and Continuous Improvement.
When we turn 18 we close the door on childhood and enter adulthood. You’re no longer a dependent for tax purposes, you can vote, and you can even run for office…at least in Canada you can. This year, Agile turned 18 and along with that came a slew of blog posts about the history of agile, how it came to be and what it has become. The ‘Take Agile Back’ movement, #NotMyAgile hashtag, and Agile Uprising has been shifting the conversation back towards the original intent of Agile because many believe the state of agile today is nothing more than a certification pyramid scheme and an excuse to sell tools and consulting. In this session, we’ll explore patterns of the last 18 years using data from all 13 Version One State of Agile survey’s and understand that where we are today is as natural as the evolution of any set of ideas.
We can choose to fight against the evil tyranny of the business of agile, criticize the latest buzzwords, or consciously choose to let our personal values and principles serve as inspiration to those around us, because let’s face it, who we are as people and our values have existed for much longer than the Agile Manifesto.
After a year of working full time as a developer, Jessica was lost. She was anxious about all the unknowns that working in tech brings; from her career path to understanding the intricacies of the techstack, worrying about writing clean enough code, and bugs in live. In addition, she would worry about code when she went home for the night, and found herself depressed and confused in other aspects of her life.
When she was crying uncontrollably on the couch of her first physiologist appointment, Jessica’s Dr put it in terms she would understand, “You just have some bad programming in your brain. You need to swap out the software for something with more joy, self love and confidence so you will feel better.” This was a turning point, that idea started to grow - just like the plot of Inception.
Jessica took that idea and ran with it. Learning about meditation, studying life coaching and shifting mindsets and creating a whole new outlook on her life. She also took control over her anxiety and minimized it.
We know by now that tech can isolate us from human connection and make us feel anxious and addicted. What is it doing to those of us who work with technology in high pace environments as part of our daily responsibilities?
Jessica will share with you her algorithm for anxiety and the program she swapped it for to feel better. Seeing how an anxious computer acts will help you understand your own anxious thinking and adjust your behaviour to create a happier life.
Whether you have social anxiety, work stress, or just want to understand anxiety better so you can empathize with other humans, this talk is for you.
In this introduction, we’ll look at how we can use Kanban method to understand the flow of value to customers, and how we might improve how work gets done, in a humane way. The foundations will be covered to set participants up to being to apply it in their own environments.
While this session has been tagged for beginners, it’s likely those more experienced will also have insights they can take away. We’ll be covering the foundations of Kanban, understanding that not all work is created equal (classes of service), and how to collect and use data to inform improvements based on the nature of the work people are doing today.
One recent definition of legacy code is code without automated unit tests. Adding new features or fixing bugs in legacy code carries a high risk of introducing new bugs. Worse, it makes software developers afraid to improve the code.
However, if the code is working today, it is often possible to leverage the knowledge encoded in the working application with Golden Master testing, also known as characterization tests.
In theory this is easy - just change the code and compare its behavior with the old code. The hard part is finding the right place to compare.
In this session I’ll demonstrate several recent examples of using this technique with good results. The surprises and failures will be at least as instructive as the successes.
In the second half of the session we’ll workshop and discuss real examples from the audience.
Your mind is under attack everyday by stressors which cause fear, learned helplessness, anger, negativity, apathy, sadness, anxiety, and depression, and these negative feelings can accumulate and fester. How are you going to be productive, persistent, creative, analytical, inspired, focused, optimistic, and enthusiastic when your mind is constantly under the attack of stress? If success is 25% skill and 75% mental, why don’t we dedicate any training or time to building resilience to support our mental health?
In this presentation we'll discuss how you can build mental resilience and better deal with stressful situations. Key talking points are:
What is a data product, and what is the role of a Product Manager or Product Owner in the world of data warehousing, data science, and data systems?
At SkipTheDishes, we aim to apply product management principles and frameworks around our data teams. In January 2019, a Product Team was established to organize, prioritize and build quarterly objectives to support our Engineering Teams. By removing the noise of backlogs and providing business context through the workflow, we were able to focus on providing value, and in turn, produce work that was more rewarding to our development teams. Specific examples will cover how we moved our entire data pipeline from AWS to Google Big Query, and how we operate under two global platforms. We will discuss how we invoke a mix of waterfall and agile principles to make it all work.
The results of agile projects have spoken for themselves over the years and it’s no coincidence that so many companies have adopted agile to power their projects. Budgeting for these projects can be challenging and not knowing EXACTLY what you are building from the outset can further complicate things. Let’s debunk one of the myths that you can’t accurately budget for agile projects together and explore some of the best practices of keeping your agile projects on track and within budget.
I am a father of two. I am a successful Cloud Solutions Architect in higher education. I have a mortgage, swimming lessons, and daycare bills. I am also going to make and sell my first video game, tentatively named Vagabond, the player takes the role of a hitchhiker meeting interesting people and going on an amazing adventure.
My situation, dreams, and story are not unique. Here’s the catch: I’m not going to risk my security, health, or family’s well being to make my dream a reality. Even then, Vagabond, a hitchhiking video game complete with world maps, rich narrative, and ability to add community driven content, will be for sale by the end of 2019.
Impossible, you say? I beg to differ. By January 2019, the first playable version was released. In February, we fleshed out maps, content, and player actions. By March, we added richer graphics and greatly improved player control. Milestones are set, work gets completed, marketing efforts continue, and the game is coming.
But how, you ask? In this session, we will walk through my journey so far, and share the lesser known stories of those who have done the same. I will share how I have applied lean development practices from my day job to ensure the right features get the time required. We will review how I found time in my real life to make games by using tried and true time management systems rather than cancelling swimming lessons, skipping the gym, or (and most importantly) quitting my day job.
According to this year’s State of Agile survey, the most common success measure for agile initiatives, at 53%, is on-time delivery. But if agile teams can choose how much work they take into a sprint, how can teams be sure of delivering pre-committed scope on time and on budget? There is clearly more to agile delivery than product owners ordering a backlog of work for teams to work on. Epic budgeting is one practice that allows the product owner to steer a product across the line, delivering the expected scope on time by managing scope creep or an unsustainable focus on the perfect over the pragmatic. During this session learn about how product owners and their teams work towards a fixed date or budget by applying double loop learning to epic sizing and breakdown. Expect some tales from real companies and a few light hearted moments. And I’m at least 53% certain we will finish on time!
We use the Internet today for practically everything. We need our eyes and hands to interact with web pages and apps. What if someone lacks or loses their ability to see or use their hands – temporarily or permanently? Can they still access the Internet? The answer is “Yes”.
Join Sam to take a peek at different technologies such as screen reader, screen magnifier, speech input, onscreen keyboard, head mouse, and switches used by people with disabilities to interact with the Internet. Of course, websites and apps need to be created with accessibility in mind for these technologies to work well.
Watch video clips from Sam’s sessions with people with different visual and physical disabilities using assistive technologies.
Learn simple and paradigm shifting design techniques from Senior UX Professional Ash Banaszek. This talk comes from hearing folks exasperated from making their project deadlines and budgets, only to fail with users upon launch. A lot of times, this has to do with missed requirements and a stubborn conviction to stick to a plan even if the design is untested. Ash will share with you the design techniques used to create effective user interfaces through sketching, mind stretching, and iteration. Further, you’ll learn how to conduct black hat sessions to shake out missed requirements, mismatched UI expectations, and get much needed buy in from project stakeholders.
With a world that wants everything faster and faster, Ash will give you simple techniques that make a big difference; thus enabling you to think through multiple solutions, get yourself un-stuck from a single idea, iterate on your designs, and rally your team around this process.
Ready, get set, FAIL!.. The faster you fail, the faster you can succeed.
Most of us have heard the mantra, “Slice your User Stories as thin as possible!” In my travels as a coach since the early 2000’s, however, I’ve rarely seen stories that truly are thin. What are these rare creatures? Why don’t I see more of them? Having good User Stories is crucial to the success of teams using them as the means for determining what needs to be built to fulfill a customer’s need. Having thinly sliced stories is even more important!
This workshop provides a level set on what stories are and explores why slicing stories very thin is important, what benefits thin slicing provides, and how to do it. Through a combination of examples and practical application in the session, you’ll leave with slicing techniques that you can apply at your very next planning or refinement session.
What does it mean to have leadership at every level of an organization? How do you create aligned autonomy in your team or organization? This talk connects the philosophy of intent-based leadership with practices that enable you to realize the benefits of aligned autonomy, regardless of where your name is in your org chart. By discovering virtual safety nets and vision balloons, you’ll learn how to pragmatically establish psychological safety and alignment of purpose, two of the core traits of high-performing teams.
You’re using Agile - great! But if you’re a product manager or executive, how do you determine what your Agile teams should be working on? Learn about how RAPID RTC has used the Scaled Agile Framework to handle feature prioritization, manage large programs and epics, and organize teams.
An article published in Forbes.com predicts 83% of enterprise workloads will be in the cloud by 2020. The “cloud revolution” is underway right now!
Manitoba Blue Cross is moving nearly 100% of our servers and infrastructure to the AWS platform. The project has been very rewarding but not without its challenges. In this talk I plan to discuss our business reasons for migrating, our strategy, architecture, team, work and the major challenges we have faced.
One of the toughest roles in an Agile squad is that of the Product Owner. Needing to understand what’s being built, why it’s being built, what problem it’s solving, and the diverse and disparate needs from customers, business, compliance, risk, legal, audit, and just about everyone else, there’s a lot of pressure on understanding and bringing together these perspectives.
However, being a Product Owner is one of the most rewarding jobs. Join a successful Product Owner with a range of real-world experience, and learn from his journey, both his successes and failure, as he’s worked in a variety of industries to bring small, frequent delivery of valuable software to those he’s worked with.
You’ll hear how he’s managed and brought collaboration to the teams he’s been working with, along with all other stakeholder groups required to solve real-world problems and deliver a measurable return on investments of valuable working software on a regular basis. Find out what patterns of behaviour have worked for John during his work, and take away some ideas you might be able to apply to your own work.
Pushing software out ‘to production’ and in front of your users is a critical step and something we should do a lot. In this session, you will learn why this ability is important, and the kinds of things that your team will need to make it happen. This is not a highly technical session, and won’t cover the details or implementation steps of the tools you might use, but it does touch on some of those tools, and discusses the importance of the capability, why your team should have the capability, the things that might need to be in place to make it happen, and the benefits the capability might bring.
Regardless of your role, you can help to move your team forward. If you’re a developer, your development practices directly contribute to capabilities in this area of course, and those practices will also be reviewed as apart of this presentation. Even as a Product Owner, Stakeholder, or Manager, you can push, encourage, and enable a team to get to the point of being able to push software out regularly. In this session, you will learn about what you can ask for, what’s possible, and why you should ask for it.
This presentation will reference a specific example case study where automation and deployment are a core part of product development, and where a ‘developer only’ team has ensured delivery quality on a highly available complex platform through continuous integration, continuous delivery, and test automation.
Why did the programmer run out of shampoo? The instructions on the bottle were: Lather. Rinse. Repeat.
In in this session we’ll look at how to harness the power of recursion to make our lives easier. We’ll look at primitive recursion with Peano arithmetic. Next we’ll look at the most powerful Inductively defined data structure in the world, the con list. Lastly we’ll look at how to solve problems using structural and generative recursion. You’ll walk away with a new understanding of how to break down a problem using recursion.
UX research is often relied upon to gather iterative feedback in the design and development process, but not every team has a research specialist. It can be hard to know what kind of research to do when and easy to assume that as designers or developers you’ll be able make the best call for your user. However, leaving user research out of your development process leaves room for you to spend time working on a feature that isn’t a priority for your target customers or implementing a feature ineffectively.
Come to this session to get an overview of the key goals of user research, the key methodologies that any team member can employ, concrete tips for how to select the best method given your goal, and advice to craft your research plans the best way to get the information you’re looking for. This session will be most useful for those interested in UX research but don’t have formal training, such as UX designers, developers, or product managers.
Join three of Northfield IT's veteran practitioners as we discuss the operational challenges you need to consider in order to support your application after it is are in the hands of your customers.Northfield is a infrastructure managed service that embraces devops culture and has years of experience on the front line of digital operations.Our panel hosts bring years of insights to share with you about lessons learned in the trenches while supporting products after delivery teams think they are "done".
Wondering what ATDD is? How about CI/CD? The benefits of Refactoring? What about Simplicity in code design? No matter what your role is, understanding how we want to deliver great quality code to our customers can be learnt using Lego. If you’re a developer or tester today, we’ll cover some modern development practices that can help improve current development approaches, in a language that might just help you explain it to others. And, if you’re not directly touching code, you’ll gain an understanding for some of the challenges and the impact you can have on the development of great solutions for your customers and stakeholders. And, since we’ll be doing it all with Lego, no coding experience is required.
The days of a genius developer working alone in a basement are behind us. Working in technology now requires a team approach and that means a set of skills that extend past writing code. Everyone in technology needs a playbook for interacting with stakeholders, sponsors, and your own team members
This presentation is to inspire you to see the social side of work. Are you in a leadership role? Are you the spokesperson for your team? Do you find gaining alignment with stakeholders a challenge? This session is designed to unlock the tools you need to empower your team, help gain alignment, and be the champion your team deserves.
Aristotle once said “Well begun is half done.” On agile teams, we often use user stories to track our value offering through development. So if we do a good job on the stories, our teams will be halfway to done!
User stories need 3 C’s to start the team on the right foot: Card, Conversation, and Confirmation. How are you doing on the Confirmation/Acceptance criteria part? No, really, how well do you think you do on those?
If you struggle when you write acceptance tests for your user stories, fear not! There is help. Instead of telling you about an analysis or design model to help you think of tests, come to this session and we will dance our way to insight and shared understanding. We will demystify terms like: acceptance criteria, ATDD, BDD, and Gherkin notation; and leave you with a memorable way to think of good tests to impress your teams. Come discover how learning can be fun and insightful.
If you could have only one agile feedback loop, what would it be? This session shows how vital to learning, improvement and engagement the retrospective is. The session covers basics such as facilitation, the five stages and psychological safety, as well as some ideas for longtime practitioners, such as: * Cadence decoupling * Pull-based retrospectives * Retrospectives for introverts
We’ll even do some role-play to demonstrate patterns and anti-patterns.
Would you bet your career on guessing that you know how to deliver high quality solutions? Do you depend on blind trust or luck to find all the critical bugs and defects before the scheduled release date? Worried that luck will run out and someone might get hurt?
They say it takes a village to raise a child, and quality software is no different. You need different perspectives and approaches to see and fill in the gaps that will lead to bugs and failures in production. “Automate all the things” doesn’t tell you what to automate. If you automate garbage, you end up with fast trash. You will miss important things if you don’t know what to look for or how you will be blinded from seeing the problems right in front of your eyes.
In this interactive session, we will explore the key concepts, models and tools (a.k.a. secrets) used by high-performing testing specialists around the world. There is a science before there can be art and magic. Come learn how to make quality happen on purpose.
Anyone who can carry a conversation can interview users, right? Not so. Gaining insight into user requirements, needs, and frustrations is a nuanced process. Without the proper training, even well-meaning researchers can lead, bias, and manipulate users into getting the answers researchers want–instead of getting the real story needing to be told. In this talk, Ash will guide you through the basics of conducting user interviews: * Picking the right interview type * Asking the “right” questions * Do’s/Don’ts of Interacting with Users * How to interpret your results User research is difficult to do well and requires lots of practice. After this talk, you should have the foundation you need to take the next steps to better user interviews.
Many different styles and frameworks of Agile Software Development have been developed since The Agile Manifesto was written. A prevailing goal across the alternatives is to promote peace of mind for customers, users, and the development team. Unfortunately, it is all too common for Agile teams to experience turbulence rather than tranquility.
In this thought-provoking presentation, seven guiding principles that promote peace of mind will be presented. These principles provide a framework for discovering new processes and practices that will improve team productivity, communication, and performance. The goal for practitioners is to find, identify, and implement practices that work in their environment and make people awesome.
Is your experience with Agile practices more characterized by tranquility or turbulence? Regardless, these seven principles will guide you to greater peace of mind.
SkipTheDishes uses Jenkins massively for build and deploy their projects and run adhoc jobs. The total of Jenkins jobs was almost 3700 jobs and we needed a Java application to create and maintain these Jobs. This architecture limited us to create new type of Jobs because we used mostly “Maven Job Projects” and “FreeStyle Job Projects”. We had to modernize our CI platform with almost Zero impact to the team development and introduce a completely new paradigm for Jenkins Jobs in the company.
Creating a backlog of user stories is pretty straight forward but it doesn’t help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan the project, and how to visualize progress. The traditional backlog is simply too flat and often too long to help you see the bigger picture and make good decisions. User Story Mapping helps simplify all of these common project issues. By adding a third dimension to your backlog, your team will make better decisions about priorities, scope, and planning while improving your ability to visualize progress. In this practical session I’ll teach you the basics of user story mapping before walking you through some examples.
The Lean Startup approach is becoming increasingly popular among companies of all sizes and organizations of all kinds. At it’s simplest, the Lean Startup approach is a way to apply the scientific method across business and product development. So what if you aren’t a startup, or even a for-profit institution? What if your budgets and resources are limited and your team is skeleton?
Turns out, the Lean Startup framework calls for very budget friendly UX-friendly processes, such as Build Measure Learn cycles, in which you collect small amounts of iterative feedback and focusing on building a Minimal Viable Product (MVP) required for doing so.
In this session, I’ll provide an overview of the Lean Startup and Build Measure Learn frameworks, description of types of MVPs and how to choose, instruction to set up effective experiments and hypotheses, and practical tips to incorporate these elements of Lean Startup practices to improve overall experience for teams and users.
Well. It finally happened. All that agile talk is landing in YOUR department. And YOU are about to “go agile.” What does it mean? There are ceremonies (do I need special robes or something?). Nah, let’s figure this all out (and no, we aren’t just talking waterfall with scrummy words)
You’ve been hearing about Agile for what seems like years. You understand the basics like ceremonies, roles, velocity, sprints and such. And then, it happens. Your department “goes Agile.” It’s no longer about the theory of Agile, but how to make Agile work where you are and at your place in the maturity of your Agile adoption. How do we align the roles of the past with new Agile roles and responsibilities? How do we excel as an Agile team when we work with teams that aren’t Agile? How can we become a better team, while also delivering software? Let’s look beyond the foundational values and principles of Agile and defined roles to learn techniques to make all of this work in the real world. In this session you will learn:
We’re agile now, we don’t need testers! What does that mean realistically when trying to deliver quality software? How does the role of a pure tester change when the team adopts an agile framework or way of working? Let’s discuss the path of a tester when agile is the new paradigm.
In this session I hope to introduce what happens to traditional QA/Manual testing orgs when teams adopt a Scrum, Kanban or agile framework or process.
We’ll talk about how to think about risk and ways we can overcome the bias toward shipping quickly even if the software is terrible.
I’ll introduce concepts like the agile testing volcano, behavior drive development and how the tester fits into a cross-functional team.
“Scrum got stupid when we were too busy in Scrum meetings that added no value.”“We stopped using our Kanban board because it wasn’t valuable”“Agile is just bean-counting and micro-management!”
These are common refrains from people struggling to be successful with Agile. Let’s look at agile through all the anti-patterns that manifest themselves when we attempt to be agile and discuss how to mitigate or avoid those pitfalls.
Topics included: How to have effective stand-up meetings How to make decisions based on data collected through the process of iterative or flow-based delivery. What are agile and flow respectively?
Why does developer testing matter if we have a QA department? Is TDD (Test Driven Development/Design) and BDD (Behavior Driven Development/Design) necessary, or is it just RDD (Resume Driven Development)? Let’s explore the whys and hows of developer testing.
Why Do Developers Have Two Keyboards? For quick feedback. In this session we’ll talk about the different ways to get feedback quickly. We’ll look at: how to get feedback about our code with unit tests, how to get feedback about our design with continuous integration, and how to get feedback about our solutions with continuous deployment.
Agile has become the dominant method for software-project management but Agile processes weren’t originally developed with UX in mind. As a result, UX practices and Agile workflows don’t always easily fit together but there’s no reason they can’t. This session will discuss the make-up of a robust UX team and break down examples and best practices from industry leaders who have discovered how to successfully weave their BA, UX and Developers together into a well-oiled Agile machine.
As developers of software we expect our programs to run smoothly, be free of bugs, and be available to serve our customers 24/7 - but is it reasonable to expect the same from the people behind the product? What does tech work life balance look like and is it achievable?
This is an open dialog and curious conversation between software developer and life coach, Jessica Watson, and indie game developer and family man, David Wesst, about their experience with balancing work and life in tech.
Jessica realized early on in her tech career that she was getting burnt out by trying to “do everything right” and “firefight” when things were “blowing up”. Which seemed to be more often than not. Her anxiety was on the rise and she knew she had to make some changes. Diving into the world of life coaching, meditation, and yoga she found techniques and wisdom about designing a life on her terms.
David is a family man, with a day job, and a dream he works at chasing continually. David is constantly working at balancing between being an involved father of two daughters, a productive solution architect, and creative game developer. In the past year or so, David has had to make some personal and professional life choices and apply new organizational techniques to keep his mind, health, and productivity in a good place.
Come to this talk if you want to explore improving your work life balance. We will also share a few coaching questions to help you create a healthy balance for yourself.