Let me describe what's in the project, The people involved in this project is:
- Company owner
- Project owner
- 4 software engineers
I'm one of the software engineers there. The responsibility/what they do are:
- Most of the requirement is defined by them and transferred to the Owner of the project (I assume this is done orally, there's really no documentation about this)
- Brief the software engineers about the requirement from the company owner by telling it in the meeting.
- Verify the progress by watching the application runs demonstrated by the engineers and sometimes by handing the app to the future user of the app.
- Listen to the Company owner/user feedback and translate it to a new requirement that soon briefed to the engineer.
- Discuss with the consultant/engineer what is the best practice when dealing with a problem/requirement.
The project owner has other many responsibilities, so the availability is somewhat limited.
- Get asked opinion from the project owner about what is the best practice from a problem/requirement.
- Tell/influence the project owner if some requirement is just too difficult to manage later.
The consultant just appear once in a while, so doesn't always available to engineer onsite (maybe available to the project/company owner)
- Develop the project
- Writing/take notes about the briefed requirement
- Demonstrate/report the project progress.
Note: this is from my point of view. there's no handbook about this
Project Management Tools
- Notepad/ Text Editor
The project owner admits that the requirement isn't all clear, it needs to be discussed with the company owner and all the potential user. So often the requirement changes.
The requirement isn't documented by a framework so it is just a text from a full meeting. The meeting text isn't always verified by the project owner. The text is just a brief description of a new feature and the constraint, not really detailed like a flow diagram, sequence, etc.
I think the project owner just assume what he thought about was already stated in the meeting and the engineers wrote all the correct description about it and will implement as is.
After a meeting passed, the text will be posted to slack and break down by the engineer to the trello board. The project owner and the consultant can read the slack and the trello board. But there wasn't any complain/correction made to those document. I have a feeling, there may be an occasion where it's not correctly written. But seems it just got away every time.
The structure of the trello card isn't defined either. Sometimes it titled by the module engineers worked with and contains checklists of the break-downed task from the meeting (not really detailed) . Sometimes it is just a single task with a little bit detailed description . Maybe that's why there's no complain/correction, but I already talked about it. The project owner & consultant seems just agree and let the engineer take care of it.
And in my opinion, the review process from the project owner seems doesn't complete. It just jumped from one to another feature. When it seems partially complete the project owner already jumped to review another feature. And sometimes just adding more requirement to be done. When I asked my teammate, they feel that although we finished developing a feature, it doesn't feel complete.
I want to propose better project management for this situation, but I haven't really had the experience to say. What kind of project management can be put into work there? I read somewhere that agile is good for prone to change requirement. Should I say agile?
But really, I haven't had any experience about it. I'm afraid, by just doing what I partially understand results in more hassle than good. I want all of the party satisfied by working on this project.
I already talked about this problem with the project owner and all the engineers. We agreed that we'll discuss this in the upcoming meeting.