Quality always matters whether the project is too small or huge.
If you have been assigned a very short term assignment for 10 days or 2 weeks like that and you are only who has to deliver it. So as a self-manager and self-lead, you have to get requirements, do POCs and bla bla.. activities required for the project.
Short term projects don't give enough time to do all these activities in detail so the information needs to be precise.
Following things can help you in better execution -
If the assignment is very short, this is very important to
know the purpose of the assignment and identify the scope after gathering the requirement.
Do not stop gathering the requirement at the level of what you are feeling will be delivered by the rest of the remaining days otherwise it may mislead the actual requirement. Which may put you in crises at the later stage. Try to capture the requirements in JIRA (if you are following Agile) or similar tool. Do it yourself or ask Product Owner (PO) (Recommended) to do that.
Sign-off on requirement
Ask stakeholder (client or PPO) to review the requirements and give the
sign-off before starting the development. Try to convert verbal communication into written format so everyone is clear with updates.
Clarity on Expectation/Goal
To make the goal clear,
highlight the unknown items or dependent items/blocker etc as soon as possible to right concern person. Don't miss to consider documentations, demos or meetings which are an important part of all projects and you have to do those as well. Sometimes it becomes problematic when you focus on development only. You can also make a checklist for your own reference like:
- Documentation of x feature
- Infrastructure setup
- Demos/Meetings with x person on n times
After this exercise, you can do estimation and tell stakeholders what you would be able to deliver in remaining days considering what stakeholder is expecting. Highlight risks, assumptions, blockers, dependency and CR (change request).
This is the best practice and most important part of project development, it provides the accurate understanding of the implications of a proposed solution, Which help the team make informed the decision about the proposed solutions. And can expect change it proposed the solution.
You must send the impact analysis report to the stakeholders/POs to get that discussed and come up with a better solution.
The Project Closure Phase is the last phase of the project life cycle. In this phase, you will formally close your project and then report with following things.
- What has been completed?
- What is pending/blocker/or can't be done?
- Is there any support needed if the system is not tested along with development.
- And if you are using JIRA, try to get UAT done/client accepted done before you actually send the final mail.
- If there was more scope which could be improved and not completed, get that informed to your superior and stakeholder with the clear picture.
Takeaways - Never give agreement on verbal communication and unidentified areas, try to do analysis and then go back to stakeholder and save yourself from being alienated.