Today, many companies are transferring their development processes to Agile frameworks. In this article, I discuss how the concept of a Project and the position of classic Project Manager are transferred in accordance with the Agile paradigm.
Flexible development methodology
- Continuous Improvement is also a Project, a meta-Project, a maintenance that usually lasts longer than the main development project.
- If you can fit into the Sprint boundaries with your development cycle, then the concept of Retrospective as it is formulated in SCRUM may also suit you. But if you are bigger and not oriented on CI/CD, then be ready to make a hybrid of SCRUM with classical Project Management – thanks God SCRUM is good embeddable (proven by SAFe) !
- What is left out in when we run retrospectives quarterly? – Plan and Check. The placeholder of classical SCRUM Retrospective is quite suitable for that purpose, surrounded, of course, by some additional groomings, providing required action plans and decompositions up to sprint-length steps.
I am a Project Manager. 14 years of project management, 5 years in agile framework, last 4 years in product companies, last 3 years in ABBYY, mobile technologies. I would like to share my practical experience, how we have organized the planning in ABYY Mobile Technologies having SCRUM development.
“SCRUM — you get too little, and you need to add the missing.” The story about how we adjusted the Planning procedure for yearly roadmapping and budgeting, how we have organized the SCRUM‑planning for the feature‑driven development with product development cycle 2–3 months and more.
I believe listicles have a huge potential for testing demand hypotheses. Have you tried using listicles for your demand validation? If so - let us know in the comments how this worked for you.
Do you know these "Top N something something" kind of articles? Like:
- 5 best GPS vehicle trackers
- The 14 hair growth products that actually work
- Top 10 Best CRM Software Tools in 2023
They are often referred to as "listicles" - articles presented in the form of a list.
I love them - they make picking a new phone, a movie to watch, an app to install much easier. I also use them at work all the time while looking for solutions to everyday challenges.
So what if we use one of them to benchmark our product against the best available alternatives?
A similar article should have appeared earlier, about ten or fifthteen years ago, when Agile was just starting to be implemented in companies. How many mistakes, problems, conflicts could be avoided if managers immediately approached the issue correctly ...
But during this time, the experience of "implementing" Agile in different conditions, in different companies has accumulated, which should be generalized and widely disseminated.
This article could have been born about a year ago – that's when the PVS-Studio team decided to try agile. However, we wanted to experience it hands-on before we told the world about it. Aside from introducing agile, we decided to switch from Bitbucket to a new task tracker. We also wanted to upgrade many of our internal development processes. No time for an article!
We work using Agile: Scrum, or Kanban, or any other extended project management way. Agile appeared in 2001 as a result of a long discussion between really smart guys. They just formed best practices of management into the shape of short documents - the Agile Manifesto. But what did they want to replace by the Agile way? Most of you may say that they wanted the Waterfall to go to the past. But what would you think if I tell you that the “classical” Waterfall had been a really rare thing even for those days?
Indeed, there were times when everything around scrum was innovative, valuable and efficient: from planning to sprints and so on.
However, recently the number of negative reviews has been escalating.
Ten years ago, a young project manager had a successful experience in implementing something similar to Scrum in one of the insurance companies. There is more than enough enthusiasm. Colleagues from the tech department strongly supported me. The developer's background was helpful too. But at some point, an impenetrable wall appeared: the Agile approach worked inside IT, but it did not work outside. It needed synchronization with other departments and a change in the way the company worked. A full transition did not happen, but a year ago, it was possible to implement Agile transformation on another project in a financial organization with more than 100 people. Is this possible?
My name is Anna and I work for an American company Scentbird NY as a product designer. Prior to that I was involved in developing flagship products in Alfa-Bank design team.
I was probably born under a lucky star but all my life I've been working with the developers who suggest the best product solutions, better than a lot of product managers and product owners. But anyway, my observation is that the earlier you involve developers into working on a particular task, the better off you are.
What you are about to read is actually a blueprint on how to conduct brainstorm sessions and generate not-so-obvious yet effective solutions, which are apparently really easy to reach and not that time-consuming.
There is no need for detailed analytics to understand that Scrum continues to grow in popularity just because of its many benefits and general effectiveness. And the important merit in this belongs to a Scrum Master. In this post, we extol and praise the role of a Scrum Master, without which no Scrum project succeeds.
Today this iterative or incremental method affects various aspects of development and business including project management. What are the best sources to learn Agile? This post covers 10 powerful books that may enhance the skills of project managers and their teams.
In this post, you will learn some basic facts about Scrumban and how to combine two popular Agile methodologies – Kanban and Scrum to make this hybrid approach perform better.
Scrum strongly enforces the goals and time boxes for everything, including the ceremonies. This post covers these outstanding events and identifies the goals for each as well as their necessity. Take 7-8 minutes to figure them out.
In Agile software development, this choice is also challenging, especially if it's about Scrum and Kanban.
A powerful Kanban board is the solution. This excellent project collaboration tool is widely used in software development, digital marketing, construction, innovative solutions and among other cases where there is a steady workflow of tasks. The Kanban approach helps teams to visualize workflow, analyze processes and achieve greater task management efficiencies. In this post, we describe 14 Kanban tools with advanced features. Compare them and choose the best one right for your needs!
What are these powerful practices that make Agile popular and trendy? Here we share the list that is definitely incomplete but foundational.
People go mad about Scrum: many IT blogs write about it, many practical courses promise to teach all Scrum features, many companies want to see a working experience with Scrum in CVs, and so on. Scrum conquers them all. In this post, we define why.