How to support requirements for the project are always up to date? Tools?

The question is more for those who ate in project management. The bottom line: there are requirements for the project, first review TZ, then in the form of tasks in the tracker, they are gradually being implemented in the developed system (SOFTWARE), new, something changing, something the customer changes his mind (the part of the task lose their relevance), etc.

And then BAM - a solid-the pattern and no, comes like a new developer to a project or even a new Manager starts then the people to ask, and how do we need to work ? The tester comes in - "I was sent to test, and tell me how it all should work ?".

Guys, what system applies to control requirements FOR what you keep in there? - tasks, or UserStories? Where to poke to read as it's all in the mind realize ?

I don't PM know what you need to kick PMA, but really don't know what it should it's stupid to track manually, and the documentation in the wiki or in a Google Doc?

Thank you all in advance.
March 19th 20 at 08:49
1 answer
March 19th 20 at 08:51
> How to support requirements for the project are always up to date?

Good afternoon. Blitz the answer is to regularly update the information )

> Tools?

Straight to the point - I am the Creator of this tool. Details on the platform vc.ru ->

> The question is more for those who ate in project management.

Almost 15 years dealing with this issue in the framework of software development. Webinars, courses conducted, wrote wallpapery, in the end I put the whole experience into the product as the only way in fact to transfer and consolidate the skill was soft.

> The bottom line: there are requirements for the project, first review TZ, then in the form of tasks in the tracker, they are gradually being implemented in the developed system (SOFTWARE), new, something changing, something the customer changes his mind (the part of the task lose their relevance), etc.

Requirements will always be evident because attention is limited - we live and work in a situation similar to games like "strategy" - when the map is foggy we can't see anything when we "get" and "in the flesh" we can see that there we see "new things." Whether they were new? no - they are new only in our attention. You think right.

> And then BAM - a solid-the pattern and no, comes like a new developer to a project or even a new Manager starts then the people to ask, and how do we need to work ? The tester comes in - "I was sent to test, and tell me how it all should work ?".

How it works - is determined in the beginning, but it is better to take in the system, have all the answers to that as there is knowledge about the result and how it is transmitted and how it is stored.

Also the effect in the game-the strategy is the same, I call it the "flashlight effect" - where the "Shine" out there and all you can see, but in the other corner where no flash (no focus) no longer visible.

As in the strategy - when you leave from the event and not your units on the map - there are "fixed" your last "vision of place", and in fact it will again be different when you come back.

> Guys, what system applies to control requirements FOR what you keep in there? - tasks, or UserStories? Where to poke to read as it's all in the mind realize ?

Tools and never appears for 15 years, I don't know what is the reason, although the question on the surface - that's why I made my product for yourself and for friends - and grew a little more.

The short answer in the group already gave the difference Jira / Teamsite / Truly and stuff:

// quote

One key difference - none of the above perechisleny products are not "forms" digital configuration of your product. In all of these products you need to do yourself, having the skills and organizational capabilities of analysts and designers architecture, documentary and system engineers.

Practice Mjolnir is not entirely clear from the go - but by following them you can just work as if they worked in other systems, but the entire context will just accumulate and you will never have someone "exchanged" knowledge and lose the context when changing employees.

But since I'm on this soil live a long time I will say this - the change of staff this is such a cute story which is told at conferences - and how to fight it using the wiki and confluence.

The problem is the other people can't formulate goals and their plans so that the problem of transmission of these ideas between colleagues is not such a problem because one says one thing and the other hears and understands the third.

Mjollnir is designed so that on the way the current periodically "included" thinking, and each time it became easier and easier, by keeping the system exactly the information that is important for the project, and colleagues, and in the absence of the need to "excess" or redundant information, which can be popular as a technique or posterization - but not in the overall context of the result, and is the information of conference and article noise.

// end quote

> I don't PM know what you need to kick PMA, but really don't know what it should it's stupid to track manually, and the documentation in the wiki or in a Google Doc?

Try it, I have make videos in a group telegram where I can make out on the steps of the development

> Thank you all in advance.

I hope not banned - it seems to be a direct answer to the question.

Find more questions by tags Project management