Posts

5 Stakeholder Questions To Ask Before Starting the Software Development Process

Software development is an intricate process that requires skill, planning and team effort. There are several stakeholders involved in the project, from company executives to various departments within the company.

It isn’t possible to satisfy all of them completely, but you can take their concerns into account before working on the project by asking the right questions. Doing so can help you understand their priorities and plan the development process accordingly. Here’s a list of 5 questions to ask before starting a software development process:

  1. What is the Product?

Projects tend to get out of hand if you don’t have a clear vision in mind. Software developers need to understand what the end product should look like before they even start planning for it. For example, does the company want an app that will help users find the best online deals? Does it want a software program for its HR department?

Stakeholders can provide a list of features or ideas for the end product to make things easier for a development team. If there’s any dispute about the final product, this will be the best time to resolve it. Make sure everyone is on the same page before proceeding.

  1. What is Not a Part of the Product?

Developers can sometimes go overboard and add features or elements that aren’t necessary. That happens if they don’t know what should be excluded from the final product. For example, if a website is only delivering to the US, there’s no need to include a feature to convert prices to other currencies. In many cases, stakeholders assume their development team is going to deliver something, but the latter is unaware of it. It is essential to establish what you will and won’t deliver.

  1. What is a Successful Product?

Software programs are tools designed to achieve a specific goal or purpose. A company creates a website if they want to establish a presence online. They design an app if they want to build a robust and long-term customer base. They develop a software application to make daily processes easier. If the product fulfills these goals, it is considered successful.

The end goal isn’t to deliver a good product; it is to provide a product that succeeds in the market. There’s a clear difference between these two goals. For example, a website can be beautiful and functional but still not provide all the services the target audience needs. Stakeholders should define what a successful product means to them at the start of the project.

  1. Do We Have a Single Point of Communication?

This is one of the most challenging aspects of project management. The project starts with one team and one client, but eventually, a large number of people start becoming part of the process. The IT guy must approve one aspect of the design, the other should please the marketing expert, and so on.

If these people start offering suggestions or requesting changes, the project can quickly get out of control. It is crucial to establish a single point of communication between stakeholders, clients, and development teams. You can maintain a smooth flow of information while keeping track of numerous requests.

  1. What are the Potential Roadblocks or Problems?

No one likes to discuss problems before they work on a project, but you need to address it. Gather all stakeholders together and ask them about possible hurdles. Can the project run out of money? What happens if some temporary contractors don’t live up to expectations? What if the client changes their mind in the middle of the project? If you know about possible hurdles, you can develop systems to counteract them.

These questions will help a team start their project on a firm foundation. Don’t hesitate to ask questions to stakeholders; the answers will help improve the quality of your end product.

At Number8, our philosophy is to empower our clients to produce better software, faster. We are experts in augmenting scrum teams with senior consultants that can help increase team velocity immediately. If you’re interested in learning more about Number8 and what we do, give us a call at (502) 890-7665, or check out our information page.

 

The 12 Principles of the Agile Manifesto

The agile methodology started in the software development industry in response to the limitations of traditional software development principles. Eventually, companies realized that it could be used to improve project management, team management, and other such processes. Agile focuses more on individuals and interactions between different teams than processes or sophisticated tools. There are 12 core principles of the agile manifesto.

  1. Customer Satisfaction – Providing Early & Continuous Delivery

The Agile Manifesto states that developers and companies can achieve customer satisfaction by delivering products early for testing and feedback. Teams can continuously share their progress with the clients and incorporate their input into the product. The focus is on fulfilling client priorities and then focusing on other aspects of the project. This allows developers to adjust to the client’s changing requirements during the development process. Customers get a more refined product at the end of this process, and they’re more satisfied.

  1. Responding Positively to Change – Even During the Later Stages of Development

The modern business environment is fluid, and customer requirements change frequently. Traditional working models don’t adapt well to change, especially during the late stages. The agile methodology adapts to change quickly at every stage. Agile offers a simplified model for requesting and making alterations in the product design. There’s no formal documentation or approval required, which can speed things up.

  1. Frequent Delivery of Product Elements

Rather than forcing the clients to wait for several months, the development team can deliver the project in stages. You need to make sure every aspect is finished, tested, and styled appropriately. This gives customers quick fulfillment and offers assurance that their project is progressing as planned.

  1. Communication Between Developers & Executives

