Hello all,
I'm managing a 10 people project for a reputed stock exchange and most of the requests are for maintenance work. Documentation plays a big part that goes along with these requests.
My developers though good technical folks run into quality issues with documentation. How do I redress these , especially since I'm on a limited budget with no extra resource to spare.
I developed checklists working with QA folks and get cross-reviews done using these, but these seem to achieve nothing.
To me, the documentation task is simple (though probably demotivating to the team). How do I achieve zero defects on simpler stuff like documentation?
How do we manage quality on projects with limited budgets?
Please advise.
Thanks
A0C61ZZ
I'm managing a 10 people project for a reputed stock exchange and most of the requests are for maintenance work. Documentation plays a big part that goes along with these requests.
My developers though good technical folks run into quality issues with documentation. How do I redress these , especially since I'm on a limited budget with no extra resource to spare.
I developed checklists working with QA folks and get cross-reviews done using these, but these seem to achieve nothing.
To me, the documentation task is simple (though probably demotivating to the team). How do I achieve zero defects on simpler stuff like documentation?
How do we manage quality on projects with limited budgets?
Please advise.
Thanks
A0C61ZZ