Uh let’s look at an example right so this is one of the projects that i was involved in so let me share my experience as well but now take a minute or so to read through this case here then we will try to understand what is it that we would have done in the first one week of the project.
Okay all right so this example is for a no so this this particular project is for a large bank now this bank has multiple business units and multiple geographies right so it you.
Know the product they have to implement a fraud management system now fraud can happen in any of these business lines like there could be fraud in retail banking commercial banking or cards but there could be fraud in any of these and there would be a team which is sitting there and you know analyzing.
All these card instances and then they would they would uh you know work on it right so that’s broadly the high level requirement and so that’s a that’s that’s the kind of information you’ll get when you generally get into that right so you don’t even know the detail.
Functionalities okay now uh so you have to implement it in these multiple geographies and multiple business lines so that’s the overall scope of the project right now.
You the project manager and the technical lead right so three people so you guys have gone to the client location on day one what is it that you would do what do you think you should do on on on the first day are you going to say okay let’s start with the requirement for what is your.
First requirement are you going to do that no first day we would first understand um the exact as is uh situation we would go through multiple um documents and whatever we have and then prepare our questions which we have to ask um.
You know which we need clarifications on before going um okay so uh yeah so you know who will tell you those requirements who will give you those documents um.
And the um what to say the libraries are probably something like that in the companies where we would get the details of each project you need to know those key people in the project right now just recollect what we did in the last three days so we are looking at what is it that you.
Do in the first one week of the project and what the first topic what we discussed you would figure out who are the key people in the project correct right so do that so figure out who are all the key people in the project you should clearly know that you know who is the point of time.
Manager there then also identify you know the solution owner and who would be your sms so primarily these are the guys you should definitely know the rest of them if you know better if.
You don’t know it you can still figure out later but the first set of people that you should figure out is these three people right sm is because they are the people who are telling you the detailed requirements you have to interact with them on a daily basis so that is what.
You want to know and you know the um you know uh solution owner because he would review your account figure out who would be the project sponsor so you want to try to figure out so read through that uh you.
Know high-level information that i’ve given now there is ahead of this compliance plot compliance okay we don’t know we are learning here so don’t assume that even if it’s uh it will actually help you think through it otherwise you know if i just keep on telling you you might you might not.
Actually uh you know finally get to so he’s the guy who has given us the budgets also right so he’s signed that contract so you know if you go through this slide right so let’s go side by side and then see now that you have this context right so we have.
Multiple business lines you have multiple geographies and then you are implementing a fraud system for all these projects and for all these business lines and geographies and then there is this head of this compliance.
Who has signed the contract with the with the product company and then you are part of the product company and implementing the product okay so the first way we are going to do this we will figure out the key people right so we know you know at least from our.
Role point of view we need to be clear about who is the project manager so there would be one project manager aside so figure out what is his name is generally you’ll reach out to this project manager for anything if you need from the client side so the communication is like this right sorry.
So we call this as hourglass communication right so all your communications has to go through the project managers right on both sides right so the pms should be involved on both sides so we’ll figure out the project manager now the head of that.
You know the compliance would be the sponsor because you know he should not be this complex because you know it’s a multi-geography and multi-business line uh kind of projects you know the project managers was not clear how should we exhibit this project should it be like.
One goal that we uh you know implement everything or should we just take it up in phases each phase you know handling one business line and then one geography at a time so you know the.
Project type also had to be decided finally we figured out that you know an iterative model would be much more relevant to this why because you know first iteration we picked up one business line and one uh geography right so we picked up malaysian geography and we take business time and then implemented that after that each.
Duration we we rolled it out into the other markets geographies and business rights right so the project managers had that initial discussion in the first one two days and figured out how should we you know execute this part right so finally it was decided.
Uh you know in the next two days the disciple of you know we will do it in iterative model phase one uh or the iteration one we will go with this retail business line and the company the malaysian japanese okay so the guy who was heading that uh fraud compliance for that was identified as the solution owner right so this this.
Was a context right so we we figured out the solution owner and all the key people then the solution owner assigned some people from his team to tell their detailed requirements okay what are the fraud scenarios in the retail banking for this geography so you know i i clearly have that you know view.
Of who is going to tell me the detailed requirements and who is going to finally approve my brd right so that clarity has to come in an initial first one week right by the time the project plan is signed up you should you should know all these things right.
So you are not going to start the requirements right in the first day and you will figure out these key people then you know to the project manager for when he is preparing the detail plan for iteration one you would help him out with the detail plan for the requirements you you look at the sow and see you know within the retail bank what.
Are all the features that we are giving you right and what of them are there for malaysian geography so then you will prepare the work breakdown structure for it and then you know give those inputs to the project okay so broadly that is what you do.
Apart from this you will also you know agree on to the traceability template change management template this management would be taken care by the project manager in fact all these templates the project manager will take care of it but you’ll be sure that you at least identified these two templates you know the.
Traceability you know the change management at least ensure that these two are in place yeah i have been queried over here now this is a multiple business so that’s again you know something we should have to figure out right so when i actually figured it out the way it was.
You know aligned was there will overall head of compliance right and then under him where these geographies okay right so the multiple geographies were there and uh you know the each geography had one yet like malaysia had one human head and under him.
You know his business lines there were some people right so there were like some uh people aligned to this uh retail buying some from karamazov within the geography within the malaysian grant so again this structure might not be.
Relevant for another project so that is where you know identifying who is going to tell you the requirements who is going to approve it all that becomes important to you so isn’t that employment sorry can you repeat the question i think i missed it um uh the requirements.
Risk approaches which you had explained in the earlier slides that will also be a part of the brd yeah your requirements are anyway captured as part of the brd but you know we have still not got to that position of writing the brd yet so in the first week we are figuring out who are the key.
People then preparing the detailed plan of on what day what requirement i will discuss and then capture right so you will get that detailed project plan you will agree on those templates and then you know the project project plans would be signed up by both parties and the.
Planning phase would end right so usually the first one all these activities would happen in some projects it would happen within two three days right but that’s the first two three days what you spending the project so you’re not going to start your requirement on day one you’re not going to say you go to the customer and then.
Say you know okay start telling me the requirement because you first have to identify who’s your customer there right who is going to give you the requirement right so that’s the first step which is figuring out your stakeholders.
On what what day what requirement have to discuss that’s coming out as part of your detail plan right so those are the inputs coming out of this plan output coming out of this planning case so this case study will be given to us by uh either of a project manager or the subject matter expert whoever.
I mean there won’t be a case study kind of thing so you know you’ll understand get this context you’ll either get an email saying that right so the you know the the account team which has won the project that will briefly there would be a project kickoff call where you’ll be given the context just as i’m explaining they would say.
That you know we got this deal signed up on uh last week and then you know and this is the project which will be starting with and uh you know you will have to start working on this day so please uh come over to this location so so that project kickoff meeting would happen initially right so.
There won’t be a formal case study which is prepared eventually so i just mentioned it because i wanted to share some experience so that you know you can actually you know visualize how it happens in the industry right otherwise you know there’s no point just learning something unless you know that you know in the.
First post two three days this is what i’m doing and whatever i’ve learned i will apply it over here right so that is it’s purely uh you know uh uh you know aligned to the industry needs right so for the first two three days this is what you are going to do okay so we just get a problem statement.
Which we uh through via email and then we just read it and then according to based on that so it problem be a through an email or it could be a call which happens like you know usually you’ll have a kickoff call keep off meeting as we call project keep off meeting so generally you know that project.
You’ll be briefed that you know this is this is what has happened they will explain about that competitive reading and then we won this project and we signed that sow right so you also get that sow which will give you that high level view about dropping the scope right so that’s that’s a initial set of documents that you’ll get.
Okay so uh so that’s all what do you do in the first you know three three three days to five days or one week right you will identify the key people you will create that detailed plan work breakdown structure and then you know help out in the detail plan then you will ensure that all those.
Templates are there replaceability from the change management then a lot of other templates also is apparently the bid template also has to be agreed right so the project managers would also figure out how to execute this project should it be you know waterfall model or an.
Integrative model it’s all those decisions will be taken and then they shall want to raise okay so in the end of it you’ll have this people identified for the project who is going to tell you the detail requirements who is going to sign off your document you will have a detailed plan on a.
Day-to-day basis what requirement have to discuss with the customer what do i have to document so you have that clear day-to-day view and if there are 20 features you would have assigned you know day by 2 of which feature will capture on which day right and then you have that sow detailing it out and you know you will.
Agree on those templates the brd templates change management templates and you know traceability templates and you don’t have to prepare these documents from the scratch don’t expect that you will you know you you need to write the b id from the scratch they will give you templates all.
The organizations would have the templates like this so so there is a folder called as uh you know templates in the course material once it’s shared with you you can access this so you’ll have these templates right so broadly they’ll tell that process which is relevant for their.
Organization and you as an uh project team would follow that okay so i’m sharing some actual templates from organizations right so you know all you need to do is you know provide your project specifications otherwise most of the content will be more or less ready right so they are explaining you the.
Process of change management so all you will do is you will define your definitions and then you have the teams you are entering the you know the various people who use the project manager in the change management the whole’s name contact and that so the project specific details you are going.
To add and then sign it up similarly you know if you look at the traceability template as well right so you will clearly say the project name description right and who is going to do what um you know all those details are covered and then you would uh miss down all the features and then start.
With some instructions which you can use okay so these documents you are not preparing from scratch so you are not expected to you know create the structure ask for a traceability template they will leave you right and it’s perfectly okay to ask those templates nobody is expecting you to create it from scratch right why.
Because you know most of the clients would have their own templates if the client doesn’t have and you are working for a vendor directly the vendor at least would have worst case scenario use these templates but don’t directly take these templates and then say okay i know i have my templates from the users don’t do that because now you are not.
Expected to uh you know take any documents out of any organization so there will be nba classes will be in a lot of probability carry-on documents documents so even once what i’m sharing this a lot of it has been sanitized and you know it’s it’s taken from the public sources.
Also so so that you don’t uh you know get into trouble later okay but uh one word of passion when you get into projects don’t share any of your documents also right so people think it’s a small thing but you know you could even lose your job.
Right so people are becoming very sensitive these days and you know with the new technologies it’s easy to find out what kind of documents are going out the documents organization and you know ask for the templates and nobody expects you to you know create these templates right from the start.
Right so you can ask for the brd template uh wherein you know you will have this detail view of how to capture the requirements we’ll go through this later but i’ll be showing you how the template should look like so it will give you a structure of how you will capture the details and all that.
You know so you can ask for those templates and then okay so most of the times you will end up creating these documents so you fill up this change management plan maybe the traceability time plan and then your brd template.
All these things would uh you know come out primarily at that place so clear about uh the planning phase so what we accomplished in the last three days is we learned what is it that you do when we are onboarded onto the past so usually the first three to five days you know you would identify the key.
People you create the project plans you would set up the frameworks for managing the scope and requirements traceability and change management and you would agree on all those templates like the bid template status reporting template all those templates should be agreed upon we call that as a project charter document all that will.
Be part of the project so the primary responsibility would be the project manager you would contribute to this and make sure that at least the change management traceability and brd templates are agreed upon okay clear about this any questions so so that’s what you would do as part.
Of the plan um this use case which we have um can you also be giving us some use yeah we’ll cover cases in details as soon as part of your documentation so we have still not got that speech where we are documenting the requirement now first three days we know what we.
Need to do right so be clear about those three days then actually the requirement should start right now say you are onboarded onto this project part compliant system and what is hot compliance system or you know you will be uploaded onto a mobile banking.
Application or a credit analysis system right or a healthcare management system right so requirements could be anything and you a lot of times will not have much clue about what it is so where do you start the requirement how do you understand it how do you engage with the customer right so the.
First the the next challenge what we would have is how do we understand the requirement right so you cannot completely depend on the sme to tell you the requirements if you are if you are doing that then there is no need of the role of a business analyst.
You know the sme could have directly told that to uh to the development unit okay so it is your responsibility to ensure that you have asked him all the questions regarding the requirement and capture the details that is where you know the the role of.
The business analyst should be okay so the next three sessions or so we would understand how to engage the customer how to ensure that we understand all the requirements and as of now we know that you know it’s always a one-on-one discussion right i.
Will go and then talk to the customer he will tell me the requirements and i will document it right so but that’s not the only way you could conduct workshops you could conduct a brainstorming session you could have a reverse engineering session you could do prototyping you could you could do a chat session there.
Are multiple ways in which you can engage the customer to understand the requirements so the next three four sessions we would understand all those techniques all right so you know broadly there are 10 ways in which you can engage the customer and some of them are context-specific so.
You know they they would be relevant only under a particular scenario only under certain conditions those techniques would be effective otherwise you cannot use restrictions right so we look at each and every of those techniques and then figure out you know how to approach.
The requirements for that okay so maybe you had a question i thought you were asking something on your finger hello all right so i i think we have some five more minutes and i’ll briefly introduce this and then we’ll.
Stop there okay so uh before you even get into the requirement installation before you start your requirements okay make sure that you have some you know documents from the planning.
Planning phase or even before that you have some documents which you have you know clearly identified okay so that becomes the input to your elicitation tokens and what is the output that is coming out the output is nothing right so basically there is no deliverable unlike a planning phase you.
Prepare the project project plan your stakeholder list rsa metrics maybe and your templates have been agreed all that we are part of your planning but elicitation there is no document coming out right away right so that document would come out as part of your doctor you know the next chapter which.
Is analysis and documentation now in fact both of them happen simultaneously your day would start like by understanding the requirements so maybe you know the first two three hours you will engage with the customer understand the reformers and spend the next four or five hours.
Documenting them right now the techniques for understanding the requirements are different from the techniques for documenting right so elicitation you would use a prototyping or a workshop to understand requirement you would use a use case or a or a you know wide frame to document.
Your department right so just that since the topics are different we are segregating them and learning differently but a typical project your part three and part four would happen simultaneously right a typical day of yours would you would spend doing requirement.
Elicitation and simultaneously the same way you will defend that requirement also okay so all this would be part of your requirements definition phase in in the indians life cycle okay so that’s the context okay.
Uh yeah any questions um before planning before requirement planning and all that involves more role of the project manager yeah not project manager it would be more of an account team and then the.
The business development team so they would work on those uh you know winning that project and getting all those right so during the kickoff meeting you’ll get that context so the pro the details what i have mentioned in that case study right so usually the you know the the bdd team or the account team would give you that context and say.
That no we won this project and then you know this is the value yeah all that details would be given as part of your kickoff initial uh you know transition okay yeah so guys are you following.
Everything are still confused uh you’re you’re able to visualize how things work in the project now at least in the first three four days are you clear what is it expected out of the business service world yes okay.
Okay yeah see all that would be part of the requirement illustration so when i say requirement registration it’s not just you are understanding it for the customer but also ensuring that you know both of them understand it the same way so validation also happens right so both of you agree okay now this.
Is the requirement so all this process happens as part of your elicitation and then documentation also you will write it in a document and then take it to the customer right so you’ll prepare the use case and then take it to the customer the customer would provide his feedback.
Okay and then you know you will update it accordingly right so that validation happens so it’s not that you know the validation would not happen and you know it would be a process of you know you know most of the times the feedback would come in during your registration session.
So let’s say you know first day you would understand one requirement and document it the second day you go and then show the document say that you know what students requirement have documented so look at it and then if you have any feedback you give it you let me know right so that way you are under getting the feedback also.
Right and then that day you also under you understand another requirement let’s say requirement too and you’ll go back and then document it so that’s how a typical uh day-to-day would go about oh.
Okay right so uh as inputs make sure that you have this scope document so primarily the sow are the business case document which is clearly listing down that these are the 20 features or 30 features that you have to deliver as part of the system okay so that has to be a definite input.
To your registration phase the next one is the output from your planning phase so your people who are going to give you the detailed requirements the the stakeholders and the sm means the solution owner and all those people you are identified.
Make sure that you know them before you start illustration otherwise you don’t know who has to tell you the detail requirements and who is going to review and then sign up right so the end of it you know you will talk to somebody else and then you know if the solution is different.
It’s not aligned to that person you know you’ll be wasting a lot of time right so you’ll figure out all that then you might also identify which techniques would be relevant because you know by the time you have got the context of the planning phase itself and then thought you know what for this project i can use a prototyping reverse engineering and a.
Workshop along with the interviews so these are the four techniques i could use right so you could do that and then you also identify how are you going to document the requirements i’ll use it i’ll use wireframes for the screens and then the use cases for the functionality.
So you could figure out those two tools and frameworks that you’re going to use right you also you know take the traceability strategy and fill it with all those you know scores and then you also know once once you have all these documents.
Then you would start your requirements registration process right but make sure that you have these documents the most important one you should know the scope of what are all those 20 30 features that that were agreed upon and you should have the list of people.
That are going to give you the requirements right the sme list okay these two main things make sure that you you are aware of it in the and then you can start the registration process okay okay so uh.
We will not get into the techniques now we’ll uh you know when you look at it uh later point uh we must start it next week right now the reason why we need to spend a lot of time on the requirement in station i think you know.
This this this cartoon summarizes right so it’s basically everybody has a different perspective and they think that they are right and you know they don’t really care whether the other person also thinks the same way or not right so the customer might want.
Something then they might have told you something different way you could have understood it in a different way the architect would have designed it in different ways the programmer could define different way finally you will deliver something else right you will deliver.
Something like this like this right so you know a business analyst plays a key role to reduce all these conflicts okay and how are you going to do that you know we will understand it in the next few weeks okay so we are going step by step so first part of what we do as part of the.
Planning we understood now we will understand how to understand the require how to you know elicit the requirements from the stimulus and then you know understand the requirement in detail after that we’ll document it so that everybody can understand so we have to learn those documentation techniques so these two are the more.
Most important topics then you know we also get involved in testing that we will look at later okay so the the next three four sessions at least should be on this requirement illustration what are the different techniques which you will use to understand how do you approach.
The requirement health station classes okay so we will start this on monday same time okay thank you everyone and have a nice weekend good thank you thanks
| PIZZA HUT GENIUS STRATEGY | BUSINESS CASE STUDY 
