What’s in the book?How to provide business value to customers and be able to learn new things at work. Can you start learning frontend when you are a backend developer, or the other way around?
Small stories. What’s their value and what kind of problems do they solve?
How to deal with positive and negative risks that affect IT projects so that people are always working on the most important task right now?
The rule that makes programmers more effective at selecting next tasks.
Developers talking to clients and creating tickets. Truly collaborative nature of work.
The life without Project Managers. Can it exist? How can developers become more independent?
Over-communication. Why do you need to communicate differently when working remotely?
Continuous deployment. Step by step guidance.
Green Build. Must be.
Screencasts, as a way to share knowledge in-company.
Communication tools, especially for remote workers.
Async Standups - how to.
And much more…
This book is for…
…Software developers
Are you tired of working in the same area of code and the same feature for a long time? Days or sometimes even weeks? Feeling disconnected from other team members? That’s a sign that something needs to change.
We will show you how small changes in the process that you can push for, can help you deal with those struggles. Working on your project should not be stressful.
You can deliver something valuable even twice a day and be proud of it.
Let’s face it. Lack of self-growth is boring. Professionals invest in their skills. When we learn at home, we don’t spend time with our family and diminish our hobby. We want to learn at work.
Is it possible?
Yes! But we need a workflow which will embrace that fact. It needs to give us a chance to work on the parts of the code, that we are not most skilled at. Back-end developers can help by doing front-end related tasks.
And vice versa. They just need to get a chance.
Confusion in this area costs the project’s money and client’s happiness. We prefer clarity. But we are often not so sure about current priorities. We would like to work on tasks that are most important right now and deliver the biggest value to the client.
…Managers
We will help you manage the priorities on a daily basis. You will be able to navigate between upcoming problems and occurring opportunities quicker.
We provide a recipe for dealing with huge tasks. How can a team approach it, when having all team members working on a big, new task.
We will teach you how to have a low barrier for developers to enter the project. They will be more mobile across different projects that your company is working on. We show how to cut the risk that the project faces when one of the developers gets sick or is going to leave the team.
… Both
The whole point of the book is to make everyone autonomous.
They need to be able to figure out the priorities on their own.
Managers aren’t only here to babysit developers and make sure they have anything to do.
They need to work with developers, not in subordinate-superior structure. They should be an equal partner in a team structure.
Managers will find out how to deal with huge tasks.
They can work together with developers in a process of priority and tasks management. And often, they won’t be a need for the project to go on.
Programmers will be happy with more variety in work. Our methods reduce the bus factor. It is easier to introduce a new developer to a team.
And above it all, there is our starting point - a remote and asynchronous workplace. You don’t need to be in an office in a fixed hours. You can spend time with your family in the afternoon and work in more loose hours.