I am a passionate Business Intelligence professional with a proven track of achievements and hands-on experience with a variety of SAP technologies . My main Focus is on SAP HANA / HANA XSA , SAC , BW/4HANA, and UI5 Development. I love my job and i love sharing my own knowledge and experiences and guiding others as they explore their possibilities and career paths in the SAP BI field.
My Mentoring Topics
- Business intelligence , SAP HANA , SAP Analytics cloud, BW/4 HANA , Data Modeling ,SQL
Marwah didn't receive any reviews yet.
You need to be logged in to schedule a session with this mentor. Please sign in here or create an account.
The Phoenix Project - A Novel about IT, DevOps, and Helping Your Business Win
Gene Kim, Kevin Behr, George Spafford
Key Facts and Insights from "The Phoenix Project" The Three Ways: The first principle, known as "The flow of work from left to right," emphasizes the need for work to be visualized and flow smoothly from development to operations to the customer. The second principle, "Amplify feedback loops," underscores the importance of creating channels for necessary adjustments. The third principle, "Continual experimentation and learning," promotes a culture of continual experimentation, taking risks, and learning from failure. DevOps: The book emphasizes the critical role of DevOps in modern IT operations and how it can help businesses win. DevOps represents the integration of development and operations teams to deliver better, faster, and more reliable outcomes. IT as a competitive advantage: The book argues that IT is no longer just a support function but a strategic asset that can provide a competitive advantage when managed effectively. Importance of Visibility: The book stresses the importance of visibility in IT operations. It emphasizes the need for clear visibility of work-in-progress, flow, and feedback to reduce wastage and increase efficiency. Work in Progress (WIP): The book highlights the dangers of excessive WIP and how it can lead to burnout and inefficiency. It recommends limiting WIP to improve flow and efficiency. Technical Debt: The book discusses the concept of technical debt and how neglecting it can lead to long-term inefficiencies and increased costs. Value of IT operations: The book underscores the value that IT operations bring to a business, emphasizing the need for organizations to invest in their IT operations. Culture of Learning: The book advocates for a culture of learning where failures are seen as opportunities for learning, not blame. Infrastructure as Code (IaC): The book introduces the concept of Infrastructure as Code, a key DevOps practice that involves managing and provisioning computer data centers through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools. Automation: The Phoenix Project highlights the importance of automation in reducing errors, freeing up human resources, and increasing efficiency and productivity. Managing Bottlenecks: The book discusses the Theory of Constraints and how managing bottlenecks in any process can improve overall performance. In-depth Analysis "The Phoenix Project" presents a compelling case for the integration of development and operations teams through a method known as DevOps. This critical shift in IT operations management can best be understood through the lens of The Three Ways. The first way emphasizes the need for work to flow smoothly from development to operations to the customer, a principle that is at the heart of DevOps. The second way underscores the importance of creating channels for necessary adjustments or feedback. This feedback loop is an integral part of the DevOps culture as it helps teams to identify and rectify issues promptly, thereby improving the quality of outcomes. The third way promotes a culture of continual experimentation, learning, and understanding that failure is a part of this process. The authors, Gene Kim, Kevin Behr, and George Spafford, argue convincingly that IT is no longer just a support function but a strategic asset that can provide a competitive advantage when managed effectively. This is a significant shift from traditional perspectives and places IT at the heart of business strategy. The book also emphasizes the importance of visibility in IT operations. It is essential to have clear visibility of work-in-progress, flow, and feedback to reduce wastage and increase efficiency. In this context, the book introduces the concept of technical debt, which refers to the future cost of correcting shortcuts taken in system development or maintenance today. If neglected, technical debt can lead to long-term inefficiencies and increased costs. One of the key insights from the book is the dangers of excessive Work in Progress (WIP). Too much WIP can lead to burnout and inefficiency. To address this, the authors recommend limiting WIP to improve flow and efficiency. This is a core principle of lean and agile methodologies, which aim to reduce waste and increase the delivery speed. The Phoenix Project also introduces the concept of Infrastructure as Code (IaC), a key practice in DevOps. IaC involves managing and provisioning computer data centers through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools. This is a significant shift from traditional IT operations and provides a more efficient and reliable approach to managing infrastructure. Automation is another key theme in the book. The authors highlight the importance of automation in reducing errors, freeing up human resources, and increasing efficiency and productivity. This is a key practice in DevOps, where the aim is to automate as much of the software delivery pipeline as possible. Finally, the authors discuss the Theory of Constraints and how managing bottlenecks in any process can improve overall performance. This is an essential principle in operations management and is particularly relevant in the context of IT operations, where bottlenecks can significantly hinder the delivery speed. In conclusion, "The Phoenix Project" provides a compelling case for adopting DevOps and rethinking the role of IT in business strategy. The principles and practices discussed in the book have the potential to transform IT operations and help businesses win in a competitive environment.
ViewInvisible Women - Data Bias in a World Designed for Men
Caroline Criado Perez
Key Facts from "Invisible Women - Data Bias in a World Designed for Men" Gender data gap: Most societal norms, systems, and designs have been created using data predominantly from male subjects. Sex-disaggregated data: The lack of sex-disaggregated data leads to a lack of representation for women in various fields and designs. Healthcare bias: The gender data gap in medical research and healthcare leads to misdiagnoses and ineffective treatment for women. Economic inequality: The economic system is set up in a way that undervalues and ignores women's work. Transportation and urban planning: Infrastructure and planning are designed with the male commuter in mind, ignoring the different travel patterns and safety concerns of women. Technology: Tech products are designed for the average male, leading to an inherent bias in their design and functionality. Workplace bias: Offices and workplaces are designed considering the comfort and needs of men, disregarding those of women. Public safety: Women's safety is often overlooked in public policies and urban planning, leading to a lack of safety provisions for women in public spaces. Disaster response: Disaster response strategies are often designed without considering the specific needs and vulnerabilities of women, causing them to bear the brunt of disasters. Political representation: The lack of women in decision-making positions leads to policies that overlook women's needs. Detailed Analysis "Invisible Women - Data Bias in a World Designed for Men", by Caroline Criado Perez, presents a compelling argument about the gender data gap and its wide-ranging effects on society. The author argues that the world is predominantly designed for men, citing various instances where women's needs and experiences have been overlooked. The concept of the gender data gap is a central theme in the book. Perez posits that the data used to design many systems, norms, and products is biased, as it is primarily collected from men. This leads to a male-centric view that permeates various aspects of society, making women 'invisible.' In healthcare, for instance, Perez highlights the lack of sex-disaggregated data, with most medical research being conducted on male subjects. This bias often results in misdiagnoses and ineffective treatments for women, as their symptoms and responses to medication can differ significantly from those of men. The economy is another area where this bias is evident. Women's work, particularly unpaid domestic work and caregiving, is undervalued and often ignored in economic systems. This leads to economic inequality and exacerbates the gender pay gap. The gender data gap also extends to infrastructure and urban planning, which are typically designed with the male commuter in mind, disregarding women's different travel patterns and safety concerns. Perez further explores how tech products, offices, public safety policies, disaster response strategies, and political representation all reflect the male-centric bias. Tech products, for example, are designed for the 'average' male user, making them uncomfortable or even dangerous for women to use. In the workplace, settings are often designed for the comfort of men, with little consideration for women's needs. The author also highlights the lack of safety provisions for women in public spaces, with public safety policies often ignoring women's unique safety concerns. The gender bias extends to disaster response strategies, where the specific needs and vulnerabilities of women are not considered, leading to a higher impact on women during disasters. The lack of women in decision-making positions, according to Perez, contributes significantly to these issues. This underrepresentation leads to a lack of policies that address women's needs and experiences. The key takeaway from Perez's work is the urgent need to address the gender data gap and incorporate women's experiences and needs into all aspects of design, policy-making, and research. Acknowledging and addressing this bias is critical to creating a more equitable society for all. References to Concepts and Ideas Perez's work intersects with several key concepts and theories in gender studies, sociology, and economics. These include intersectionality, which considers how various forms of inequality often operate together and exacerbate each other, and feminist economics, which critiques traditional economics as being inherently biased towards men. Moreover, the book aligns with the concept of gender mainstreaming, an approach to policy development that takes into account both women's and men's interests and experiences. It also draws on the notion of gendered innovations, which encourages the inclusion of sex and gender analysis in research and development. In conclusion, "Invisible Women" is a call to action to address the systemic bias in our societies and to work towards a more inclusive world where women's experiences, needs, and contributions are acknowledged and valued. Through this book, Perez offers a powerful critique of the gender data gap, urging us all to challenge and change the status quo. The book is an essential read for anyone interested in understanding and addressing gender inequality in our world.
ViewStorytelling with Data - A Data Visualization Guide for Business Professionals
Cole Nussbaumer Knaflic
Key Facts and Insights: Effective data visualization is a critical tool in business communication. Context is key in data storytelling; without it, your audience may not understand your message. Too much data can be overwhelming; simplicity is often more effective. Color and design elements should enhance understanding, not distract. Story structure can provide a framework for presenting data. Visual cues guide the audience's attention and highlight important information. Audience understanding and action is the ultimate goal of data storytelling. The book provides practical examples and exercises for honing data visualization skills. It emphasizes on the importance of scrutinizing, altering, and improving data visuals for clarity and impact. The book reiterates the significance of data ethics and the potential consequences of misleading data visuals. An In-depth Look at the Book "Storytelling with Data – A Data Visualization Guide for Business Professionals" by Cole Nussbaumer Knaflic is an invaluable resource for anyone who needs to distill complex datasets into meaningful narratives that can drive business decisions. As data becomes increasingly crucial in the business world, being able to effectively visualize and communicate this data is a vital skill. The book begins with the premise that effective data visualization is a critical tool in business communication. This is a truth I have affirmed over my years as a professor, seeing how the ability to present data in a clear and compelling way can significantly impact business strategies and decisions. Knaflic also emphasizes that context is key in data storytelling. Without it, the audience may not understand the points you are trying to make. This aligns with the concept of situational analysis in business communication, where understanding the context can determine the effectiveness of the communication. One of the salient points in the book is the idea that too much data can be overwhelming and that simplicity is often more effective. This resonates with the principle of 'less is more' that I often advocate to my students. The ability to distill complex data into a simple, understandable format is a skill that is highly valued in the business world. Knaflic also discusses how color and design elements should enhance understanding, not distract. This underscores the importance of aesthetic considerations in data visualization, a point often overlooked by professionals who focus solely on the data's numerical aspects. The book further highlights how a story structure can provide a framework for presenting data. This concept of using a narrative arc to present data is a powerful tool, as it taps into our innate affinity for stories, making the data more relatable and memorable. Visual cues are another tool discussed in the book that can guide the audience's attention and highlight important information. This is in line with the cognitive theory of multimedia learning, which posits that visual cues can help guide cognitive processing and enhance understanding. Knaflic's ultimate goal is to ensure that the audience understands the data and takes appropriate action. This aligns with the communication theory's purpose, which is not just to inform but also to persuade and motivate action. One of the book's strengths is its focus on practical application. It provides practical examples and exercises to hone data visualization skills, allowing readers to apply the principles learned. The book also emphasizes the importance of scrutinizing, altering, and improving data visuals for clarity and impact, underscoring the iterative nature of the data visualization process. Lastly, it reiterates the significance of data ethics and the potential consequences of misleading data visuals. This is a critical reminder, given the potential misuse of data and the impact it can have on decision making and trust. In conclusion, "Storytelling with Data" offers a comprehensive approach to data visualization, combining theory, practical application, and ethical considerations. It is a valuable resource for professionals looking to enhance their data visualization skills and effectively communicate data-driven insights in the business world.
ViewThinking, Fast and Slow
Daniel Kahneman
Key Insights from 'Thinking, Fast and Slow' Cognitive Ease: The human brain tends to choose the path of least resistance when processing information. System 1 and System 2: Two distinct systems govern our thought processes. System 1 is fast, intuitive, and emotional, while System 2 is slow, deliberate, and logical. Heuristics and Biases: Our brains use mental shortcuts or 'heuristics' to make quick decisions, which can often lead to biases in our thinking. Prospect Theory: People tend to make decisions based on potential losses and gains, not final outcomes. Anchoring Effect: The first piece of information we receive about a subject heavily influences our perception of subsequent information. Availability Heuristic: We tend to judge the probability of events by how easily examples come to mind. Endowment Effect: We value things more when we own them. Hindsight Bias: Our tendency to see events as more predictable than they really are after they have happened. Framing Effect: The way information is presented can drastically affect how we perceive it and make decisions. The Halo Effect: Our overall impression of a person influences how we feel and think about their character. Deeper Analysis of the Book's Concepts 'Thinking, Fast and Slow', a seminal work by Daniel Kahneman, delves into the two systems that drive the way we think—System 1, which is fast and intuitive, and System 2, slow and deliberate. This dual-process theory of cognition is not new, but Kahneman's exploration of how these systems interact, often leading to cognitive biases, is groundbreaking. System 1 operates automatically and quickly, with little or no effort and no sense of voluntary control. It's the part of our brain that responds to a surprising sound in the darkness or decides to swerve to avoid an accident. This system is heavily influenced by our past experiences and emotions, making its responses feel intuitive and automatic. In contrast, System 2 allocates attention to the effortful mental activities that demand it, including complex computations and conscious decision-making. This system is slower and more deliberate, often stepping in to verify and modify the impressions and intuitions from System 1. However, System 2 is lazy and often defaults to the easier, automatic responses of System 1. This is where cognitive biases come in. Heuristics and biases are mental shortcuts that System 1 uses to make quick decisions. While these shortcuts can often be useful, they can also lead to systematic errors in our thinking. For example, the availability heuristic might lead us to overestimate the likelihood of dramatic events (like plane crashes) because they are more memorable and thus more easily available to our minds. Prospect theory, introduced by Kahneman and his colleague Amos Tversky, challenges traditional economic theory, which assumes that humans are rational actors. Instead, prospect theory suggests that people make decisions based on potential gains and losses, not the final outcome. This can lead to seemingly irrational decisions, such as refusing to take a small loss to potentially gain more in the long run. The anchoring effect describes our tendency to rely heavily on the first piece of information we receive (the "anchor") when making decisions. Even when the anchor is arbitrary or irrelevant, it can dramatically influence our judgments and estimates. Similarly, the framing effect reveals that the way information is presented can drastically affect our decisions. For example, people are more likely to opt for a surgical procedure if it’s presented with a 90% survival rate than a 10% mortality rate, even though both statistics convey the same information. In conclusion, 'Thinking, Fast and Slow' highlights how our thought processes—though powerful—are not always as rational, objective, or logical as we might believe. By understanding these biases, we can take steps to mitigate them and make better, more informed decisions.
View