3. IBC Method
STEP 1 STEP 2 STEP 3 STEP 4 STEP 5
Define the Problem
Structure the Problem
Gather the Data
Synthesize the Data
Structure the Report
& Create Buy-in
4. Define the ProblemSTEP 1 STEP 2 STEP 3 STEP 4 STEP 5
SO
EO
Avoid similar
coding problem
Avoid adopting
wrong SPECs
Initial
Discussion
5. SO
EO
Systematic Issue Artificial Issue
No unified
storage space
PMProgrammer
No official
announcement
No double
confirm
Not checking email
Not implementing
Not informing team
members
Structure the ProblemSTEP 1 STEP 2 STEP 3 STEP 4 STEP 5
6. Gather the DataSTEP 1 STEP 2 STEP 3 STEP 4 STEP 5
Internal
Interview
We don’t regard redundant code as a problem
We understand code spec but not knowing the
indentation rule
Requirement spec document is now V.1.3
The document is received from e-mail
7. Synthesize the DataSTEP 1 STEP 2 STEP 3 STEP 4 STEP 5
No unified
storage space
PM - No official
announcement
PM - No double
confirm
PG - Not
checking email
PG – Not
implementing
PG - Not informing
team members
8. Structure the Report &
Create Buy-in
STEP 1 STEP 2 STEP 3 STEP 4 STEP 5
• Make a Group Chat room
• Add project members
• Hold MTG if big change occurs
• Have MoM after MTG
• Use cloud file sharing service with version
control feature
9. There is no best but the most suitable
Business Process.
Thank you !