There’s often a communication gap between developers and executives. People who work on the project have more technical skills and knowledge about the product, while executives understand the business side of things. This can lead to miscommunication, delays, and other such issues. Agile requires everyone to be on the same page and maintain open communications.

  1. Trusting Developers & Teams to Do Their Job

Many executives don’t trust their workers to choose the right job, which results in micromanagement. Such micromanagement can hamper productivity and place unnecessary pressure on the team. Projects should be built around motivated and passionate professionals who understand their strengths. Self-organized teams are more efficient and content to work on every aspect of their projects.

  1. Face to Face Conversations

Essential instructions and project requirements can become lost in endless chain emails, which is why face-to-face communication is necessary. Executives should obtain feedback from the source and work with the team on the project. Virtual communications like video conferences can help in this process.

  1. Collocation & Pair Programming

Collocation is the process of making a team work from the same open area. Pair programming is when two programmers are assigned the same workstation. One programmer is writing the code while the other looks at the bigger picture. Both swap roles every few minutes. Both of these processes improve product quality and make teams more productive.

  1. Sustainable Development

No one can work continuously or at a demanding pace without experiencing some form of burnout. Agile methodologies focus on improving work-life balance and making sure everyone in the team is healthy. Product development is only sustainable if workers are allowed to get adequate rest.

  1. Self-Reflection to Improve Overall Performance

The agile manifesto is focused on the human aspect of development. The best designs come from teams who are committed, passionate, and happy to work. They also come from teams that are willing to look back at their past work and improve.

  1. Simplicity

The Pareto Principle says that you get 80% of the work done with 20% of the effort. Professionals should focus on the 20% and make sure that 80% of the work reaches the customer on a priority basis. You can then focus on the nitty-gritty and refine the project later.

  1. Self-Organizing Teams

Executives should give their teams some room to flex their creative muscles. The team has skilled employees who are experts in their field. Allowing them some independence will help product development and improve overall work culture.

  1. Adapting to Change

Agile means fluid and adaptive. You can only be agile if you’re willing to accept changing demands and requirements during a project. Everyone can plan for a perfect product, but you can only develop something substantial through trial and error. Adopting agile principles can help improve your team’s performance and productivity significantly.

At Number8, our philosophy is to empower our clients to produce better software, faster. We are experts in augmenting scrum teams with senior consultants that can help increase team velocity immediately. If you’re interested in learning more about Number8 and what we do, give us a call at (502) 890-7665, or check out our information page.

 

“Automated QA: Save time, use a web calendar handler!”

Number8’s very own Derick Arzu was recently published on Medium. Read the article on automated QA processes below.

Text boxes, check boxes, radio buttons, and other elements of forms are fairly simple to deal with when it comes to developing UI functional tests for a web application. But what happens when you want to write a test that verifies that the UI for a web calendar is working?

You are probably thinking that it can be easily achieved with a couple of clicks and validations, which is not only true but also the approach that led to the idea of a handler.

Before you discover how to make your automated QA team very happy, here are some reasons why writing a simple function or just a segment of code that deals with ONE specific calendar is not as scalable. Imagine you are a QA Developer at a company who is developing the websites for airlines A and B and your team is requested to create the automated test suites. Sounds quite easy, you will use the same code in both projects, nothing will need to be changed; until someone shows you the designs of the two web calendars each airline uses in their website.

Beginning with the obvious differences, airline A uses two windows while airline B uses only one; that surely represents a significant change in the code of that first approach. Another difference you might not have noticed is that airline B has a dropdown to change the year of the calendar, so that would mean a slight change in the method used to get the text of the displayed year. Those are two visual differences that will affect the way your bot interacts with the calendar and the DOM will surely surprise you with more.

Now that you are interested, the coding begins!

This handler was implemented in Node.js and uses WebdriverIO as the test framework that interacts with the browser.

You will find out that the framework has two functions ($ and $$) to fetch web elements. However, a hierarchy of classes will be created to manipulate elements, later on you will learn this is so that the handler can easily be able to cover many web calendar designs.

The main class is Element. Here is where, the method to obtain the fetch function is implemented, it has two parameters:

    1. selectorObject (required) which refers to an object with two properties; the first named selector , is a string that specifies the selector that will be used to fetch the element. The second is index, which is an integer that must be assigned to the object if the fetch result wants to be treated as a single element and not as an array of elements.
    2. additionalProperties (optional) is an object with any property that wants to be added to the fetch result. The subclasses of the hierarchy use this to manage how some data is obtained from the web elements, you will learn this later on.

