Process, process, process.

Just another opinion.

I believe the most crucial part of an IT system development is understanding the business processes that you want to system/automate. Not just understanding them, all the activities are crucial, to collect, gather, and document the whole process into one complete diagram/flow where you can always refer to throughout your project (the Bible they say!).

During this time, if your business people or you yourself are still having a doubt on their processes, question them until this sentence came out from their mouth and recorded, “Yeah, that’s the job I have been doing all this while.”

Finalise it with a formal documentation. By this time, any relevant solutions that is out of their current official activities/processes/SOPs too should also be recorded.

I’m seeing this is the part where often loosely emphasised in a lot of project management teams. Then, when the requirements were passed to the programmer/developer, often what is developed not up to the expectations of the users.

To me, it is worth spend a time to ‘drill’ the business rather than jumping straight to development after collecting requirements. Requirements that came without basis/official business processes are ‘fairy tales’, if this happens, somewhere at the end of the projects, revamping, redesigning of the system will surely happen.

I’m not sure if Analysing was often misinterpreted or underrepresented. I know this part of PDLC might not give a sight how a complete result would be but it’s the lead. It will determine where the end results will be. It should be where the details should be dug, clarified, and thoroughly assessed. It is where the start of the planning is. Requirements collected must be detailed (not high level interpretations), must be UNDERSTOOD word by word by all levels, users and project members must both be in the same understanding.

Technical limitations shouldn’t be the showstopper. Once you are confirmed with the business processes, you should be able to map the system with workarounds/any technical limitations identified.

Until today, I couldn’t find a good theory/scientific proof to support this.

This is not just an opinion for that matter, it’s an inspiration.

business process

Goodbye.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s