This website uses cookies for analytics and to improve provided services. By choosing I Accept, you consent to our use of them and other tracking technologies according to our Privacy Policy.

Introduction To Agile Retrospective: Dos and Don'ts For Project Managers

I remember hearing about Agile for the first time. The concept behind it seemed pretty straightforward: sprints, planning sessions, and backlog—it all looked like it could really help us accomplish more in the same timeframe (especially in comparison to Waterfall). 

Read more

A 4-step Guide To Validate Your Product Idea Without Investing In Development

An aspiring entrepreneur I’ve recently consulted told me that she’s done coding. As she’s a great programmer, I asked her what’s wrong. She was a capable technical co-founder, but, as it often turned out, she was too quick to assume that her ideas would sell.

Read more

5 ways how Agile IoT improves hardware business

We know that for some people hardware devices plus Agile just doesn’t sum up. Agile may even feel a bit odd for hardware development, with all the tools and processes behind it. The problem is, hardware is often deprived of iterative development and therefore its release may be overwhelmingly stressful (and exciting for sure) for the company.

Read more

Communication challenges in Agile Project Management

Communication is a key element of the majority of actions undertaken in both private and professional life. If we know how to do it efficiently in business, we are able to build a strong brand and gain the attention of our co-workers and – what is more important – our customers.

Read more

Quality Assurance Basics. Proper QA for your Agile projects

Grzegorz Hajdukiewicz

September 7, 2016 | QA Agile

Why do we do this?!

People make mistakes. No matter how accurate we are, no matter how much we try, when working on modern, complex applications misunderstandings and misconceptions are embedded into our daily work. The key to success is to make sure that we have skills and processes in place to detect and eliminate those as soon as possible. This is where the QA team comes in. Not only does the team care about catching and describing bugs, but also about making sure that all new features and stories are described in an understandable and meaningful way. This helps the project move forward smoothly, keeping both team and the customer happy and confident.

Read more

50% of 20%: How "20% time" practice mutated the DNA of our company in just half of that time

Darya Stepanyan

August 17, 2016 | Culture Agile

If we made a ranking of top corporate buzzwords of the past two decades, "innovation" would likely take the podium; Chief Innovation Officer seats were added to many executive board rooms across the globe, R&D divisions have been "recoolified". If innovating has become a sector-agnostic must for any business claiming to matter - what did it mean for companies that offer innovative technology solutions as the core of their service?

Read more

Fixed price vs. Time&Materials

One of the main goals of a Project Manager is to maintain a comfortable environment for developers in order to let them do their job in the best way possible.

Read more

Egoless Programming: Code Review

Jan Dudulski

February 10, 2016 | Development Agile

There are dozens of articles about Code Review (you will find some links at the bottom of this article), but from time to time it is a good idea to revisit the basics or just find everything you know about the topic for industry newcomers.

Read more

Agile resource planning: How to start a new project next Monday

Problems we've had

We cannot predict the future.

This is what makes our lives exciting, but it could be also very annoying when you're forced to make a decision without sufficient information.

Read more

8 qualities of a great Technical Leader

Tymon Tobolski

September 8, 2015 | Development Agile

As the development team working on a particular project grows, there becomes a need to divide the duties and responsibilities amongst all team members. After a few years of testing different options, we went with the Technical Leader approach and we are pretty confident with the role definition.

Read more