Read More…

Q & A Best Practices

On top of delivering a project on time and within budget, developers must test for quality assurance upon completion to ensure stakeholders’ expectations have been met.

However, testing for quality after a product is built, usually results in far too little, too late. The agile model of software development encourages practicing quality assurance throughout every phase of the project. The agile way also prioritizes quality by making it the responsibility of every team member, not just the QA testers. As a result, the QA team coordinates efforts with the development team at each iteration, providing continuous testing.

Implementing a feedback loop is a fundamental step in the quality assurance process. In order to guarantee that the product meets all of the requirements (feature functionality, design, reliability, usability and efficiency), it can be helpful to enlist the perspectives of those with varying backgrounds. This can include those proficient in testing, business and or development.

Quality assurance testing can be both manual and automated. While both approaches are proficient at mitigating bugs, automated software testing is often more beneficial in that it is quicker and more effective at checking for code correctness. It’s important to remember that the goal of Q & A testing is to find faults within the software so that an error-free application can be delivered to the client.

The following are integral software testing methods when best practicing quality assurance:

Test Driven Development (TDD)

TDD works by building a project’s code around the QA tests. The programming team first designs and builds tests for functional code, and then creates code that will pass them. This development method helps everyone gain an understanding of the code’s purpose before development; guaranteeing the initial functionality of the code and effectively building in quality.

Behavior Driven Development (BDD)

Similar to TDD, in that the test is written before the code, BDD tests the behavior of an application under specific conditions. This is done with the end user in mind. As development progresses, BDD often proves to be more reliable than TDD. BDD is also written in English instead of code, allowing for a more streamlined feedback loop.

Acceptance Tests

Acceptance tests are simple pass or fail tests that check whether or not a feature behaves as it should. These are often automated to meet customer and business requirements.

Regression Tests

Once one feature is functional, regression tests ensure it’s stability throughout the software’s other modifications. As more features are built, these automated tests check that the others aren’t being negatively affected as a result.

Exploratory Tests

Exploratory tests are usually manual, in that a human operates the software looking for unknown unknowns. These tests are meant to identify new situations that the development or QA teams haven’t thought of.

Once a product thoroughly meet’s it’s intended purpose and performs well under pressure, the QA testing is complete.

At Number8, we believe in developing software that is user-friendly, reliable and completely functional. As a result, we are always recruiting talented QA professionals for quality assurance jobs on our team. To learn more about how we can help you complete and successfully launch your software project, contact us at 502-890-7665. 

10 Agile Project Management Terms You Should Know

Whether you’re planning on managing a project the agile way, or just want to stay up to date on the latest developments in the field, here are 10 agile project management terms you should know:

1. Agile Manifesto

The agile manifesto is a great starting point for anyone looking to familiarize themselves with the agile methodology. The manifesto outlines the 4 values and 12 principles of agile software development and was actually created by a group of software developers in an effort to provide a clear and alternative set of processes for developing software. The agile way of doing things prioritizes individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan. 

2. Scrum

A scrum is a daily stand up meeting with the sole focus being to review each team member’s progress on any given project. Scrums help to keep everyone accountable and on the same page, ensuring no one falls too behind or gets too far ahead in the development of a project.

3. Scrum Master

A scrum master oversees the development process and acts as a problem solver for the team; preventing roadblocks and enforcing the agile way of doing things.

4. Stakeholder

A stakeholder refers to anyone with a vested interest in the product. This can be the client, the end user, sales people, legal representatives etc. Stakeholders have an informative role in the development phase, and are critical in defining the project’s requirements.

5. Backlog

The backlog is the ever changing list of the software’s requirements. It’s not to be seen as a to do list so much as a prioritized list of desired features of the product provided by the stakeholders.

6. Story

The story tells the software system’s requirements from the consumer’s point of view. For example, as “a <type of user>, I want to <perform some task> so I can <achieve some goal.>”

7. Burndown & Burnup Charts

A burndown chart visually measures the progress of a project over time (the vertical axis is made up of the backlog while the horizontal axis represents time). A burnup chart displays completed work (the vertical axis shows the amount done over the horizontal axis, time). These charts are essential to inspiring the team as they work and help provide a realistic time frame for the project’s completion as well as a working scale of the project.

