Just do project management, the software is going to be accepted, please enlighten me

微笑死神

Don't worry about those documents, just find some junk templates.

5583581

Haha. I think it's good to invite customers to dinner :(

doomlast

I personally think that the quality of the software is the key. It is very important for both myself and the customers.
The quality of the software is guaranteed, the customers are also very satisfied, and their understanding of the software will be improved.
Of course, inviting customers to dinner is a good way to deal with business affairs, and you can also try.

zz719181

Judging from your current management situation, I suggest you do more integration to stabilize the system, through continuous integration + testing, combined with your scope of needs, tailoring, and clarifying that those are the core, high priority, and costly Efforts to ensure it does not mean that all submissions must be submitted during acceptance. Customers still allow a little deviation.

It’s still going to be inverted according to the progress and see how much time is left, what else can be done at this time, what are you doing, and the idea must be clear, and the system must be upgraded to a better state every day, so that everyone should not be discouraged

niushi0159

Following........

Peter1984

1. Do a good job in software progress management
2. Refer to the chapter on system design in the CMMI model

QQ1168184

For the first project, it is basically necessary to treat it with an absolute learning attitude.


The project design differs greatly. This is normal. Don't put too much pressure on it.

For example, for the many documents involved in software engineering, lz as a manager should still make up.

Some basic data and design modification records are required.

djxok121

I have also experienced your stage, but there are still 7 fresh graduates in the project team. In terms of general direction and strategy, you can only plan by yourself, please refer to the above together.

What you need is to list a Checklist to see what to do, check one by one, and what risks will be brought if not done.
Please take a look at the leaders above.
Then make an announcement in the team, and each checkpoint must reach a consensus on how to deal with it, and obtain everyone's commitment, so that the execution is very powerful.

wangyaohui

Also care about this issue

QQ1168184

[Quote=Quote the reply oflaylay008on the 1st floor:]
Need to sort out the design ideas of the software (because it is very different from the earlier design, there are many changes),
-------------------------
????
Acceptance soon?
In theory, this should be about to fail.
But our environment is like this, and we don't think this is a failure.
It may also be that you are too worried. It's over when it's over, don't worry about so many bugs and defects
Patch or upgrade later
As long as the system is stable and the basic functions are similar,
Party A also wants to check and accept, finish early
I also do...
[/Quote]

Well, the top one.

That's right, lz doesn't have to worry too much, it's useless, because bugs are there every year and they can't be killed.