Product Thinking And Agile Frameworks Full Course 2026 | Product Thinking Tutorial | Simplilearn

Simplilearn| 03:39:55|May 21, 2026
Chapters8
Sets the stage by noting that firms want teams that deliver the right product for the right user, highlighting the move toward hybrid and flexible methods.

A practical tour of product thinking and agile frameworks (Scrum, Kanban, Lean, XP, SAFe) with Jira, user stories, and canvas tools to turn ideas intoDelivery-ready products in 2026.

Summary

Simplilearn’s comprehensive course walks through why modern teams must build the right product for the right user at the right time. Suryange Tanna frames product thinking as a way to understand user needs, market signals, and business value before coding. The module then pivots to real-world case studies—Netflix, Uber, Amazon, Blackberry, Yahoo—to illustrate why some products succeed and others fail due to misreading customers or market dynamics. The course contrasts agile mindsets with traditional waterfall, emphasizing fast feedback, small releases, teamwork, and continuous improvement, before diving into popular frameworks: Scrum, Kanban, Lean, Extreme Programming (XP), Crystal, and SAFe. It then tours a toolkit of product management methods—stakeholder alignment, product thinking canvas, business model canvas, design challenges, user experience maps, wireframes, proof of concept, prototype, and MVP—and shows how to move an idea from a problem statement to a deliverable MVP. Through hands-on explorations of Target/Walmart expansion failures, the Amazon story, and the Netflix evolution, learners see how customer insights and iterative testing steer strategy. The course wraps with practical Jira training, epic/story structures, backlog management, and how to orchestrate large programs with SAFe versus lightweight Kanban. By the end, you’ll grasp how product teams think, how agile teams operate, and how to convert ideas into user-relevant products at speed.

Key Takeaways

  • Jira is used to manage epics, stories, and backlogs, with sprint planning and boards guiding delivery.
  • Agile frameworks (Scrum, Kanban, Lean, XP, SAFe) offer different visibility and flow controls to suit startups and large enterprises alike.
  • Story points encode effort, complexity, and risk to help prioritize work without committing to exact hours.
  • Product thinking canvases and the business model canvas translate customer problems into testable hypotheses and monetizable plans.
  • A/B tests, alpha/beta testing, and rapid prototyping are integral to validating ideas before full-scale delivery.
  • Epic-to-story hierarchy in Jira organizes large goals into manageable, testable units.
  • Stakeholder alignment and transparent communication are essential for balancing customer, investor, and developer needs.

Who Is This For?

Product managers, agile coaches, software developers, and business analysts who want a practical, modern playbook for turning ideas into customer-loved products using agile practices.

Notable Quotes

"According to PMI project performance across organizations is around 73.8% and the use of hybrid project approaches has increased by 57%."
Opening lines set the case for flexible, modern delivery models.
"Product thinking helps you understand the real customer problem and agile helps team build, test, improve and deliver products step by step."
Core definition of the course theme.
"Fast feedback, small releases, teamwork, and continuous improvement are so important."
Key agile principles highlighted early on.
" backlog says whatever you have in mind, jot it down over here in the backlog. Whatever you would like to do immediately, whatever you'd like to do it now, please do it over here."
Explain Jira backlog and backlog grooming.
"Epic refers to the final objective you are trying to achieve and stories are the deliverables that make up that epic."
Clarifies Jira terminology and hierarchy.

Questions This Video Answers

  • How do Scrum, Kanban, and Lean differ in practice for a mid-size product team?
  • What’s the difference between an epic and a story in Jira, and how do you estimate story points?
  • How can I use a Product Thinking Canvas and a Business Model Canvas together for a new product idea?
  • What are practical ways to validate a product idea with alpha/beta testing before MVP?
  • How does SAFe scale agile in large organizations versus a Kanban-only approach?