8. Feature Creep

While changes are expected, and certainly embraced in the agile way of doing things, the phrase “feature creep” refers to features that are added after development has begun. Adding too many features during the development phase can result in feature creep and software that is too complicated or difficult to use.

9. Timeboxing

Timeboxing is kind of like time blocking in that it assigns a specific time frame to accomplish a goal. The definitive feature of timeboxing however, is that the work stops at the end of the timebox, instead of when the work is complete. This is extremely helpful in terms of productivity, and controlling the scale of a project.

10. Sprint

A sprint is a short development phase usually lasting anywhere from 1 week to a month. Sprints help prevent projects from feeling overwhelming and allows feedback to be given at appropriate junctures.

At Number8, we help project managers connect with highly trained and efficient IT support to help reach company goals. If you’re interested in learning more about Number8 and what we do, give us a call at(502) 890-7665, or check out our information page!

How To Overcome 7 Common Software Development Obstacles

Launching a newly developed software is as challenging as it is rewarding. Developing software from the ground up is no easy feat. It takes a lot of planning, time management, and knowledge of the ins and outs of information technology. When the launch of a software development project goes off without a hitch, it’s an IT miracle. It’s known that with software development, as with most IT projects, there can be some obstacles to overcome. More often than not, things go wrong within the coding or through a development process that must be fixed. Sometimes developers even have to go back to square one and start the entire project over. However, that is not always the case. Developers prepared to overcome obstacles are often successful in doing so. The key is knowing how to overcome common software development obstacles. This way you can ensure that the launch of your software goes smoothly.

You may be asking yourself if every software development project is different, what are common software development obstacles? And that’s what we’re here to help you with today. Follow along to learn how to overcome 7 common software development obstacles before starting your next project.

7 Common Software Development Obstacles You Can Overcome

1. Poor Time Management Sets Unrealistic Expectations

Mismanaged timelines and missed launch dates are common obstacles that people overcome during a software development project. Whether it’s due to unforeseen roadblocks or issues that were expected to come up, there’s not much worse for a project than an extended delay. One of the best ways to avoid missed deadlines is to brainstorm with your team before starting the project. What could go wrong? Which pieces are expected to break? Where do you foresee there being delays? Being prepared for the inevitable bumps in the road is the best way to get over them smoothly and without too much delay. When a problem does come up that threatens the timely delivery of a project, stay calm, get the team together, and work as a group to find the best way forward.

2. Issues with Integration

Compatibility can be an issue with any project. When developing new software from the ground up, how do you ensure it pairs with all the tools the client already uses? One of the best ways to go about integration is through the use of application programming interfaces (APIs). Another option is to partner with the other tech brands that the client is prone to use. Find ways to work together with already utilized tools and teams of developers experienced with said tools.

3. Breakdowns in Communication

No software development program was launched alone. Depending on the size of the software development project, the team working on it can be as small as 5 people or as large as 20. When a communication breakdown occurs, it can have disastrous effects that could put the entire project in jeopardy. One of the best ways to avoid a communication breakdown is by hiring an effective project manager. Someone who can divide tasks among the team then ensure each of them is done and any changes which may affect the entire development outcome are communicated effectively is imperative to a successful project.

4. Overloading the Software with Features

While some features are necessary, others can be downright frivolous and simply load a software down. There is such a thing as too much and, when it comes to software, the line between just enough and too much is very thin. One of the best ways to circumvent overloading your software is to focus on features that truly embellish the core goal of the program. Less is always more in software and features that help the software rise above other programs are useful, but the goal of the software is to solve a problem, not create more, so keep features slim.

5. Not Understanding Exactly What the Software is For

One of the best ways to succeed in software development is to have a clear vision of what success looks like. Being able to completely understand how your software should work if it is working well will make it much easier to get to that finished point. Determine the “why” of the software before beginning the development process. Once you start, do not waiver from that why without good reason.

6. Not Realizing the Importance of Quality Assurance

Customer satisfaction is dependent on extensive quality assurance. Sending a software development project out into the world without assuring it is working as well as it possibly can is IT suicide. In order to achieve a high-performance product, the quality of the coding needs to be reviewed and tested continuously throughout development. Consider hiring a tester from a third-party source or create your own quality assurance checklist, in-house, and employ it repetitively.

