How to manage the process for a project for one person

Question

We have one developer working on three different projects. He worked on bug fixes, maintenance, and some features. In one specific project, he works with another junior developer.

Our company wants to introduce a fight for all projects. What is the best way to handle the scrum process for a 1 or 2 person project?

Answer 1

I agree that you need to keep it Simple Stupid, but here you can use most of the Scrum infrastructure.

I had several people working in this way both on projects and on maintenance work.

Product Owner / Backlog - There is still an owner who is responsible for determining the value of the business and setting priorities, right? There must be a backlog. If he is part of a larger Scrum enterprise, he will probably need to feed part of a larger Backlog product.

Team Scrum - yep, her team of 1 or 2 people. So its really a SELF organization ... but that's fine! Daily fight? Yes, between two people, or if it’s just one person at times, a good time to solve problems and problems, think about what obstacles you need to come up to Scrum Scrum or the owner of the product.

Sprint is still a good idea, especially if it is part of a larger Scrum enterprise that works in the sprint, but even without it. A good chance to catch up with the PO, the demo that you got, activate yourself, retrospectively and see what you can do better, plan your next sprint. Please note that if you work outside the Scrum / Scrum of Scrum facility, the sprint may benefit from being shorter than usual, since the scope is probably smaller and the planning overhead is lower. but it depends on the situation.

Retrospective - yes, it can be done alone. I think killer programmers should look back at their work / progress and take action on what keeps them going. Even keep a chart in your workspace to help you make progress.

Taskbar / Burndown - Yes, you need it. You can have them in your workspace on the wall, they can be small, but they really help, even if you are one person. Why does GTD (Getting Things Done) help one person and TB / BDC? If this person does the work on the project, then Sprint Burndown and Release Burndown give great value. If he carries out operational / technical work, this is another way to check it or not, and apply appropriate measures accordingly.

Scrum Master - a person must be his own master of the battle.

Coach - if the organization had a coach helping teams / SMs / POs, then he also had to help this fight ...

To summarize, it is clear that the values ​​and principles that underlie Scrum / Agile are also applicable to teams of 1-2 people. It is also clear that much of Scrum can also be applied.

Questions are what people think.

If the management, developer, software are all on board and believe that the values ​​/ principles make sense and strive for improvement, it will work. If they do not, then first get to the point that general thinking makes sense, and then figure out a separate team ...

Answer 2

The ideal team for SCRUM is 8-10 people. So, I do not know how you can make it work for such a small team.

Typically, management issues or agile processes are misunderstood by management people. Just by reading about the balance of successes in a fight, it creates attractiveness for people engaged in managing people.

There are two aspects to the entire SCRUM implementation:

• Processes: meetings, retrospective meetings, etc.
• Engineering practice: creating clear requirements (user stories), test automation, continuous integration, etc.

IMHO, here your guide looks forward to engineering practices and (maybe) some processes.

You can take them in parts to get a better shape, then you can be at the moment. (At least in the eyes of management ;-))

Answer 3

Maybe SCRUM is crowded here. Organize into work packages and core tasks.

The best way? Keeping it is just plain stupid. Do not inflate a project with high management overhead. You do not need to use software for scrum tasks. Problem trackers like Redmine / JIRA are nice to keep track of progress and assign tasks. But you can also use a board with several magnets and notes (task name). Thus, you can assign tasks through the board;)

Answer 4

In my experience, Scrum may still be relevant to projects in small teams of a couple of people with existing responsibilities. That's why:

• He still encourages breakthroughs and task detail.
• Sprints are still units of work that should not vary in scope or duration.
• Regular daily meetings continue to encourage regular discussion.
• You are still doing iterative loops.
• The burning pattern for tracking is still maintained.
• You still have a retrospective phase of continuous improvement.

All of them are equally important for 2 team members or 8 team members. Don't be beaten up by people saying “only one way to make Scrum”, or you need more than a few people to get it working.

Answer 5

Scrum is definitely crowded here. In addition, do not think that Scrum is a silver bullet, and you cannot implement it in your project. Read “Getting Reality” on 37-digit characters and some other things preservation resources, and you will find that working with an interdisciplinary team of 1 or 2 is actually a very impressive productive unit if 1 or 2 people are ready and capable.

As Martin K. said: “Keep it stupid. It's just 1 or 2 people, you don't need to have“ project management ”as such. Cut the shit and just do it.

(This does not mean that you should not monitor budgets, costs and measure progress, but do not waste time and money on infrastructure that is not needed)