Product ThinkingAgile FrameworksScrumKanbanLeanExtreme Programming (XP)SAFe (Scaled Agile Framework)JiraEpic/Story/BacklogProduct Thinking Canvas and Business Model Canvas
Full Transcript
Hey everyone, welcome to this product thinking and agile frameworks full course by simply today companies are not just looking for people who can build products. They are looking for people who can build the right product for the right user at the right time. According to PMI project performance across organizations is around 73.8% and the use of hybrid project approaches has increased by 57%. which clearly shows that modern teams are moving towards more flexible ways of working. Also, many organizations now use agile, DevOps, hybrid models to manage product delivery faster and better. Today, having an idea is not enough. Many products fail not because the idea is bad, but because teams do not understand the user, the market, the business goal or the right way to build and test the product. That is where product thinking and agile frameworks come in. Product thinking helps you understand the real customer problem and agile helps team build, test, improve and deliver products step by step. So in this course, first we will understand what product thinking means and why successful companies focus on user needs, customer feedback, business value and market changes. Next we'll look at some real world examples and understand why some products succeed while others fail. We'll also see how companies like Netflix, Uber, Amazon, Blackberry, and Yahoo changed because of product decisions, customer behavior, and innovation. After that, we'll learn about the agile mindset and understand why agile is different from traditional waterfall project management. We'll also discuss why fast feedback, small releases, teamwork, and continuous improvement are so important. Then we'll explore popular agile frameworks like scrum, canban, lean, extreme programming, crystal, and safe. You'll understand how these frameworks help teams plan work, manage task, improve speed, and deliver better products. Next, we'll move into product management tools and techniques like stakeholder alignment, product thinking canvas, business model canvas, design challenges, user experience map, wireframes, proof of concept, prototype, and MVP. Finally, we'll connect everything together and understand how a product idea moves from a simple problem solving statement to a prototype MVP agile execution and final delivery. And by the end of this course, you will understand how product teams think, how agile teams work and how to turn an idea into a product that users actually need. Also, if you are interested, check out this program, professional certificate program in AI product development and innovation by IM Kodi code. Now this program helps you learn how to build AI powered products, use generative AI, create AI product strategies and manage the complete AI product life cycle from idea to deployment. You will learn through live online classes, hands-on project, real world case studies and capstone project. After completing the course, you will be getting certificate of completion from IM Kore and also qualify for IM's executive education alumini status. The program also includes career support, resume assistance, interview preparation, and 3-day campus emotion experience at IM Cody Code. So, you will get started and learn how to build better products with product thinking and agile frameworks. Now, before we get started, here's a short quiz question for you. What is the main goal of agile? Building everything at once, deliver in small steps with feedback, avoid customer feedback, or work with planning. Let me know your answers in the comment section below. So, without any further ado, let's get started. L, why don't you have a look at this? Uh, a fast growing. Have a read quick. A fast growing grocery delivery app 40% generate. Delicious asked for a complete checkout redesign before the holiday season. All right. Check out redesign is how do you simply buy something from an e-commerce website. Simple. Okay. This is what happened. Now, now I'll give you 30 seconds if you if this will happen for project ramp up. Okay. Now learners, I'll give you 30 seconds. They did they met with, you know, only sales and marketing people. They focused more on the documentation, lengthy documents to developers, you know, timely insights they couldn't get and they had restricted visibility or flexibility. Sorry. My question for you is if you were given this design, can anyone elaborate how would you or what approach would you take to completely redesign the checkout system? Let's see who would like to take that up. Go ahead. Open to answers. Pravin, Priyanka, Shikha, uh maybe Sumeda, Seali, anyone would like to pitch in, you know, we'll take it up. How would you take this approach? what approach would you take so that you can uh you know make this working rather than the way it was done. So um hi I will create a prototype kind of mockup to create my idea what I'm thinking and this is like a sample. Absolutely. This is my visual like uh picture what we are trying to build right so Shikai is saying that Suryan you know why do you complicate things just simply show a design on how this will work right Shika? And if this thing gets quick then you can send it for development and then you can test it. So in this way you can have multiple designs whichever way or whichever design fits you give it for development and based on the inputs that you're getting you deploy it. Cool. Next point. Next point. Thank you Shika. Any other learner has got a different approach. Redesign the only user. Talk to customers. Ask them why they're churning. Great. That's Priyanka. That's correct. So you follow V model P for the application. Okay. OMA, why don't you elaborate in easier words for everyone to understand? Okay. Any other approach anyone else has on how do you take it better? Because what Shikha told what Omar and Pranka have given they make sense and that's what they did customers actually someone mentioned talk to customers right so they didn't talk to customers the reality was customer they needed some clearly delivery slots and instant payment options they didn't talk to customers they got stuck the development spi priorities again which was not needed the solution missed the mark card ab card card abandonment remained high and uh holiday marketing push failed Learners, how do you Okay, here's a small question for you. Okay, now listen to this. Today, let's say you have made a new way to check out. Okay, you've redesigned this entire thing. In a very layman terms, you will before opening it to users, before opening to the users, how do you get feedback whether this is working or not? Because to get feedback you need to deploy it so that everyone can use it. But the moment everyone starts using it that's when your system starts showing problems and that's when people think it's a failed product. So how do you get out of this loop learners wherein how yeah Shika go ahead over to you. Yeah we will test in like as a BA like we will test in Q environment. So first internal train and then before go in production it will go live. So we can find the internal testing what are the absolutely drawbacks. That's right. That's right. Thank you Shika. Any other learner got any other input on that? Uh we could also go with the alpha and beta testing and absolutely right. Absolutely. Hypothesis like build a hypothesis do testing as well. That's right. Go ahead. Reena build a hypothesis and do the AB testing whether this is actually viable. Good. So one way how pranka everyone we we used to do was we would first deploy something on mod server before we move it to the production server. So learners usually one way that we commonly adopt is have a different server for internal testing usage. If it gets approved then you move it to the production server. That's how work usually happens in tech. So they have different servers for testing and internal usage. Okay. H okay. Now 10 seconds to read what is being shown on your screen. It is similar to what we have already discussed yet. Okay. So I'll give you 10 seconds to read then we'll continue. Hello students. Tanoshi. Just give me a moment. Tanushi. Learners. Do you also hear Tanoshi's voice breaking? Because Tanushi I just heard your voice and I saw it and I heard it breaking. So yes, Pranka Omar are also feeling that your voice is breaking Tushri. So why don't you go ahead and try again? Is it audible now? Perfect. It's perfectly fine. Go ahead. Yeah. Yeah. So actually my uh question it's not a question it's a request because uh everyone here is experienced I feel so but few are like nonexperienced. Mhm. So can you take it in some uh easy pace? Oh sure. So that we can get through it because how the production and all so it's completely rapid. Got it. Got it. So we'll take some examples wherein we can work and see that everyone fits in. By the way, by the way, thank you Tanushi. However, whenever you have these kind of doubts learners, try to bring it immediately. Okay. So next time if any learner feels the same, just feel free to pitch in and then there we can switch to something. It's easier. Okay. All right. All right. I if you have read this slide quickly type yes in the chat box because then we have a new problem coming up if you have read that slide learners now I want you to read this then we'll have a small discussion on this we'll take a break at 900 p.m. on this by the way. Okay. So, just read this and then let's get in a discussion. Thank you, Rahul. Okay learners as in you know when almost all of us are reading. So why don't we do this? Why don't we get a pen and a paper and then we start focusing on the problem over here. I'll give you 10 seconds for everyone to get a pen and a paper and then we can start. learners the question says that Target or you could say a similar company to Walmart okay they decided that let's say enter Canada we doing very well in US and they decided to open 100 stores within months now learners remember one thing target stores are if I'm correct me if I'm wrong okay aren't they pretty huge learners do you agree yes or no target doors. Do you agree? Yes or no? Now you're opening hundreds of these member. Do you agree with the problem? Yes or no? Yes or no? Do you agree with the problem? Hundreds of stores. Just imagine the cost. Not only the cost of leasing. Imagine the cost of land plus construction plus let's say cost of labor inventory. Do you agree with the cost that is involved? Yes or no learners? Now, now my question for you over here is that since they opened over 100 shows and within two years they realized they had done a huge mistake. They incurred a loss over $2 billion. Okay. Could you tell me what could have gone wrong? Let's see who would like to pitch. Anyone can pitch. Tanushi would like to start. What could have gone wrong? Uh any other learners now you can pitch in that what do you think could have gone wrong in this expansion by target? Shikha over to you. Yeah, since I'm in Canada so I can easily tell uh so first of all they have to do the market strategy like in they there are a lot of competitors so they have to see um what they are what they are uniquely offering so if they have to survive in the market so first point if I'm taking incremental rollout so the scale expansion was big instead of 100 they should start with two or three stores just to see how the response is coming and then uh secondly ly in terms of inventory. So um if there's offering similar product and like for example high price so no one is going to buy right and there is no variety in terms of like inventory so uh the customer will go to other uh market. Got it. Got it. Got it. So you mean to say that they could have gone with a little bit incremental kind of an approach and at the same time they should have understood the market requirements better. Correct? Yeah. And in uh like they start with 100 stores no feedback loop that means they didn't gather the response from the consumers how they feel about the store and the products. So all these things you know pile up and that leds to the failure of this. Great. So let's let's say they invested a lot of money in the very first place. May I know the reason? Anyone can speak. May I know the reason why a company like Target, it's not a startup. It's a well established company doing very well in US. How can a company like this commit such a mistake that you know suddenly they spent 2 billion said okay we'll take the risk and so on and so forth. Go ahead. Can anyone tell me some reasons why this could have happened? I mean obviously they would have better people to manage right they would have people who knew agile they would have people who understand these concepts right just as we are able to discuss so can anyone tell how could they make these kind of mistakes there's a disconnect with what they expected the customer wanted um necessar like certain products um say across the a state would nec necessarily sales at high volume in one end of the state may not be the same result in the other end. But just because it's that state in particular, oh, we can we can put this drink, you know, in this area and it'll sell out, but it won't happen that way. Yeah. Especially if that if the east end of the state doesn't know much about that product, but it's very popular on the other end. Yeah. you'll sell out but it's like they didn't do a market research to see okay what the response would be with customers. Cool. Makes sense. Thank you Adrain. Any other learner who would like to pitch in on what wrong? Rahul maybe you would like to go ahead. Uh Shika we'll come to the solution in a moment. Let's see what the exact problem could be. Then that time we can you can speak out your solution. Go ahead Rahul any suggestion any reason you could figure out maybe Tanushi Omar Pravin Priyanka Sumedha and anyone yeah even I might feel that uh there might be a controversy on regions like in some regions people opt for those things like these stores and in other regions they think uh they don't go actually this problem has occurred from my end from our Mhm. Mhm. So what people think is uh uh rather than going and buying there we can get it on blinket and all or else Okay. Or else one more criteria is over confidence. Got it. Yes. Maybe the company became complacent. Right. Adding on to what Tanushi and everyone mentioned over here learners. Do you know? Do you use this? Yes or no? Overestimation of their branding. That's right. I hope everyone uses this brand. And let's see who can answer what was the first product they started selling on this platform. The first product books. Books. Absolutely. Right. Right. Now, now, now later they scaled to everything. Everything means everything. Today you find everything on Amazon, right? How did this happen? Because when they launched books, they got continuous feedback. What different products are people buying from other e-commerce platforms? Remember 2001.com crash. Before that you had lots and lots of companies, e-commerce companies selling anything and everything online. Medicines, books, shoes, toys, clothes, everything had started gone online because of this.com. And then Amazon realized let's have a look what else is growing on e-commerce. They already had a good user base because of the books part. So that's how based on the feedback on what people are buying more they went in acquisitions on what products people are buying more so let's why don't we buy that e-commerce platform so that we directly onboard the users that's how Amazon scaled and that's how they introduced their prime membership plan because they had access to data starting with one category of books. So target learners didn't have access to that level of user insights and even if they had they did not take action points on that. My question for you is my question for you is if you were to get this thing off ground learners okay as Shikhan everyone told you have opened two stores. All right Shika you mentioned two to three stores now everyone listen to this carefully. Yeah, you have opened two stores in Canada. What is your next step? Who will answer? Go ahead. We have we are now following an agile approach. You being the agile masters, you have told me to open two stores. I've opened two stores. Now tell me what should be the next step. Go ahead. So we will survey uh what's the revenue uh what's the you know by having survey we will take the feedback from consumers. Excellent. What exactly have feedback? Good. Yeah. And what else? Uh Syrian, I have a question at this point. Priyanka, go ahead. Yeah. The question is at what location are you opening the store and what's the criteria for it? Good. So you mean to say let's say Priyanka they did some market research and they realized that these two locations would be good enough to try. So the background will not touch. Okay. We believe that the background that they did in choosing those two locations was good. Now we'll focus on the situation. That's a good question. How did you first decide on the two locations? Okay. So we consider as a what do you say uh something that is sure short for we know what we know that it is the best location. Now what next? So Shikha has told revenue monitor feedback monitoring from users. What else need to understand the need of the customer. Okay great. What else? What else? How do we do that better? When should we open a news show? Okay, we have taken feedback. We are now monitoring revenue. What else can we do to stop committing regular supply of goods? Okay, so if something is in more demand, just ensure that it's always stocked and piled. Okay. What else? Uh no, sometimes they'll check out other stores in that area to see what's offered. Check the competition. Good. That's you know, you need to check the competition first. Great. Learners, here's a small question for you because it is adding on to the target. What we're going to learn, we're learning over here Walmart failed in India. Why? Walmart Indians love to and who would not love to buy goods at the best price, right? Obviously, who wouldn't want to do that? My question is Walmart failed in India. Why go ahead? anyone any guesses any reason why why why could what could be I'm not sure maybe um like India um is a huge market with local retailers so sometime people feel like we will support our local economy why are the US retail come but but Shika but Shika same people happily adop adopted blinket instrumentat zeppto when these things came in the picture so they were readily happy to forgo their favorite local shops when these Yeah. Yeah. I mean but again blanket instam all they are Indian brands correct. Okay. Okay. Okay. Okay. So you mean that's what I'm trying to say. Got it. So there sometime this mindset also comes into picture people want to support especially in the co time lot of people have this business mindset and people were supporting to their being a local you know even from village. So that's got it got it now. Now similar similar reason for target anyone physical store what physical store political okay what else what else they able to find cheaper rate some place Rahul nobody can beat Walmart in pricing nobody you know you can't imagine I I've never seen it personally but the way I've heard about it read about it you can't beat Walmart in pricing so it's not possible for them learners is same thing Target did wrong in Canada, Walmart did wrong in India. Do you all agree that Walmart store is a huge store? Yes or no? It's like a city on its own. Correct? Now, now when you have a city of your own, that means this big chunk of land cannot be in a city. Obviously you will not get this huge piece of land in a city. So definitely it will be some place outside the city. Yes or no? Yes or no learners? Do you agree? Yes or no? Now now in US almost every family has a car. It's common understood common understanding that people own a car in US. However, in India that time cars were not as common as they are today. Maybe even in India today we are mainly the world's largest two-heer market. So now if I have to buy something you mean to say I need to drive all the way outside city in broken roads just to buy something doesn't make sense. That's the reason the model didn't work out because US has excellent infra road infrastructure in India now it's getting really good it's getting really better but when Walmart came it didn't in India not everyone has a car to drive and go there and get it done in US everyone has so because of these conditions Walmart also couldn't take off in India however another company learned from this mistake can anyone guess which company in India works on the Walmart answer Demart. So they learned they took feedback from Walmart and they opened Demart offering cheapest prices. And what Demart did? They said that in order to offer cheapest prices. How do we do that? Buying power and all is one thing. They brought a strategy that we will buy, we'll make a heavy investment, but we will buy all stores. We will not lease them. So we don't have a recurring expense called lease. We buy it. An asset is built for us so that we don't pay rent anymore. So that's how it worked. Learned from one company to another. And that's how the inventory kept on increasing and increasing. If you're clear with these examples and the way we are going learners, just quickly type your name in the chat box because we'll have 22 minutes more and then we'll take a small break. What we're going to learn now learners is a very uh what do you say common interlin uh structure okay you don't need to learn it by heart you don't need to what do you say take notes all you need to know is that there are different ways we all can work together in an agile team okay now let's say you know today we all are sitting uh pra gives me a suggestion praine says hey uh you know I have an idea why Why don't we discuss whatever discussions we are doing? Why don't we put it all our discussions on let's say our own website? I say to Pravin, how do we do that? Pravin says, I'll quickly make a WordPress website. You give me the videos, I'll I don't need to buy storage space. We'll paste we'll, you know, upload the videos on YouTube. We'll paste the link on our website. How much time do you think learners will this take? for Pravin to create a very small dummy website, pasting link on that website, uploading video on YouTube. How much time do you think Pravin will take to get it done? Well, depending on your skill set, it may not take long at all. Especially if you're using AI, it takes minutes now minutes, right? So, let's say Pravin says, Sri, WordPress is like drag and drop. It's like a PPT. I will simply enter some text. Let's say our sessions. Then I will put simply links. I can get it done in less than 20 25 minutes. And the moment I get feedbacks then I'll keep on adding. Okay. Now, now how much time will a company like Accenture take to deliver this same product if they were to put a platform of all of their uh trainings, the POVs on their website? How much time do you think a big company like TCS or Accenture take? Any guesses? It will huge loss for company. Huh? It will huge loss for the company if they do like this as in it's going to be a huge cost and effort for company. Right Pravin? Yes. And it's going to take a maybe a quarter to get it done. Right Pravin? Correct. Now do you see learners Do you see learners how priorities are different for a 0ero to1 company and for a wellestablished brand like Accenture? Do you agree with this learners? Yes or no? Tell me. Makes sense, right? Similarly, the amount of regulations that financial institutions like banks have to undergo when they launch a new financial product. Again, it's a time-consuming process. Correct? Because it requires a lot of safety checks. Cool. And the same way for a company that already has a good product running in the market now they have been asked to trim down some of their products and focus only on what is necessary. They will also have a different approach. So do you agree that in all of these scenarios the approach that we will be taking in tackling a problem is completely different. Obviously time and effort is also different. That's the reason the approach cannot be same. If you agree with this, quickly type yes in the chat box that yes, it's common sense. Uh the approach itself is completely different. However, however, Surange, we would still like to follow principle of principles of agile. Does that mean you are taking us back to waterfall? No. In agile learners again there are different approaches that we take towards a delivery or a development process and that's what we're going to see now. Can you see this thing called scrum kban lean xp scaled agile framework crystal lean. Do you see yes or no? Do you see this? Yes or no? Okay. Just keep a note of these things and I'll explain you in very very simple layman terms. Okay? And then we can go ahead and start discussing on each and everything. Learners, let's say today we've got Tanushri who is more focused. She's let's say running her own startup and that startup pertains to similar products like Amazon. All right. Tanushri since it's a newly launched products. So Tanoshi says Suryange I don't have time to brainstorm for one week on a feature. I would prefer deploying it immediately getting the feedback and then deploying it again. Do you all agree learners that's how it has to work out? Yes or no? Therefore learners when we are discussing our focus is on rapid delivery that just get that feature running at all cost. I don't care what's the feedback. We got to improve on that. But just get the deployment done now. Even if it's not wellm made, it's halfcooked, get it done because I want to see deployments. I want to see features. This is in this scenario learners, we usually follow scrum approach because scrum focuses on rapid delivery. this feature in one week, next feature, next week, take feedback, launch another feature, next week, take feedback, another feature, another feature. This is what we follow in scrum in very simple layman terms. If you're clear with this learners, quickly type a yes in the chat box that yes, Ranch, it's very straightforward when the focus is on delivery. Okay. Now consider a scenario wherein our friend uh Tanushi and Rahul are you able to follow now with some of the examples that we are touching and the discussions related topics that we are doing are you now able to relate them better Tanushi Rahul because Rahul perfect now learners consider a scenario wherein we have Rahul Rahul you are running currently a production house and you are a media company. Okay now learners listen to this carefully. They let's say are in the business of advertisements. They are in the business of social media reels. They are in the business of let's say YouTube ads. It could be anything for them. Let's say if they have a client called Dropbox or they have a client called Ola or Uber, they need to ensure that continuous delivery of whatever production they are making continues to take place. Do you agree with this learners? Yes or no? that every now and then the flow should be maintained so that there is no break in any production advertisements customer touch points at any point of time there should be one or the other production taking place always some production can take one week some production can take two weeks I'm happy with that but the visibility should be such that it appears to be as a continuous flow. In this kind of scenario, learners, we use something known as a kban approach. Okay? Wherein our focus is mainly on flowing that it should not stop at any point of time. Are you if you're clear with Kanan learners just quickly type K in the chat box that yes, we're good with KBAN. Just type K in the chat box. Okay. Now learners, there could also be a possibility wherein a company like Accenture has let's say five lakh resources which means roughly 500,000 resources work. Now all of you would agree that there would be thousands and thousands of teams. Yes or no? And you would also agree that let's say Accenture has a client called Ani. Okay. Anit. And for Anik Accenture let's say considers Ani what you call a diamond client. That means a huge value client. Now now if it's a huge value then Ani would have multiple teams from Accenture working for him correct when as an organization you have to manage multiple teams cross functional teams using agile principles you use what is called over here scaled agile frame framework. Now, if you're clear with concepts, okay, when do I use what? Big organizations use what? Just quickly type why in the chat box, then we'll go and see what are we looking at. Just quickly type why. Kanban. Okay. Who said Kan? Kanban Rahul. Wherein you're focused more on seeing that the flow of delivery does not break. That means if you have a task of having production of advertisements or YouTube shorts or Instagram reels as your project then at all times there are some deliverables taking place. Maybe after 1 week, maybe after 2 weeks, maybe after 3 weeks something is always flowing. At no point of time there is any lag in one flow from the other. That's what Kanban in brief means. Now, now instead of wasting time on these theoretical aspects, please take 10 seconds to read what's there on a screen because in this way you'll get some idea about the key elements. You don't need to memorize them. You just need to know that these words exist. That's it. I'll give you 10 seconds for this and then we'll continue. Pravin yes you could consider it more of for a social media management company for a production house that's when convits well however however if you have let's say you are in a you're working with a client who has fixed deliverables you don't need to brainstorm on much of deliverables or it's more of like a not a new product or a system integration it's a maintenance work for a software that's when again you can use KBA bar because it shows that continuous flow of tickets is taking place and those are being resolved in the right time. Is that clear Pravin? Uh I have a question. Go ahead Shika. Just give me one moment Shika. By the time others read KBA you can ask now. Go ahead Shika. Yeah so when you say I'm just trying to understand the base here. So scrum is like umbrella and canban agile safe all these are falling under this umbrella. No, no. Agile is the umbrella over here. Agile is the umbrella over here. Shika and all of these frameworks fall under agile because if you see what I told in KBAN that there shouldn't be any breakage. It should come out as a flow. That's what agile exactly means. Continuous delivery and continuous improvement. Scrum also does the same thing. However, the only difference lies in the visibility wherein the scrum part focuses more on the sprints that lead to deliverables. KMAN focuses only on the flow that during this time a flow came of getting this production done or a ticket resolved done. Yes. The next time same thing happened done. Yes. The next time same thing happened done. Yes. So there is an overlap but the umbrella is agile and all of these frameworks fall under agile. Mhm. Okay. Then why people say like usually every company they say we are in scrum call but irrespective of whatever approach they are following because scrum is the scrum is the most commonly followed or used methodology. The reason being is whenever we work in agile teams Shikha okay learners many a times I'll give you answers that are pertaining or relating to your industry so if you don't understand the answer I'm giving to Shikha because it is a little technical and you know someone from the industry might understand but if you would like to know more you can immediately say that can you elaborate more on this all right so shikha whenever we work in an agile team there is usually a stand-up call right Shika and whenever we talk of working in a scrum environment, it is considered to be launching some kind of a feature. And when you talk of launching some kind of a feature, you definitely bring in the word sprint, right? The moment you bring these two jarens, scrum automatically fits in. That's the reason for any new product development, any new product development you do, you will run sprints. And that's the reason scrum is most commonly used. That's the reason you keep on hearing the word called scrum call. I'm working in two teams. One follow agile, other one follow can. So I get it. Get it. Less Shika has got a good question that one is saying agile and one is saying Gman. However, you are giving all frameworks under agile. So learners, let me make one thing very clear. There is no standard agile that you will follow in any organization. If you are in TCS, if you are in Accenture, Accenture has something called Accenture Agile. So they have tweaked the model based on their requirements. Therefore, learners, whatever we are discussing, these are guidelines or principles that are followed with tweaking done based on client requirements or project requirements. So therefore, you just need to be aware about the principles and the governing sites, the technicalities. For example, Shika mentioned Kanban was not called agile. So these things can vary. So Shika, you're right in that sense that they use this word. Make sense, Shika? Yeah. So but I have a question. In my previous we had water force structure but still we had stand up but we don't like sprints like it was not following the agile but we had standup and we call scrum call. So like scrum word is very common. It is used everywhere irrespective of your structure. Even in waterfall we can't say like waterfall is completely positive right it's opposite right yeah but still we say we have scrum call so I I'm just trying to understand the scrum word is so common that we used everywhere and when you use jira when you use jira scrum is also called a board yeah yeah yes you're right the word jira board that's right okay learners can anyone tell me what exactly do you see over here it's called extreme programming it says software quality and responsiveness the changing customer to engineering excellence. Okay, what exactly does this mean? Can anyone elaborate based on whatever you're seeing on the screen? I'll give you maybe 20 30 seconds to read and then you can go ahead and tell that Suryan this is what I believe this means. Go ahead. Anyone can answer on this now. What is extreme programming? Yeah, I can over to you. So actually it is called uh extreme programming also we used to call it a behaviordri development that is BDD you already have the uh requirements ready and we were mostly writing the test cases even before like side by side with the development. Mhm. So they were working in parallel like okay the uh development and the testing because the uh requirements are clear the test and the test engineering and the development engineering were done simultaneously and when we talk in terms of uh the CI/CD pipeline the first version of the product with vent also went ahead with the uh tests that were written to it. So this is how we saw that the extreme programming. Great. Great learners. Let's uh exactly what Pranka you know mentioned over here. Consider this scenario that once you're developing something it's like writing an exam with a teacher on top of you. So whenever you're doing something you get it checked with the teacher. If you check this are you going to give me full marks? Yes or no? So teacher will look at and say no no no change the answer in this way so that I can give you full marks. Then you change the answer. Give it is this fine now? Yes. Yes. Now it's fine. You get full marks. Go to the next one. That's how it works. You put the tester, the developer. That means if I am tasked with developing a new feature, I'll have a someone who is there to ensure that feature does not work. So whenever I make something, he or she will sit next to me and find out ways to show that this will not work so that I can get it corrected then and there. In simple words, the testing team and the development team work hand in hand from starting. That's in very simple terms for extreme programming. Have a look at lean. Now while you're reading lean, I'll tell you one very simple thing. When you don't have budget, just keep it very simple. When you don't have budget, you don't have money for impressive launches, for all the jambburis that you can think of, you focus on bare minimum what has to be done. If you are Zomato, you focus on selling online. Forget about membership, forget about wallet, forget about financing or you know uh different payment options, forget about uh AI, forget about customers requirements getting sold. You only focus on what is needed. That's in layman terms what lean means that you are on budget constraints you don't want any jambburis you just want it to be delivered that is where lean comes in the picture can I say that because this is again this will require lots of discussion so please participate this is a development team the client. Okay. this is a business analyst. You are the bridge connecting these two. Do you agree that this diagram rightly justifies somewhat rightly justifies the role of a BA? Do you agree with this? Just type yes in the chat box if you are clear. Thank you Sumea. Do you agree that Surange? Yes. Somewhat you are heading in the right direction. That's in layman terms were BAS. Okay. Now, now listen to this carefully. You see the reason why BA stands somewhere at this junction is can we say this again? Because this person understands the business side of the client. Maybe if the client is from again let's say oil and gas. So maybe the BA has got some background in oil and gas. Therefore he understands what oil and gas what happens in oil and gas industry. What are their priorities? What are the problems that they the softwarees that they use can incur and at the same time the same person can also talk to developers in their own jargon. So he is aware of both the jarens. That's the reason he's in the right position to bridge the gap. Do you agree with this learners? If yes, just type why in the chat box that yes Suryanch because he's someone who has got both of these points cleared, both of the industry sectors cleared. Learners, there is another category. This category is mainly of a product owner. It could be a owner, it could be a product manager. It all varies. Okay. Now listen to this carefully. Since our friend BA knows industry. Our friend BA knows the industry. Therefore he knows the priorities and inside details about the industry. Maybe he knows the safety regulations. Maybe he knows the culture of the organization. Maybe it knows what is valued the most in these kind of organizations. Maybe he also knows how the person who is acting as from the client side will get his or her money. Therefore, he knows this area very well. However, our friend over here, product owner or manager, he is someone who says, "Hey, you know what? You just tell me what do you want. I am a features guy. You tell me what feature you want. I will get it done. Period. That's it. Therefore, learners in many organizations this role and BA role in many projects is played by a common person. If there are two people playing this, let's say one is the PO, one is the business analyst, then the BA understands the industry requirements and tells the product manager that this is what they want. So the product manager says that this translate into these kind of features. Now BA based on his domain knowledge explains the product manager that you know these are the features perfectly well defined. I would request you to focus on these top two three features first and get them delivered by this time because this period is usually considered busy for this industry. So the product owner says cool I will get this delivered working with the developers just in case I need your help I'll come I'll bring you as well in the picture. Once this is done then the B then you know a business analyst goes back to the client and shows that with our tech team we have managed to get this thing done that's how a usual development process works learners if you're ex if you're clear with the process that okay Surange I get it type why in the chat box if you're clear with this process that why do we need a BA along with the product owner if there is a role both product and uh product and b this is where learners I want you now to take 10 seconds to read what is written over here then we go to the next all right so I'll give you 10 seconds read what is being shown then we continue may I have another question at this point go ahead priyanka by the time others are reading you go ahead so when You talked about uh BA adding value to the product owner. I was under the impression that uh product owners usually select the features uh based on the competitor analysis of what's happening and then they prioritize when that is the case and and also based on the feedback they come up with the different features. So how can we add value there as business analysts? Now, now you mean to say prana that in any product development work okay a product owner or a manager sees what's happening in the world manages to prioritize things and then gets the developers work done. Yes or no Priyanka? Yes. Now everyone do you agree with the fact that there is kind of an overlap with the role that a BA does? Do you agree? Yes or no? Everyone just type yes or no in the chat box. Do you agree that we see an overlap? So learners that's the reason in very few teams you will have a product owner and you will have a BA very rare chance that both of these would be present because BA does the role of understanding industry and conveying it to product owners who convey it to the tech lead and then con it is being conveyed to developers. Therefore, this step of communication gets skipped and BA can directly communicate to the tech team what has to be done. Therefore, overlap is there. Very rare you will find a product owner working with a business analyst. Even if you have a business analyst on board, let's say you have a business analyst on board along with a product owner, then business analyst will not get involved with the development work. His side would only be to understand the business. Talk to the client in his or her own terms. And gain clients confidence that okay, you know this is someone Priyanka is someone who is from pharma industry. So she understands what I'm saying. She's well aware about let's say FD approvals. She's well aware about all the jarens that I'm discussing. Great. The BA develops the confidence. Now based on this BA communicates to the product owner that these are the features and we're discussing with the client these are the priorities please get it done. Now the product owner starts getting work done with the developers. So both of these scenarios work uh Pravin it only gets uh does not involve in development side. It only happens when you have a product owner or a product manager. Majority of the time the product owner or manager will not be there if you are sitting as a BA. Now you are clear uh Pravin that if you are a BA and the team does not have a product owner or a manager which it will not have because it doesn't need therefore you would be the one who would be working with the developers. That's the reason in both the roles BA and what do you say uh product owners many a times these are no one but developers who switch to these roles B side it is usually a developer or someone from the industry knowledge who manages to get in this role. So all of these options are possible but the way of keeping it simple straightforward is the BA works with both developers and the client but if another layer of product owner is added then BA gains clients confidence takes care of all the client dealings and communication with the product owner does that somewhat answer your question by the time others go and read to the next one yes or no yes okay now learners Shalesh I'll come to that note in a moment but how many of you learners present over here have used this tool called Jira anyone so if you have used the word Jira go ahead tell me just type yes no in the chat box that yes Surange I've used Jira no I've not used Jira so go ahead Okay. So learners what I'll do now is I'll just explain you what exactly uh Jira kind of a thing is so that you understand once you start using it in your career. We'll not give a demo of Jira and all because that's going to be a lot of time consuming. So consider a scenario today that let's say over here a friend all learners who are well aware just uh you know bear with me for a moment let's say today we have Pravin who is client we have got Priyanka who is let's say the business analyst we have got who is the developer we have got you know Anik again who is also a developer and we have got over here Deepipika who is as a working as a software tester Cool. Don't you think you need a place where you can manage all of these people? Whatever work they have been given, whatever task they have been assigned, whatever updates they've got, whatever you know status they about the work that they working with. Don't you think it would be great to have all of this available at just one place? Do you agree with this? Yes or no? Thanks Sumeda. Do you agree with this? Yes or no? That yes, it's I think it's common sense. Who is going to keep on updating those Google Sheets or Microsoft Teams, Excel uh all the time just to ensure that where all we are working? In fact, client would never have so much time to look around Excel sheets and know the status. This is where learners Jira comes in the picture. Jira says all team members everyone you want to know anything come to Jira. I will show you what features are currently being made. What features have been made? What features are yet to be started? What features have to be made? What products are in testing? I can let you know if let's say we've got over here Pravin working as a developer. What products what features he's currently working on? What features he has not even started? If let's say Sumeda is a tester, what products has she done her testing completion? What products she's currently working on? So all of this view is given using Jira. If you're clear with this very simple story, just type see so don't worry if you have not used Jira there are multiple products available in the market the way the reason why Jira is being used or being spoken more of simple reason because I I'll explain that pra simple reason it's got excellent UI UX. It's a good tool for collaboration across teams. Most importantly, you could say that since it was it's already made by a company called Atlassian which already has other products. So yes, the adoption is high. So Pravin in layman terms just remember that Jira is a software that can be used to run software development product development projects wherein you can track each and every team member working on what all features and those features are currently at what all stages. So you don't need to write a mail to check where are you working, what are you working at, what was the update. You don't need any rag status update, nothing. All updates take place at Jira wherein you can work and a client can also view if needed what is the status of the product that he has asked to deliver. Does that make sense Pravin? A very simple clear meaning. Yes or no? All earners. Does that make sense? Yes or no? Is this similar to Azure DevOps though when we have the vision boards and you go in and do the updates or you assign the different It's similar. Yes. Yes. See the same thing can be done using email. Same thing can be done using Excel, Slack. Whatever product you say, right? It's just it's another tool to manage. I'll if time permits towards the end I'll also show you exactly how a Jira board looks like. Okay. Now, now, now learners, let's say today we have Pravin over here. Pravin says, "Uh, Surri, why don't we do this? Why don't we launch since we all work at let's say Uber, why don't we launch a feature called a prime membership of Uber which guarantees you a cap. No matter what time, what place you are at, if Uber is there at that location, no matter what happens, even it means heavy rains, you will still be guaranteed a cab ride. No matter what. So, Pravin has given this idea that let's work on this. Everyone, are you clear with the idea? Yes or no? Yes or no? Clown is quickly clear with the idea now. Now learners this is the idea that means just understand the story. Okay. That means this is Surange the final objective that we are trying to achieve. Correct. That we need to have a prime membership that offers these benefits. If I talk in terms of Jira, the final objective is called epic whatever you want to achieve while you are making a software right you have a final objective you name it as epic in Jira that this is the reason why I'm on Jira this is the reason Tanushri is a tester Pravin is a developer Suryange is a developer and Adrin is a client we all are here to achieve this final objective called epic Everyone clear what exactly an epic is? It is a final objective that you're trying to achieve. It could be adding payment online payment methods. It could be adding cash on delivery to an e-commerce platform. It could be anything. Are you clear? If you're clear with Epic, type E in the chat box everyone. Okay. Now learners, obviously to complete this objective, you would like to make some features. Yes or no? First feature because to get this thing live you first need to have a option on the app which says buy prime membership. Another option which says benefits of prime membership right another development that takes payments for the membership right and another one you know for renewal or cancellation of the membership. Do you think that whenever you launch a new membership program you need to at minimums of the minimum you need to get these things done that give a button so that users can click on it users need to know more about it users can pay for it and if they want to cancel they want to refer or maybe they want to renew this is how they can do it therefore learners again now what I'm going to say is going to vary a lot from organization to organization therefore we'll not discuss more on what is it fault. But many companies call these as features. Many companies call this as stories. So the final objective is called epic. And in order to achieve an epic, what is it that you need to do? I need to give you a button to buy. I need to give you a payment option. I need to give you the features. And then I need to give you an option to renew. So these are called stories. So that's the hierarchy. On top you have epic and then you have got stories. We'll not dig in much more details on this because it's a huge topic on its own. What comes after stories? You know why only stories or it's a huge topic. So just let me know if you're clear with the story that I told you about epic and stories and the example that I gave. If you're clear, just quickly type your name in the chat box so that I can continue with the next part. I know already who are from tech background you will have a different opinion the surin we call it we don't call it stories we call it features we don't call it features we call it something else sometimes someone will say task subtask so we'll not get in those details because it is not a session on jira okay now learners um darushi and raul now Are you able to follow as in the examples and all they are coming as per your what do you say uh industry relevancy and you're able to understand yes or no. Okay, great. Great. Now learners, let's let's see this. Let's see this. Everyone, keep your typing ready. All right, you need to type it in the chat box. All right, keep your chat box ready. You need to type it out. Do you see user story one? It says as a shopper, I want to pay using UPI cards or wallet so that I can choose my preferred payment method. User story 2. It says, "I want to save my card securely so I don't need to re-enter details. I want to clear error message if payment fails so I know what has to be fixed." Okay. Now, now, now this is a very simple example on how an online transaction takes place. Do you agree? Yes or no? I can choose UPI, I can choose cards, I can choose wallets. And after that, I need to save it. And after that if the payment fails tell me it has failed. Okay. What I want you to do is what I want you to do is write down similar user stories on the chat box. User story 1 2 3 of entering a delivery address. For example, as a user, I my current location should automatically be accessed by the platform. User story 2, I should be able to manually enter if it is a new address. User story 3, I should be able to select which address I want the delivery to take place. Okay. So now write down three user stories, four user stories on updating or adding delivery details for the user. One example I gave you, you can take that example as it is or maybe you can add something more to that. Don't worry if it's right, wrong, whatever it is. Just learners, I'm so sorry. Okay, just give me one moment. The session is till 10:30 or till 10. Learners, can I get an answer to that please? 10:30. 10:30. Right. Please don't fill the feedback form now. I'll tell you why. Because uh because usually I get my feedback forms filled towards the last 15 minutes. Uh what do you want? You want you want to fill the feedback form right away or what do you want to do? Tell me you since it has already been shared and many of us may skip. Please take 10 seconds and get the feedback form done. I'll wait. Hurry up. Quickly fill the feedback form. Take 10 seconds. Uh chalesh if you just fill it now because now it is being shared. So it's good that uh it gets along with the flow now because after that maybe many learners leave towards the last or the link will get we we forget to share it again. Okay, so learners take 10 seconds quickly fill that form. Come back, type in your user stories. You don't need to worry whether it's right, wrong, doesn't matter. You're only here to learn. So hurry up. Just get it done. Just write down user stories, but fill the feedback form first, please. Quick. It won't take more than 5 seconds, 10 seconds for you to do that. Hurry up learners if you have done the feedback form please let me know so that I know that if most of you have filled I'll now straight away go to the user stories part all right hurry up learners get the feedback forms quick okay thank you pravin learners send me your user stories now quick hurry up let's see what we have But I would like to see all your user stories. Go ahead, show me your user stories. 1 2 and three. I'll give you maybe a minute more, but not more than that. Hurry up, learners. Show me your user stories. Quick, Tanushi. Perfectly fine. Perfectly fine, Sumera. Makes sense. Works well. Good. Next learner. Let's see what all Okay, good, Priyanka. Let's see. Able to enter multiple delivery locations. Perfect. Uh-huh. Able to label my Excellent. You home office. Okay. I wish to have an option to choose delivery. Excellent. Priyanka. So, we've got as a user I want to fetch my current location by turning on. I want the app to remember my location. Good. Refresh my current location. Perfectly fine. We'll take 10 more seconds. If anyone else would like to share, please do that right away. Good. Good. Good learners. Now, now, now, now let's come over here. Let's come over here and have a look at this. I want to update my address manually. Great. Now, now no, no. We'll not spend time much on this. But, but do you all agree that whatever stories you've given, they all are small enough? I don't I mean they are not big paragraphs. Do you agree? Yes or no? You also agree that they are valuable to the customer. They can be tested very well. And moreover, they're independent. That's it. They're independent of any other feature. Selecting location, choosing my location, labeling my address. Therefore, these are certain things that keep usually are kept in mind while designing stories. It's a principle called it's called the invest test. Okay. Now, now, now, now here we go. Here we go with Mhm. What is this learners? Can anyone please read take 10 seconds and then we'll start. It says agile estimation. Okay. Focuses not on exact hours but on effort, complexity, risk, uncertaintity. The goal is to help team decide this. Now, now, now as we go, as we go, as we go, I have a small question for you. Let's say let's say how do you decide how much effort or cost is a feature going to take or or let's make it very simple. How do you decide value of a feature that you're going to launch? Let's see who can answer this question. My question is very simple. How do you decide value of a feature that you're going to launch? Can anyone answer? All features are important. Some features are more important. Some are less important. So, how do you decide the value of a feature? Correct. Can anyone answer this question? Well, dealing with it in the past has been like historical fact. So, if we've had something similar to that um to that feature and everything it embodies, then we'll usually go with the numbers that were used previously. So, if we're launching um a feature that says um install a go button and we used a go button for another similar spring. Good, good, good. So, excellent. So let's say you use your so use the historical data whatever is available to get that's perfectly fine depending on customers needs t-shirt sizing great all answers learners remember one thing depend on what Sumeda has just written at the last depending on the customer need remember this if a feature takes more effort consider this okay if a feature takes more effort okay but client says it needs to it needs to be done right away and and that requires additional efforts to be put in. That means additional resources to be brought in then that feature carries more value. Therefore, no matter what the effort or resources are required, you need to get it done. Therefore, estimation, how much time, you know, how much effort should be done, is it big or small, there are no straightaway answers for this. It all depends on your interactions with client. Okay. Now learners, it says it says that uh you know we're looking at four factors and we are looking at story points. Let's understand what exactly what we're reading over here. I'll give you 10 seconds. Go ahead and read whatever text you can see on the screen. Someone mentioned already that Priyanka I think you mentioned right giving a story point. Yes or no pranka? Yes. Yes. So that's what we are looking at. See learners it is in simple words assigning weightage that if launching or let's say if developing this feature or let's say working on this story would require keeping effort complexity risk unknown in mind this much level of weightage. So we assign that. So let's say at last if you look display user profile at two points that means very mild risk in that complexity in that. Okay. However, if you look at the last one, learners story C profile update, you need to edit profile also, but you are adding multi- language support. Now, that requires a lot of effort. It is complex, but maybe the risk is less, but still it carries eight points. Therefore, you give certain story points to every story. And once you have got a total that okay this story carries this much point this story carries this much point then based on the time you have got you decide which one to start. Can anyone guess how do you determine how much points should be given to a story. Now here's a question for you all. Surange you have told us that to give story points and then once we have story points then depending on time and all available with us we can choose which one to work on first. Perfectly fine. But you didn't tell us how do we assign the story points? Who decides whether it's a twopoint story, five point story, eight point story? Who decides that? Can anyone answer this? Shikha, please. Uh in my process, it's product owner. Uh usually say and they ask for the you know input from the developers like two two story point is enough. So it's not only one way, it's always mutual. I would say it's always mutual. Right. Good. But I have like I have a question. How even the developers or the product owner how do you derive the two points, four points, five point because this is always approximate or average right? No no no no learners. Shaka is saying that usually the product owner would do that working with the developers or with the tech lead working with the tech lead. Right now she is curious to know how even the developers come to this point. Right Shika? Yeah, I mean I always have a curiosity to know how do we derive the story points. So let's let's let's do this and let me give you uh let's say let me give you uh what do you call uh some uh the answer from some of my experience right when I was taking care of a product called discover I what we would do was my job would be to elaborate as much as possible. When I say as much as possible, I mean to say I would take 10 minutes to understand from the client or from the leadership. This is what we are trying to make only 10 minutes so that just to get an overview what they want because they don't have time. they'll just going to get a call okay do this do this you know uh why don't you integrate a chatbot covering all industries so that I can ask questions and I straight away I can get answers okay this is what you have to do tuck tuck tuck tuck I would just keep a note of it then it would easily take me 30 to 40 minutes to elaborate them on my own and then a call would take place involving me and my tech lead sometimes tech lead would also have their own backups right So they would involve their backup also the top performing developers. Now this call would be easily for one to two hours where I would explain the entire story that I discussed with client. Now what tech lead would do is he would suggest now you tell how much time you've got. I'll say okay we need to start showing deliverables in 1 week's time. Now everyone what they would do is they would figure out that certain developments certain features that do not require a logic change that do not require a UX change that do not require any kind of changes in the current structure. When I say structure I mean to say no changes in the database. Let's target them first so that they can be shipped easily. Certain changes that require UX, database changes, please leave them for a longer side. They can't be done so easily because they would require a lot of discussions to be done. Now the backup person who is an experienced developer would give the new upcoming developers what do you call these simple task you get it done. I'm not getting involved in this. He would start working on the logical questions or or on the logics. Let's say if a new feature is being built to calculate certain values. So he would start working on the logic part. The tech lead will not get involved here. The tech lead would start focusing on the UX and the database changes keeping the backup involved. They come out with these points based on experience and the changes that are needed in the current structure. Shika somewhat learners if you're okay with this story that okay Surange now we get it that's how it works. Quickly type yes in the chat box. Shika does that somewhat answer your question because there's no I'm I want to ask one more question. So is it always tech lead or developers because I I'm assuming they are the person who can actually judge the work like how much time it take right non-technical person can't tell or specify so the you're right when it comes to assigning points because assigning points comes from the effort required so they are the ones who make the decision however however they have made their decision in terms of efforts time resources you on on the other hand know that these 1 one point 22 points features carry no value to the client he or she is going to simply scrap them off and say I don't need them then comes your picture saying that you're saying it is a 10 points thing and you're saying two weeks time show me one deliverable after one week so then you begin with some kind of negotiation with them so that's how usually the discussion happens And is it correct? I'm sorry. Um I'm just trying to be more upfront. Sometimes you are non-technical. The other person is technical but you don't know how truth is that like let's say someone says oh this is very big task and actually it is not and they want to take you know buy more time just to have see usually in usually in bigger organizations or let's say if you work for the same firm it doesn't happen. However, if you're dealing with a vendor, then yes, you need if you're not a technically sound person, you need to deploy someone who is a technically sound person. That case, your question comes valid. No, uh I have seen people who are both business and technically sound. So they counter question how your developer is saying this much time will be you know they need that. So that is the thing I have encountered in my working areas. So in this kind of a scenario the situation. Yeah. So in this kind of a scenario what you do is you get certain answers from the tech lead so that you know the client is also technically sound. Okay. Now what you do is you get certain answers on detail basis. This is what it's going to take and if you have a doubt that discussion is going a different direction you bring the tech lead along with the call. you don't come in and give in the tech answers because you're not from that field. Okay. Now learners, that's how we've been using Jira. And uh what I'll do now is what I'll do now is Mhm. I'll show you Jira for a moment. But before that, I'm just seeing if there is there any other concept that we supposed to discuss in Jira before I take you to the tool itself. Okay. Now, okay. Here we go with the Jira part. Now I'll stop sharing from my pad and I'll take you to the tool now on my laptop. Is my screen visible learners? Just sorry. Just give me a moment. I just stopped sharing. Uh where is it? Yes. Just let me know when you see my screen. Screen's visible. Yes or no? No. Screen's visible. So, just I just Googled Jira and I'll take you to the software. Let's say Uh-huh. since I'm already using it. So, I'll just simply sign it. Sign in Google. Okay, it says welcome back. Go to Jira. Okay learners, I'll show you from scratch how a new project looks like in Jira. All right. So what do we do is we go to let's say where do we have an option of no this is something else where do I have an option of let's say if I go to cheetah over here and do I have an option of creating a new project supposed to be here for you apps plans spaces uh recent it's already showing me my recent ones uh Just give me one moment. Where are they? Where is it? Then Lis, do you see a place which says new project? Anywhere on my screen? Do you see a place which says new project anywhere you see? No. Right. So let's it's fine. Let's create a fresh one. All right. We go for software development. Over here you will see learners Kanban and scrum. So select scrum. You we'll use this template. You can select anything team manage or it doesn't matter over here. Team managed. Just name let's say we'll name this team. Mhm. Beta zeta 4. All right we have chosen scrum. Next learners. Now you need to tell me one thing that if you look at a product let's say like Uber okay I'll click on skip I don't need to add any team members if I look at a product called Uber do you agree when the product Uber was let's say being conceptualized there were at least 100 features that could have come in you know the founders's mind do you agree yes or no just quickly type yes no that yes Suryan even if I am supposed to do that I can also think of a 100 features in Uber correct Now, do you think all of those 100 features were launched at once? No. Right? Obviously, there was some kind of prioritization. Therefore, the word that you see over here is called backlog. Backlog says whatever you have in your mind, whatever process, whatever feature, whatever thoughts you have got in mind, please jot it down over here in the backlog section. Whatever you would like to do immediately, whatever you'd like to do it now, please do it over here. So let me show you how do you actually start something in Jira. What you do in the first place is you need to create an epic. All right. Let's say I'm creating an epic for the same Uber thing that we discussed over here. You click on create. No, not over here. It's not. Yes, create. You have an option called epic. But in order to do that, let's first enable the epic bar. Do we see that option called view of an epic bar? No. So we need to go it from here itself. uh create nodes. So click on create and click on epic. All right. Is epic or feature is same. Surely no no no epic and features are completely different. So that's the reason I didn't touch upon more on what is a story, what is a feature because that's going to take another set of discussion. Okay. So they're different. Remember one thing learners epic refers to only the final objective. That's the final objective you're going to type. So epic we're going to type over here is enable prime membership at Uber and then I click on create view epic. So let's say I get a chance to view epic over here. We've got this epic coming up ready. Now earlier there used to be an option over here to enable epic panel which I believe they have removed. There was an option over here which said uh enable epic panel wherein we can see the epic but right now I am not able to see that no they have changed the UI now let's start and let's start you see story I told you they are called stories so select story and we can just mention that have a button for booking Then another story can be create a page for benefits. So let's say if we talk of only these two stories. Now using this I can assign an epic to them that they both work for this and then I can start a sprint. I can set timeline 2 weeks, one week and I can click on start. The moment I click on start, the sprint gets started and you are taken. Just give me a moment. Hey, something changed. Just give me a moment. We move something else. Uh this one. Yes. And we came from backlog. We here at backlog. We came at a place called board. Now over here we can move whatever we have done. We can open any story. We can assign it to anyone who is added to our team. That's how simply how Jira tool works because it's a huge tool in training itself. That's the reason you know I'm not able to give you a demo otherwise I would have made you have some kind of hands-on but seeing the time and what we are learning over here a small intro is good enough for you to have a look. Okay, learners look at my the screen now. All right. Okay. This is what I showed you as a backlog. Learners always remember that backlog you, your development team and the client together decide from the list of 100 features that you have thought which features should be developed first. So this is how you clear your entire backlog. All right. No, no, no. Anyone aware of any of these things? Visual modeling toolkit for agile BAS. Anyone aware of, has anyone heard of it? Anyone you know knows about it? Anyone has thought of any idea what this exactly could mean? You can speak now. All right. So that I know if anyone is aware of this. Okay. So Anoo is saying no. Surri not being aware of this. Okay. We've got multiple no. No. Pranka says yes. Okay. She's heard of these things. Okay. No. Anyone else would like to give an answer on this. Okay. Now I'll take a pause for a moment because this is where we come to the last part because visual aids are the last part and they they'll take their own sweet time. Till now with lots and lots of discussions that we have had till now is there any learner who got any questions you can put in your questions right away so that before we go to the last section we have taken up almost all doubts in the end of course I'll ask you for questions but now if anyone has please ask right Okay. Anyone? Okay. So before we go ahead, you need to quickly type your name. If if you got some basic understanding of agile, your role as a BA in this entire thing. If you got some basic understanding of all of this just type your name in the chat box so that I know how many of us are up to speed and uh in this way we can now go towards the last part of the session. Uh Sur I have a doubt. Go Tushri. Yeah. In one of uh my interview I got a question of what is Jad session? I click type it in the chat box. Joint application development session. Jad session. Okay. I am not aware of this Tanushri. If anyone is aware you can help Tanushi right now or if you're not aware then Tanushi maybe we can connect it later at see how we can take that out. Anyone aware about this what Tanushi just mentioned? Tanushi can you type it in the chat box? Okay, just type it in the chat box. I'll see if I'm able to, you know, get some kind of an answer to it. Now learners, I just wanted you to check with one thing. When you use Amazon, keep that journey in mind when you look at my screen share now. All right, just keep Amazon in mind and uh then look at my journey. All right, here you go. Okay, Lis, do you see the first visual diagram that we're going to learn together, which is the use case diagram? Okay. Now, now, is my screen visible? I hope you can see. Yes or no? Cool. Yes or no learners? Okay learners let's have a look what exactly is a visual tool like you know if it's helping us in some way how is it helping us it's called the use case diagram by the way it itself is a subject if you are studying engineering it comes under the category of database though it's a huge subject on it on its own so let's see as a BA what do we make out of it cool I'll give you maybe 10 20 seconds to read what is being shown. Go ahead and read. I'll give you 10 20 seconds and I'll open discussions. Okay. Now learners, now learners, since you have read, can anyone elaborate what exactly is a use case diagram? And uh if it's helpful for us, yes. If it's not helpful for us, then how? Go ahead. Anyone can elaborate based on whatever you have read. relationship between user and system. Thanks Pranka. What else learners? Let's let's understand this so that you know we're able to dig down a little better. Okay. Let's say this is where we have our user. This is where is where we have our system and over here online shopping takes place. Okay. Now let's say we have the user who is currently browsing. Now the user would like to add to cart. Then user is would like to begin the checkout process. Would like to add delivery details. Would like to make the payment. And let's say then the user decides to check out. Okay. At every point of time the user is interacting with the system there are responsibilities being shared. For example, payment can be shared by the credit card company provider. Delivery can be shared by someone providing the location services. Adding to cart, adding to cart, browsing or logging in can be taken care by certain other users who check the credentials. The credential works well then only allow the user to login. The user does not interact with the credit card service providers location access identity. All of this happens outside the system for the user. The user interacts only with these. Are you clear with what I just told you? Now if you're clear, just quickly give me a heads up. Nurange, we are clear what you have just told us. Go ahead, tell me. Therefore learners if at any point of time certain breakage happens let's say a breakage happens at payments certain breakage happens at login you know location sensing now you know which particular portion area is at fault so you can correct it therefore using this called the use case diagram you understand how your user is interacting with your system the different points that you are currently covering with the system and if there is a breakage or fault you can pinpoint where the scope for improvement lies in this simple language we cover your use case diagram if you're clear with this just quickly give me a yes in the chat box by the time I go to the Next one. Learners, remember one thing. When you're discussing concepts like these, you need to be aware about the story or about the discussion that is happening. The theoretical details are not of your concern. You don't have to give a semester end exam for this. All right. Now, now let's look at another one which is called the data flow diagram. I'll give you 10 seconds to understand and then we can continue. is uh flowchart or data flow diagram is yes okay learners what I'm going to tell is mainly understood again because it's a technical term shika flowchart is usually created before you create the schema of a database right shika Yeah, basically if someone requirement is there, you just want to show how it looks like. So flowchart is a tech. Yeah. So that's a data flow diagram. Shikha, so when you mentioned flowchart in technical terms, Shikha, a flowchart is a diagram that you create before creating the schema of a database. Because through flowchart, you come to know what will exactly form tables, what will exactly form attributes, what exactly can be a primary key or a foreign key. That's what you develop from a flowchart. However, when you are discussing the flow of a user, how it will happen or maybe you are discussing what we're going to see now, the flow of data, what you hinting at, this comes under data flow diagram. Data flow diagram is more of from the managerial perspective of different types of integrations and fault analysis. The flowchart diagram is mainly from an engineers or a data DBA database administrator perspective because he has to create the database structure in the schema in the background. So that's a small difference. Shika although the terminologies may look similar no I have drawn only flowchart uh like data flow diagram basically I'm not from technical background technical background right okay now learners didn't I just tell you that there happens I'll just come to you in just one moment if it's fine sure hello who's this sure okay sure pranka now learners in the use case diagram We just realized how as a user we are interacting with the system and what all players are involved when we are obviously discussing about these tech products. Therefore we see a lot of data being flown over here credit card information, location information, over here login credentials. We see a lot of data being flowed. Whenever learners data keeps flowing within the ecosystem, it makes less of a worry because it's in our control. We know where the fault lines could lie. However, when we are integrating a payment gateway, in simple words, when we are allowing a user to pay using credit card, we are allowing user to enter their credit card details. That details are then sent to companies like Razer Pay, PayPal, PayU or Paytm or something or the other. Those require integrations with our website or our app. This is where data flow diagram comes in the picture and lets us know whenever the data is flowing outside our ecosystem. This could be important to know from the data privacy perspective. It could be important to know from the fault detection perspective where all we are having problems in integration. For example, we made a product perfectly fine but suddenly Google pay server has gone for a toss. Google pay is not working. Therefore you are able to identify the data flew to Google pay but it didn't come back. There was no response for payment confirmation. That means a fault lies over there. So using a data flow diagram you get to know any data of that user external flow internal flow where exactly it goes. Good. Now learners just quick question why do you think Blackberry failed? I mean it was supposed it was always a premium product especially BBM and uh it was more of a proud moment to own a BlackBerry. However, things went down and I believe we don't even see that product in the market today. My question for you is why do you think this happened? Okay. Uh adapt alama they did not went uh with the evolving needs of the users and uh overcoming the uh lacunas of the uh existing products.…

Transcript truncated. Watch the full video for the complete content.

Get daily recaps from
Simplilearn

AI-powered summaries delivered to your inbox. Save hours every week while staying fully informed.