7. Not Having a Target Audience Defined

While you, and your team, may think that your new software project is the best thing since sliced bread, not everyone will. Defining a target audience can help to avoid wasting time and money once the project is launched. Outline the demographics of the ideal user of your software. Then build a marketing plan that will appeal to that demographic. There are third-party companies available to complete market research, including focus groups, which can help identify the perfect consumer and what rings true with them in regards to marketing.

There are a lot of dos and don’ts to consider when developing new software. These are some of the software development obstacles our team has learned to avoid.

The more dos you can accomplish and don’ts you can avoid, the more likely your project will launch smoothly. All in all, the more planning you can put into your project prior to starting, the better. The tips above will help you to avoid a variety of issues, but there are always unforeseen circumstances.

If you are in the middle of a software development project and have hit a roadblock, Number8 can help. Our dedicated team of software developers located in Louisville, Kentucky and at our nearshore office in Costa Rica has worked together to launch countless software projects successfully. Contact us today by calling 502-890-7665 to learn more about what we can do to help you wrap up your project.

5 Must Read Career Books

We all face challenges in our careers at some point or another, and the truth is, we spend most of our lives at work. So why not make the most of it? Whether you’re feeling stuck in your current position and need a boost or are transitioning to a new role, we are firm believers that even in this age of technology, some of the best answers can be found in a book!

To help give you a leg up, we’ve compiled a list of must read career books chalked full of advice and tools to help you tackle everything and anything.

1. Master Your Next Move by Michael Watkins

Experiencing a lot of change in your career? Master Your Next Move offers insight into some of the most important transitions that occur within our careers. From overseas assignments and on-boarding at a new company, to getting promoted and having to lead former peers, sometimes even a good career move can be challenging. In his latest book, Michael Watkins lends a helping hand to those in leadership positions looking to excel as they climb the ladder.

2. Designing Your Life: How to Build a Well-Lived, Joyful Life by Bill Burnett & Dave Evans

Looking for more fulfillment at work or in general? Designing Your Life suggests that in order to live a life of fulfillment, one should apply the concepts of design to both their personal life and career. After all, every design begins by solving a problem. If you want to rework your career, start by rethinking your approach.

3. Love Your Job: The New Rules for Career Happiness by Kerry Hannon

Hate your job? According to a recent Gallup Poll, 85% of people do. Kerry Hannon’s Love Your Job explains how you can make the most of your current position by changing your perspective. Hannon offers tips on developing positive thought patters and habits that will reinvigorate you and give you a new found purpose at work no matter what stage of your career you are in.

4. Linchpin: Are you Indispensable? by Seth Godin

We all know that in this new age of the workforce, innovation is key to staying relevant. Seth Godin’s Linchpin paves the way for anyone looking to make a lasting impact. The book begins by posing the following questions, “Have you ever found a shortcut that others missed? Seen a new way to resolve a conflict? Made a connection with someone others couldn’t reach? Even once? Then you have what it takes to become indispensable.”

5. The Up Side of Down: Why Failing Well Is the Key to Success by Megan McArdle

Anyone who has ever been in business, knows about failure. For those who have recently experienced a set back at work, Megan McArdle’s The Up Side of Down is an inspirational guide to reinventing yourself in the face of failure by learning from the experience instead of allowing it to debilitate you.

At Number 8, we help companies connect with qualified remote employees to help with software development. We also focus on helping companies improve their internal IT processes. If you’re interested in learning more about Number8 and what we do, give us a call at (502) 890-7665, or check out our information page here!

3 TED Talks to Listen to When You Need Motivation

We’ve all been there. The point in the day, week, or month where the steam that’s been powering our engines seems to disappear. Losing motivation is never convenient. Often it comes at the most inconvenient times, such as, when a large project is due or a new endeavor is just kicking off. So, how do you overcome that lack of motivation and continue to power through the work you’re obligated to deliver?

There are many ways to regain motivation. Sometimes taking a short break of 5-10 minutes to get away from your desk is all it takes. Other times it may take a little more space from the office, perhaps in the form of a personal day, to get back into the right headspace for work. And that’s okay. Managing burnout is important in everyone’s career. We have to do what’s necessary to deliver our best performance as often as we can. For those times when you can’t get away for even five minutes, but you need a little more motivation to keep going, listen to one of these TED Talks on staying motivated.

