Get Users Hooked by Applying the Hooked Model to Release Slices
What if we took Nir Eyal’s Hooked model – Trigger, Action, Variable Reward, and Investment – and plugged it into Agile and Scrum release planning?
Explore with CardBoard.
Ready to dive into the deep end of product development? Grab your gear and join us as we navigate the currents of insights, advice, and stories. No fluff, just the good stuff.
One of the BIGGEST Mistakes Teams Make When Building Apps
Imagine this, you have a idea for the world’s next great application. You have raised the money you […]
Using Roadmap Templates in your Online Whiteboard
The vision has been cast, the planning done, what is next? A product roadmap helps teams determine what […]
5 Ways Your Team Can Benefit From an Online Whiteboard
Online whiteboards are on the rise, and we can only anticipate that the demand for online whiteboards to […]
Network Diagramming with CardBoard
Mapping out your network and all the elements it interacts with can be done using networking diagram and […]
How to hold 4 Ls Retrospective
What is a 4 Ls Retrospective? At the conclusion of a sprint, the 4 Ls Retrospective is designed […]
How to Prioritize Agile Stories
Using a problem based approach to assign priority One of the biggest steps after you’ve planned and mapped […]
How to Make a Mind Map
Mind mapping is quick way of getting information out of from your brain and in front of your team. Mind Mapping is a unique solution to map out the ideas and connect thoughts.
Three trends for 2020
As more team members work remotely, finding visual collaboration tools will become vital for teams With more workers […]
How any business can benefit from User Story Mapping
If you were to do a Google search on the term User Story Mapping you might be led to believe […]
4 Tips for Better Collaboration
Working with teams can be highly rewarding, yet extremely challenging. Collaboration is fundamental piece to scaling business and […]
What Makes a Great Scrum Master?
Managing your team and being the voice of accountability is tough. Being a great scrum master is even more challenging. What does it take to be a GREAT scrum master?