Collectively manage your project as it grows.
Be part of flat, scalable, self-organizing teams.
Who is this book for?
For people working in IT industry, mostly:
- Product Owners
- Project Managers
- Agile Company owners
Wow, isn’t that too wide audience? We don’t think so. Just like Extreme programming wasn’t targeted to one group of people, because everyone involved in the process of creating software could find valuable advice inside it.
What’s the book all about?
The book is about improving the process of working on a software application. Wait, but isn’t that what Agile is all about? Yes, but we want to take you further than the standard, classic Agile techniques that you already probably embraced (at least partially). We are talking about soft skills and technical procedures, because both of them can bring you benefits when applied properly.
What’s in it for me?
I’m a programmer
Chances are your project is not perfectly managed. The process is probably focused on your customer and project manager needs, while ignoring or pushing your needs aside. Are you tired of working on 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 being proud of it.
Let’s face it. Lack of self growth is boring. Professionals invest in their skills. But our time is limited and valuable. 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 it is, but we need a work-flow which will embrace that fact and give us a chance to work on the parts of the code, that we are not most skilled at and improve in such area. Backend developers can help by doing frontend related tasks. Frontend developer can improve their backend skills. They just need to get a chance.
As programmers, when we are certain that we work on the right thing and the scope of the task is small and well defined we are 100% committed and effective. 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 and we would like to work on tasks that are most important right now and deliver business value to the client. We fear that when we fail to do so we will be blamed. Learn how to communicate with product owners and project managers to be sure what you should be working on. Propose improvements so that it is always obvious what needs to be done without the need to contact anyone.
Agile provides great opportunity for people to step forward and become leaders. But do you and your company know how to let people enter the path of leadership? How to empower the developers so they can introduce changes that makes them more effective? As part of the book we are writing as well how developers can play to role of project managers. Your company might not become second Valve or Github but you can certainly benefit from applying changes leading towards more flat organization structure. Learn how to become a leader.
As programmers we are privileged. In our lives we can enjoy many things that people doing other kinds of job cannot. But we need a work-flow that will let us actually seize the opportunities such as, for example, the possibility to work remotely and asynchronously. Push for the right kind of change from bottom up and fix the problems that are making you unhappy.
I’m a product owner or project manager
You will learn what you can do to improve the Collective Ownership and minimize the risk that the project faces when one of the developers gets sick or is going to leave the team.
We will help you manage the priorities on daily basis so that you can quicker navigate between upcoming problems and occurring opportunities.
We provide recipe for dealing with huge tasks. How can a team approach it gradually, having all team members working on a big, new task without assigning one programmer to it for weeks.
Technology is exponentially changing society. Workplaces are transforming to catch on. The best knowledge workers have broken free. “Developers oriented project management” introduce you to the mind of A players passionatly collaborating freely on the other side. Adapt or be left behind.
I’m Agile Company owner
We will teach you how to have low barrier for developers to enter the project so that they are more mobile across different projects that your company is working on at the same time.
We will help you increase Collective Ownership so that developers are more familiar with multiple parts of project. This will help you mitigate the risk that comes when one of them leaves the project or the company together with entire knowledge about certain parts of the app.
We will show a process for collective management of a project. You can still have project managers but without the burden of micromanagement for the programmers. You will learn how to give more power to programmers, embrace their technical knowledge about the project as part of the management process. All that, so the work on the project is more smooth and your customers more happy.
Are you a self-organizing team and do you want to estimate, plan and track your work without the support of a project manager? Developers Oriented Project Management gives you lot’s of valuable ideas on how to do it!
The final price of this ebook will be higher (around $49). Current price is for the beta version of this ebook and for all the future updates. Unlimited money back guarantee policy in case you are not completely satisfied. We will deliver new versions of the book to you via email.
- 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?
- Sprints. Are you really having them? Or maybe you are working day by day to improve the codebase and release new features?
- 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 attitude to project management. Why should developers improve their soft skills and how to do it.
- Customer meetings. How to take most of them?
- Developers talking to clients and creating tickets. Trully collaborative nature of work.
- The life without Project Managers. Can it exist? How can developers become more independent?
- Extracing tickets from documentation of feature. How to deal with big features and attack them step by step in 2 different ways.
- Over-communication. Why do you need to communicate differently when working remotely?
- Continuous deployment. Step by step guidance.
- Lack of Pull Requests. The way Google does it.
- Green Build. Must be.
- Screencasts, as a way to share knowledge in company.
- Communication tools, especially for remote workers.
- Meetings, not too much, not enough.
- Async Standups - how to.
Current size: Around 105 pages.
Available formats for beta version: Pdf, Epub. Mobi (Kindle).
Just tell me when the book is ready
Robert Pankowecki is Ruby on Rails developer, working remotely for more than two years. At Arkency he’s worked on number of web projects in collaboration with small startups as well as large corporations. The creator of active_reload library which made your Rails apps faster in development mode. Founder of wroc_love.rb conference and one of the leading speakers at Lower Silesian Ruby User Group
Andrzej Krzywda is the Owner and CTO of Arkency. Working remotely for over 7 years and with 10 years of experience in Ruby on Rails application. The author of Fearless Refactoring: Rails Controllers ebook. Founder of wroc_love.rb conference and the member of Lower Silesian Ruby User Group since its very first meeting.