3 TED Talks to Help You Get Motivation

1. A Powerful Way to Unleash Your Natural Creativity by Tim Harford

Harford opens this TED Talk with the quote, “to do two things at once is to do neither”, and it leads the listener to think that his entire talk is going to focus on how multitasking kills creativity. However, Harford quickly clarifies that he is not on stage to debunk the benefits of multitasking. Instead, Harford discusses a practice common among highly creative people, including Albert Einstein, and that practice is called “slow-motion multitasking”.

It may sound counterintuitive. For most people, the entire point of multitasking is to be able to get multiple things done quickly and efficiently. Slow-motion multitasking does not have the same end result. Slow-motion multitasking is not about getting things done as quickly as possible. It is about getting multiple things done at once without feeling burnt out by one project. By slow-motion multitasking, one is able to hop from project to project as their inspiration strikes or creativity sparks. Harford explains multiple studies that prove highly creative people have multiple projects going on at one time and allow themselves to move between these project at their own leisure.

He also discusses how athletes benefit from cross-training and how Michael Crichton created the world’s most commercially successful book, television series, and a movie with the help of slow-motion multitasking. Listen to the full TED Talk here and the next time you find yourself overwhelmed with a project and losing motivation because of your feelings, try shifting gears to another task. Working on, or even completing, another task will help the negative thoughts you’ve associated with your more daunting project dissipate, making room for productive and motivational thoughts to come in.

2. How to Make Work-Life Balance Work by Nigel Marsh

As we stated earlier, one of the biggest triggers for lack of motivation is burnout. Being tired, and even fed up, with your day-to-day work life can really affect your work ethic and your drive. In this TED Talk, Nigel Marsh discusses work-life balance and how incentives like “dress-down Friday” and “flexi-time” don’t make up for the fact that some career paths are fundamentally incompatible with being present at home. However, if you’re in one of those job fields, all hope is not lost.

As long as you can recognize this, and understand that your boss or higher-ups will not correct the imbalance for you, then it’s possible for you to create that balance on your own. Being aware that your employer may not have your best intentions in mind will allow you to set your own boundaries on how much time you dedicate to work and how much you dedicate to your home life.

Marsh suggests (quite hilariously) that if you’re feeling unmotivated, or burnt out, to write down your ideal day. How much do you want to get done? In order to get all those things done, how long do you need to be awake? Because, let’s not forget, sleep is just as important to motivation and productivity as work-life balance is. Is your day jam-packed? That’s Marsh’s point and, according to him, in order to balance work and life, you must “approach balance in a balanced way”. By tending to the intellectual side, emotional side, and spiritual side of one’s life, a person can create a more balanced life quite effortlessly.

You can listen to the full TED Talk here to see how Marsh’s realization that slowing down and investing the right amount of energy into the right tasks can transform a person’s day-to-day life.

3. Want to Be More Creative? Go for a Walk by Marily Oppezzo

It’s no surprise that we lose motivation. Almost any project is a long process from start to finish and takes an exorbitant amount of time and energy. So, how do you ensure your creativity does not falter and your motivation does not dry up? Marily Oppezzo recommends going for a walk. She’s not saying that you’re going to get stuck during your project, go for a walk, and come back with all the solutions. But she is saying that walking during the brainstorming process of a project can boost creativity.

During her TED Talk, she discusses a study that measured if people were more creative while sitting or walking. By asking four test groups to come up with alternate uses for a specific object (like a key) she was able to deduce that the members of the study who walked while brainstorming ideas came up with twice as many ideas as those who remained seated.

Now how can this help you stay motivated? Well, you can apply Oppezzo’s approach to brainstorming to your motivation. Ask yourself what your problem is? Why are you losing motivation? Then take yourself for a walk and brainstorm around these questions. Continue to come up with ideas and try for as many as you can. By not getting stuck on your first or second idea you’re allowing your creativity to flow. As it flows, it will help you find more motivation to continue your project. Listen to Marily’s entire TED Talk here to learn more about the study and its interesting results.

Next Time You’re Losing Motivation…

Motivation ebbs and flows, like most things in life, and sometimes the best way to regain it is to forget it. Go for a walk and try to get your focus back. Shift from one task to another to allow your mind a break. Consider how much time you’ve put into the project for the past day, week, month, and step away completely. Or listen to a TED Talk. It may give you the motivation you need to continue working or take a break.