Epics -

Moblie:- 8668266780

Email:- info@v-academy.in

Vrindawan Academy

    Epics

    / Epics, Literature / By

    Epics ?

    “Epics” can refer to different things depending on the context:

    1. In Literature:
      • An epic is a lengthy narrative poem, typically detailing the heroic deeds, adventures, and journeys of a central figure or group of figures. Examples include The Iliad and The Odyssey by Homer, and The Aeneid by Virgil.
    2. In Agile Project Management:
      • An epic is a large body of work that can be broken down into smaller tasks called “user stories.” In Agile methodologies like Scrum and Kanban, epics represent big features or objectives that will be developed over time. They help in organizing and prioritizing large chunks of work that span multiple iterations.
    3. In Video Games:
      • In some gaming contexts, an epic can refer to a rare or high-quality item, weapon, or event that has special attributes or significance within the game’s world.
    4. In Business:
      • It can also be a term used for grand-scale, visionary projects, especially those aiming to make a significant impact or last over a long period.

    Which context are you referring to?

    What is Epics ?

    Epics” can be interpreted in different ways depending on the context. Here are the common meanings:

    1. In Literature:
      • An epic is a long narrative poem, often written in a grand, formal style. It tells the story of a hero or a group of heroes whose actions are central to the fate of a nation or the world. These works typically involve themes of heroism, adventure, and significant cultural or moral lessons. Famous examples include The Iliad and The Odyssey by Homer, The Aeneid by Virgil, and Beowulf.
    2. In Agile Project Management:
      • An “epic” is a term used in Agile frameworks (such as Scrum or Kanban) to describe a large body of work that can be broken down into smaller, more manageable tasks called “user stories.” Epics usually represent major features, goals, or initiatives that span multiple iterations or sprints. They are used to track large-scale progress and ensure that work is organized in a way that is achievable within the scope of the overall project.
    3. In Business and Product Development:
      • An epic might refer to a broad, high-level objective or project that has significant importance for a company or organization. It is usually broken down into smaller tasks or sub-projects for easier execution and management.
    4. In Video Games:
      • The term “epic” is often used to describe a special, high-quality item, weapon, or event that stands out due to its rarity, power, or significance within the game’s world. Epics in gaming typically offer enhanced abilities or features compared to standard items.

    So, “epics” can mean long stories of heroic deeds in literature, large tasks in Agile methodologies, or significant milestones in various contexts. Would you like further clarification on any of these definitions?

    Who is required Epics ?

    The term “epics” can be required by different groups or individuals depending on the context:

    1. In Literature:
      • Readers and Scholars: Those studying literature, history, or mythology may require epics for academic purposes or general interest. These texts are valuable for understanding cultural histories, heroism, and moral lessons that shape societies.
      • Writers and Poets: Authors who wish to create stories with grand, epic themes may draw inspiration from traditional epics.
    2. In Agile Project Management:
      • Product Owners and Managers: In an Agile development environment, product owners and managers are responsible for creating epics. These are large features or initiatives that need to be broken down into smaller tasks (user stories) for easier development.
      • Agile Teams: Development teams, including software developers, designers, and testers, work on the user stories that stem from epics. They require these epics to understand the larger vision or goal they are working toward.
    3. In Business:
      • Project Managers: In business settings, project managers might require epics to manage large, overarching projects or initiatives. They help break down goals into smaller tasks to ensure progress.
      • Teams/Departments: Different departments involved in a project may need epics to align their work with broader company goals.
    4. In Video Games:
      • Game Developers: Developers working on game design might create epic content, such as epic quests, items, or events, to engage players. These elements can require significant effort and planning to create.
      • Players: Players who are seeking rare or powerful items, achievements, or experiences in a game may seek out epic-level content to advance or enrich their gaming experience.

    In short, anyone involved in large-scale projects, storytelling, game development, or management may require or interact with epics. Are you referring to a specific area where “epics” are required?

    When is required Epics ?

    The need for epics arises at different stages depending on the context. Here are when epics are typically required:

    1. In Literature:

    • When Telling Grand Stories: Epics are required when a writer or storyteller wants to narrate long, heroic tales that involve grand adventures, epic journeys, or significant cultural or moral themes. Epics are often required for works that are intended to capture the imagination of an audience over a longer span, conveying a larger-than-life narrative.
    • Historical or Cultural Context: Epics may be written or required when documenting the history, mythology, or cultural heritage of a particular society. This helps preserve and share the foundational stories that shape traditions.

    2. In Agile Project Management:

    • During the Initial Planning Stage: Epics are required at the start of an Agile project to define broad, high-level objectives or features that will drive the development. They serve as a roadmap for the project and help guide the team’s work.
    • When Organizing Large Features: If a product development or software project has significant, complex features that cannot be completed in one sprint, epics are required to break them down into manageable chunks (user stories).
    • When Setting Long-Term Goals: In Agile, epics are required for tracking progress on larger goals that span multiple iterations. As the team moves forward, epics help maintain focus on the bigger picture while dealing with the smaller, more actionable tasks.

    3. In Business and Project Management:

    • When Managing Large-Scale Projects: Epics are required when dealing with projects that involve multiple teams, resources, and stages. Breaking the project down into epics helps ensure that progress can be tracked and that everyone involved has a clear understanding of the overarching goal.
    • When Defining Major Initiatives: If a company has a long-term initiative or business objective, epics are required to break it into smaller, actionable tasks. This helps in prioritizing and allocating resources effectively.

    4. In Video Games:

    • When Designing Major Game Features: Developers require epics when creating substantial game elements like major quests, storylines, or powerful in-game items that will take time and resources to develop.
    • When Creating Special or Rare Content: Players require epics when they seek to accomplish significant achievements, such as completing rare quests, acquiring powerful items, or achieving the highest level of difficulty in a game. Game developers typically require epics when creating these types of content.

    In Summary:

    Epics are required at the beginning of a project or when large-scale or long-term work needs to be broken down into more manageable, actionable components. Whether you’re working on a literature project, an Agile development, or a business initiative, epics help organize and manage the flow of work towards achieving bigger goals. Would you like to know more about how to create or manage epics in a specific context?

    COURTESY : Divineocean ai

    Where is required Epics ?

    The term epics is required in various contexts across different domains. Here’s where epics are typically required:

    1. In Literature:

    • Epic Literature: Epics are required in literary traditions where long, narrative poems or stories are needed to convey larger-than-life tales, cultural histories, or heroic deeds. They are often found in ancient literature and mythologies.
    • Cultural Heritage: Epics are required in places where a culture needs to preserve and pass down its foundational stories, heroes, and values. These stories can shape national identity or community traditions.

    2. In Agile Project Management:

    • In Agile Development Teams: Epics are required in Agile software development and project management settings to organize and structure large, high-level features or initiatives that cannot be completed in a single sprint. They are needed in Scrum, Kanban, or other Agile methodologies.
    • In Product Backlogs: Epics are typically used in a product backlog in Agile environments to describe the broader objectives that need to be broken down into smaller user stories. They are used across software development projects, IT infrastructure projects, and product development.

    3. In Business and Project Management:

    • In Large-Scale Projects: Epics are required in project management to break down large, complex projects or initiatives into smaller, more manageable tasks. This could include business transformation projects, product development cycles, or company-wide strategic goals.
    • In Business Process Improvements: Epics are useful when businesses are trying to improve their internal processes or develop new systems. For example, when a company decides to overhaul its customer service strategy, epics help organize and track progress across various departments.

    4. In Video Games:

    • In Game Design: Epics are required by game developers to create significant content such as major quests, boss fights, or rare items. These elements often require significant resources and time to design and implement.
    • In Game Events and Challenges: Epics are required in live service games for organizing large-scale events, challenges, or content updates that require careful planning and execution. For example, seasonal events or expansion packs may involve epics to break them into smaller tasks.
    • In RPGs: Players in role-playing games (RPGs) may encounter epics in the form of large quests or challenges that span a game’s storyline, often requiring significant effort to complete.

    In Summary:

    Epics are required wherever there is a need to manage large-scale, complex work across multiple tasks, teams, or stages. They are used in literature, Agile project management, business projects, video games, and other areas that deal with significant, long-term efforts.

    Would you like more details on how epics are used in a specific field?

    How is required Epics ?

    The requirement for epics can arise based on the need to organize, plan, and manage large-scale, complex work or projects. Here’s how epics are required and created in different domains:

    1. In Literature:

    • How Epics are Created/Required:
      • Writers, poets, or storytellers create epics when they want to tell grand, narrative tales that span long periods, involve heroic figures, and explore significant cultural or moral themes.
      • Epics are required to preserve cultural heritage and mythological traditions, often involving gods, heroes, and monumental events that reflect the identity and values of a culture.
      • The process of writing an epic often requires deep knowledge of history, culture, and the ability to engage readers over long passages.

    2. In Agile Project Management:

    • How Epics are Created/Required:
      • Product owners, project managers, or business analysts create epics when defining high-level features, goals, or initiatives that will guide the development process in Agile teams.
      • Epics are required when large features or goals cannot be completed in a single iteration (sprint). These are broken down into smaller, more manageable user stories that are executed across multiple sprints.
      • Agile teams require epics to understand the broader scope of the product development process. Epics help to visualize and manage big objectives while focusing on smaller, actionable tasks.
      • In this context, epics are broken down into:
        • User Stories: Smaller tasks that can be completed within a sprint.
        • Tasks: Specific actions or steps within a user story.

    3. In Business and Project Management:

    • How Epics are Created/Required:
      • Project managers, business leaders, or teams require epics when planning large-scale projects or strategic initiatives. These epics represent the high-level objectives of a project that may span several phases or departments.
      • Epics are required to break down large, complex business goals into manageable, actionable steps. For example, a company may require an epic to organize a company-wide product launch, with smaller tasks focused on marketing, logistics, customer support, and development.
      • Workshops, brainstorming sessions, or strategic meetings are often where epics are identified, defined, and structured.

    4. In Video Games:

    • How Epics are Created/Required:
      • Game developers create epics to define significant game features, quests, or events that require substantial effort and time to develop.
      • Epics are required to design major game content, such as new expansions, complex quests, or unique items that require detailed planning and resources.
      • Epics in games often span across various aspects of development, including programming, art, design, and sound. These tasks are broken down into smaller tasks that can be completed by different team members.
      • For example, a game expansion may be defined as an epic, which is then broken down into smaller tasks like designing levels, creating character assets, writing storylines, and testing.

    5. In Marketing and Sales:

    • How Epics are Created/Required:
      • Marketing managers create epics to define large marketing campaigns, product launches, or branding initiatives. These are typically broken down into smaller, actionable campaigns or projects that can be tracked over time.
      • Epics in marketing might include efforts like digital marketing strategies, event planning, or cross-channel promotional campaigns.
      • Campaign managers often break down epics into smaller tasks, such as social media management, content creation, ad management, and analytics tracking.

    6. In Education:

    • How Epics are Created/Required:
      • Curriculum designers, teachers, or education administrators create epics when developing broad educational goals, such as an entire module, semester-long course, or large curriculum initiative.
      • Epics in education are required when designing long-term learning objectives that need to be split into smaller, more specific lessons or units. These can be related to both academic subjects and extracurricular activities.
      • For example, an epic could be to teach a broad topic like “Understanding Climate Change”, which is then divided into smaller lessons about the science, effects, and solutions related to climate change.

    In Summary:

    Epics are created when there’s a need to manage large-scale or complex tasks that span a significant period of time, require multiple steps, or involve multiple team members or stakeholders. They are necessary for planning, organizing, and achieving long-term goals. Epics are then broken down into smaller, actionable tasks or stories to ensure manageable progress.

    Would you like to know more about how epics are structured or implemented in any specific domain?

    Case study is Epics ?

    A case study is not the same as an epic, but there can be some overlap in certain contexts, particularly in business, project management, and educational settings. Here’s how case studies and epics differ, and how they can sometimes relate:

    1. What is a Case Study?

    • A case study is a detailed analysis of a particular subject (such as a project, company, person, event, or phenomenon) to explore its complexities and learn from it. It typically provides in-depth information and insight into a real-world situation, offering lessons, challenges, and solutions.
    • In academic and business contexts, case studies often focus on specific challenges or success stories and are used for learning, research, or problem-solving.

    Key Characteristics of a Case Study:

    • Real-life examples or scenarios.
    • Focus on challenges, solutions, or lessons learned.
    • Used for analyzing and understanding specific situations in depth.
    • Typically provides qualitative analysis.

    2. What is an Epic?

    • An epic (in Agile project management) is a large body of work that can be broken down into smaller tasks or user stories. Epics represent high-level goals or features that span multiple sprints and typically require significant resources and time to complete.
    • Epics are generally used in the context of project management (particularly in Agile methodologies) to organize and manage larger work items within a project.

    Key Characteristics of an Epic:

    • A high-level goal or feature.
    • Spans multiple sprints or iterations.
    • Broken down into smaller tasks, called user stories.
    • Used to plan and structure the flow of work in a project.

    Case Study vs Epic: Key Differences:

    AspectCase StudyEpic
    NatureDetailed analysis of a specific situation or event.High-level goal or feature to be broken down into smaller tasks.
    FocusFocus on real-world examples, lessons learned, and problem-solving.Focus on project goals, features, and tasks.
    ContextTypically used in business, academic, or research settings.Primarily used in Agile project management to structure large tasks.
    OutcomeProvides insights, conclusions, and learning from the case.Helps in organizing and tracking work progress toward a goal.
    BreakdownDoes not have a structured breakdown but may lead to conclusions or recommendations.Can be broken down into user stories or tasks to be completed in multiple iterations.
    DurationGenerally focused on a single event or time period.Can span across multiple sprints or phases in a project.

    When Epics and Case Studies Can Overlap:

    While case studies and epics are distinct, epics in project management or Agile frameworks can sometimes be linked to case studies in certain situations:

    1. Using Case Studies to Define Epics:
      • In business or project management, case studies of past successful projects, challenges, or client solutions can be used to define epics in new projects. For example, analyzing a successful product launch or software implementation could lead to an epic such as “Develop new product features” based on the insights from the case study.
    2. Using Epics to Solve Problems in a Case Study:
      • A case study may present a business or project issue that is broken down into epics to structure the approach toward a solution. For instance, a case study on customer complaints in a retail business may lead to epics such as “Improve customer service experience” or “Develop a new CRM system.”
    3. Educational Purpose:
      • In some educational environments, a case study may be used as an epic-level challenge for students or teams to solve over an extended period. Students might break the case study down into smaller tasks, just as epics are broken down into user stories in Agile projects.

    Conclusion:

    • A case study is typically a deep dive into a particular situation, used for learning and problem-solving, often presented as a narrative with real-world examples and lessons learned.
    • An epic is a tool in Agile project management for organizing large, complex features or goals that need to be broken down into smaller tasks (user stories) to be completed over time.

    While they serve different purposes, epics can be used to frame and organize the work in projects, while case studies provide valuable insights for defining such work or learning from past experiences. Would you like to explore more on how case studies are used in project management or Agile methodologies?

    COURTESY : See U in History / Mythology

    White paper on Epics ?

    A White Paper on Epics can be a detailed document that explains the concept of epics, particularly in the context of Agile project management, but it can also discuss their application in other areas like product development, business strategy, and software development. Below is a structure for a white paper on Epics, including sections that explain their importance, usage, and best practices.

    White Paper: Understanding Epics in Agile Project Management

    Executive Summary

    An epic is a high-level body of work in Agile project management that encompasses a large goal or feature requiring multiple iterations (sprints) to complete. This white paper explores the concept of epics, their role in Agile methodologies, their lifecycle, and best practices for managing them to ensure successful project outcomes.

    Introduction

    In Agile project management, tasks and objectives are often broken down into smaller, more manageable pieces known as user stories. However, sometimes projects involve large-scale initiatives that cannot be completed in a single iteration. These larger goals are called epics, and they serve as a critical tool for managing complex tasks in Agile environments. Epics are vital in ensuring that projects are organized, trackable, and aligned with strategic business objectives.

    This white paper will explore:

    • The definition and purpose of epics in Agile.
    • The process of breaking down epics into smaller tasks.
    • How epics fit into the broader Agile framework (e.g., Scrum, Kanban).
    • Real-world examples and use cases of epics.
    • Best practices for managing and tracking epics in Agile environments.

    What are Epics?

    An epic is a large user story or feature that represents a significant piece of work within a project. Epics are typically too large to be completed in a single sprint and need to be broken down into smaller user stories for execution in multiple iterations.

    Characteristics of Epics:
    • High-Level Goal: Epics represent a broad objective or feature that aligns with the business’s strategic vision.
    • Longer Timeline: Unlike user stories, which can be completed in one sprint, epics span across multiple sprints or iterations.
    • Breakdown into Stories: Epics are divided into smaller, more manageable user stories that can be tackled by the team.
    • Cross-Functional Impact: Epics often require input and effort from multiple teams or departments, making them more complex than individual user stories.

    The Lifecycle of an Epic

    The lifecycle of an epic generally involves several stages:

    1. Creation: Epics are identified based on business needs, customer feedback, or strategic goals. They are added to the product backlog in the Agile framework.
    2. Refinement: As the project progresses, epics are further refined and broken down into smaller user stories.
    3. Execution: The user stories derived from epics are worked on during sprints, with progress tracked via tools like Jira, Trello, or Azure DevOps.
    4. Completion: Once all associated user stories are completed, the epic is considered finished, and its success is evaluated based on the original business objectives.

    Why are Epics Important?

    Epics play a crucial role in structuring and managing large initiatives. Here’s why they are important in Agile methodologies:

    • Organize Complex Work: Epics help break down large goals into smaller, manageable pieces, allowing teams to focus on delivering valuable outputs incrementally.
    • Provide a High-Level View: Epics offer a strategic perspective, helping product owners and stakeholders understand the broader goals of a project.
    • Improve Planning and Tracking: By defining epics, Agile teams can plan sprints more effectively and ensure that progress aligns with business objectives.
    • Align Teams: Epics bring clarity to cross-functional teams by ensuring that everyone is working towards the same strategic goals.

    Best Practices for Managing Epics

    To maximize the effectiveness of epics in Agile project management, the following best practices should be considered:

    1. Define Clear Goals: Ensure that each epic has a clear, well-defined business objective that aligns with strategic goals.
    2. Break Epics into Smaller Stories: Once an epic is created, break it down into smaller user stories that can be completed within a sprint. This makes it easier to manage and track progress.
    3. Prioritize Epics: Prioritize epics based on their value to the business. This will help ensure that the most important goals are tackled first.
    4. Monitor Progress: Use Agile tools (e.g., Jira, VersionOne) to track the progress of epics and their associated user stories. Ensure that each user story is completed within the designated sprint.
    5. Review and Refine Epics: Regularly review epics to ensure that they remain relevant and aligned with business objectives. Refinement is an ongoing process that helps keep the team focused.
    6. Use Epics for Long-Term Planning: While user stories are focused on short-term tasks, epics are ideal for long-term planning and can help guide the direction of the project over time.

    Real-World Examples of Epics

    1. Example 1: Software Development Project
      • Epic: “Develop User Authentication Feature.”
      • User Stories:
        • As a user, I want to create an account so that I can access personalized features.
        • As a user, I want to log in using my Google account for convenience.
        • As an admin, I want to manage user permissions for security purposes.
    2. Example 2: E-Commerce Website
      • Epic: “Revamp Checkout Process.”
      • User Stories:
        • As a customer, I want to save my payment information so that I can check out faster in the future.
        • As a customer, I want to view order summaries before finalizing the checkout.
        • As a customer, I want to apply discount codes easily during checkout.

    Challenges in Managing Epics

    While epics are essential for organizing large-scale work, managing them can come with challenges:

    • Scope Creep: Because epics are large and complex, it’s easy for them to expand beyond their original scope.
    • Resource Allocation: Large epics may require the efforts of multiple teams or departments, complicating resource planning and allocation.
    • Tracking Progress: Tracking the progress of an epic across multiple sprints can be challenging, especially when user stories evolve.

    Conclusion

    Epics are a powerful tool for organizing and managing complex work in Agile environments. By defining high-level goals and breaking them down into smaller user stories, teams can ensure that large initiatives are completed incrementally and aligned with business objectives. Adopting best practices for managing epics, such as clear goal setting, prioritization, and regular refinement, will help teams maintain focus and drive successful project outcomes.

    Recommendations

    • Invest time in thorough epic planning and definition to align with the team’s capabilities and business objectives.
    • Regularly refine epics to ensure they remain aligned with customer needs and project goals.
    • Use Agile tools to monitor and track the progress of epics and their associated stories.

    This white paper provides a comprehensive overview of epics, highlighting their importance, lifecycle, and best practices. It serves as a useful guide for Agile teams, product owners, and project managers looking to implement or improve their use of epics in managing large-scale projects.

    Industrial application of Epics ?

    he concept of Epics in Agile project management, typically associated with software development and product design, has broader industrial applications as well. In various industries, epics can be used to structure and organize large-scale initiatives, break down complex projects into manageable tasks, and ensure that strategic goals are met incrementally. Below are a few industrial applications of Epics:

    1. Manufacturing Industry

    In manufacturing, epics can be used to manage complex production processes, large-scale equipment upgrades, or the launch of new product lines. These epics are typically broken down into smaller tasks (user stories) to be addressed over multiple sprints or project phases.

    Examples of Epics in Manufacturing:

    • Epic: “Develop and Implement New Automated Production Line”
      • User Stories:
        • Design the new automation system.
        • Test and calibrate the robots for product assembly.
        • Integrate automation with inventory management system.
        • Train production team on operating the new system.
    • Epic: “Launch New Product Line”
      • User Stories:
        • Design new product packaging.
        • Set up production equipment.
        • Implement quality assurance protocols.
        • Market the new product to target customers.

    Benefits:

    • Helps manage large-scale projects in phases, ensuring continuous progress.
    • Ensures that each part of the production process aligns with strategic goals.
    • Improves team coordination by breaking down large projects into smaller, trackable tasks.

    2. Construction Industry

    The construction industry often deals with large-scale infrastructure projects that require careful planning and long timelines. Epics can be used to manage these projects, ensuring that different elements (e.g., architectural design, materials procurement, regulatory approvals, etc.) are completed in an organized and structured manner.

    Examples of Epics in Construction:

    • Epic: “Construct New Manufacturing Facility”
      • User Stories:
        • Finalize architectural design of the facility.
        • Obtain building permits and approvals.
        • Source construction materials.
        • Hire subcontractors for different phases of construction.
    • Epic: “Build New Bridge”
      • User Stories:
        • Complete geotechnical surveys.
        • Design the bridge’s structural components.
        • Procure materials for construction.
        • Conduct safety audits and compliance checks.

    Benefits:

    • Ensures large projects are divided into manageable chunks, each contributing to the final goal.
    • Tracks progress across multiple stages, from initial design to construction and final inspection.
    • Provides a clear overview for project managers, helping them allocate resources and monitor progress.

    3. Automotive Industry

    In the automotive industry, epics can be used to manage the design, manufacturing, and testing of new vehicles or vehicle components. These epics are especially useful in multi-phase projects that involve multiple teams (engineering, design, production, testing, etc.).

    Examples of Epics in Automotive:

    • Epic: “Design and Develop Electric Vehicle (EV)”
      • User Stories:
        • Research and select battery technology.
        • Design the vehicle chassis and body.
        • Integrate electric motor and powertrain components.
        • Conduct crash tests and safety assessments.
    • Epic: “Improve Fuel Efficiency of Existing Model”
      • User Stories:
        • Analyze current fuel consumption data.
        • Develop and test more efficient engine designs.
        • Upgrade aerodynamics for better fuel efficiency.
        • Implement lightweight materials in the vehicle.

    Benefits:

    • Coordinates the efforts of diverse teams (e.g., engineering, design, testing) to work toward a shared goal.
    • Provides a roadmap for product development and helps prioritize tasks.
    • Allows teams to release updates and improvements incrementally, ensuring ongoing innovation.

    4. Energy Sector

    The energy sector, including oil, gas, and renewable energy industries, involves large projects like the construction of energy plants, the installation of new infrastructure, or the implementation of new technologies. Epics help ensure these projects are well-managed and aligned with the company’s strategic objectives.

    Examples of Epics in Energy:

    • Epic: “Develop New Solar Power Plant”
      • User Stories:
        • Site selection and environmental impact studies.
        • Design the solar panel installation system.
        • Secure necessary permits and funding.
        • Install and test the solar panels.
    • Epic: “Upgrade Oil Refinery to Meet New Environmental Standards”
      • User Stories:
        • Review current facility compliance status.
        • Upgrade filtration systems to reduce emissions.
        • Train staff on new environmental compliance procedures.
        • Conduct regular environmental audits.

    Benefits:

    • Breaks down large-scale, multi-year projects into manageable units.
    • Helps teams focus on delivering specific outcomes while keeping an eye on the larger goal.
    • Ensures compliance and innovation are aligned with strategic goals in energy projects.

    5. Supply Chain & Logistics

    In the supply chain and logistics industry, epics can be used to manage the implementation of new systems, optimize logistics operations, or improve inventory management.

    Examples of Epics in Supply Chain:

    • Epic: “Implement Real-Time Inventory Management System”
      • User Stories:
        • Select and customize inventory management software.
        • Integrate the system with existing ERP software.
        • Train warehouse staff on the new system.
        • Conduct user acceptance testing.
    • Epic: “Enhance Supply Chain Visibility”
      • User Stories:
        • Integrate RFID technology for tracking goods.
        • Implement GPS tracking on delivery vehicles.
        • Create real-time dashboards for supply chain visibility.

    Benefits:

    • Coordinates the execution of large-scale technological or operational improvements across multiple locations or teams.
    • Ensures alignment between logistics, inventory, and overall business goals.
    • Helps track incremental improvements in efficiency, customer service, and cost reduction.

    6. Pharmaceutical and Healthcare Industry

    In the pharmaceutical and healthcare sectors, epics can be used for large-scale projects such as developing new medications, launching healthcare initiatives, or implementing new healthcare technologies.

    Examples of Epics in Healthcare:

    • Epic: “Develop New Drug for Disease X”
      • User Stories:
        • Conduct pre-clinical research and trials.
        • Develop manufacturing processes for the drug.
        • Conduct clinical trials and regulatory approval.
        • Launch marketing and distribution plans.
    • Epic: “Upgrade Hospital IT Systems”
      • User Stories:
        • Select and implement new electronic health record (EHR) software.
        • Train staff on the new system.
        • Test system integration with existing hospital infrastructure.
        • Roll out system to all hospital departments.

    Benefits:

    • Helps healthcare organizations manage complex projects that involve both technical and regulatory requirements.
    • Ensures progress is made incrementally while aligning with critical milestones (e.g., clinical trials, regulatory approvals).
    • Facilitates communication and collaboration across multidisciplinary teams.

    Conclusion

    In various industries, epics serve as a powerful tool for managing large, complex projects by breaking them down into smaller, more manageable tasks. By adopting an epic-based approach, companies can:

    • Align large initiatives with strategic business goals.
    • Ensure that progress is made incrementally and in phases.
    • Improve collaboration between cross-functional teams.
    • Maintain focus on the overall vision while managing detailed, tactical work.

    Whether in manufacturing, construction, energy, automotive, logistics, or healthcare, epics provide a structured way to handle significant projects and drive organizational success over time.

    Research and development of Epics ?

    The research and development (R&D) of Epics refers to the process of creating, refining, and optimizing epic stories as part of the Agile methodology in project management. An Epic is a large body of work that can be broken down into smaller, more manageable tasks (often user stories). Epics are usually created during the early stages of the project and help provide a broad vision of the project’s objectives. Their R&D process helps ensure they align with the project’s strategic goals and are efficiently broken down into user stories.

    Here’s a detailed explanation of how Epics are researched and developed across different stages:

    1. Identifying and Defining the Epic

    The first step in developing an Epic involves identifying the high-level business goal or project milestone. This stage focuses on understanding the bigger picture and ensures that the Epic aligns with strategic objectives. This involves collaboration with stakeholders, product owners, and other decision-makers.

    Research Activities at this Stage:

    • Market Research: Understanding customer needs, market trends, and competitive landscape.
    • Stakeholder Interviews: Gathering input from internal and external stakeholders to understand their priorities.
    • Defining Value Proposition: Identifying the business value that the Epic will deliver (e.g., improving efficiency, increasing revenue, launching a new product).

    Output:

    • Epic Definition: A concise statement of what needs to be achieved and why it’s important.
    • Initial Scope: The boundaries of the Epic, including what will and won’t be addressed in the Epic.

    2. Breaking the Epic into Smaller Components

    Once the Epic has been defined, it’s essential to break it down into smaller, manageable units (user stories). This phase involves further refinement to ensure that the Epic is not too broad and can be realistically accomplished within the overall project timeframe.

    Research Activities at this Stage:

    • Stakeholder Workshops: Working with the team, including product owners, developers, and other stakeholders, to break down the Epic into smaller features or functionalities.
    • Feasibility Studies: Determining whether each smaller unit (user story) can be completed within the expected timelines.
    • Dependency Mapping: Identifying dependencies between user stories to avoid delays.

    Output:

    • Refined Epic: A more focused version of the Epic that is broken into features or capabilities.
    • User Stories: These represent smaller deliverables or tasks that can be completed within a sprint.

    3. Prioritizing Epics and User Stories

    In Agile project management, Epics and user stories must be prioritized based on their business value, urgency, and technical feasibility. Researching and identifying the most important items to tackle first ensures that the most valuable tasks are completed as early as possible.

    Research Activities at this Stage:

    • Business Impact Analysis: Understanding the business impact of each user story or feature.
    • Risk Assessment: Identifying any risks or uncertainties that might affect the progress or completion of specific tasks.
    • Cost-Benefit Analysis: Analyzing the costs of completing certain user stories against the potential benefits.

    Output:

    • Prioritized Backlog: A list of Epics and user stories ranked by importance.
    • Release Plan: A roadmap detailing when and in what order user stories will be completed.

    4. Implementation and Iteration

    The actual development of an Epic happens through multiple sprints or iterations. As Epics are implemented, the team reviews their progress and may need to adjust the scope or approach depending on the feedback from stakeholders, customer needs, or technical constraints.

    Research Activities at this Stage:

    • Customer Feedback: Gathering customer feedback to validate whether the Epic’s objectives are aligned with user needs.
    • Prototype Development: Testing prototypes or early versions of features to assess their performance and feasibility.
    • Continuous Improvement: Regularly refining user stories, adjusting priorities, and improving processes based on feedback.

    Output:

    • Functional Features: Completed user stories that are part of the larger Epic.
    • Validated Solutions: Solutions that have been tested and refined based on customer feedback or performance data.

    5. Review and Reflection

    Once the Epic has been developed, it’s important to evaluate the results. The R&D team reviews whether the Epic has met its original goals and objectives and identifies any areas for improvement.

    Research Activities at this Stage:

    • Post-Implementation Review: Reviewing the performance of the Epic and its impact on business goals.
    • Lessons Learned: Identifying areas where the process could be improved for future Epics.
    • Customer Satisfaction Surveys: Gathering feedback from stakeholders or end users to assess satisfaction levels.

    Output:

    • Final Epic Report: An assessment of the Epic’s impact and lessons learned.
    • Refined R&D Processes: Improvements in how Epics are defined, broken down, and developed in the future.

    6. Continuous Evolution

    As part of the ongoing Agile process, the work on Epics may continue to evolve based on emerging business needs, technological advancements, and feedback. R&D teams must stay adaptable and refine existing Epics or create new ones as required.

    Research Activities at this Stage:

    • Emerging Trends: Continuous monitoring of market trends, technological advancements, and user needs.
    • Innovation: Researching new approaches, technologies, and methods that could improve the Epic development process.
    • Market Adaptation: Adapting to changing market dynamics, such as customer preferences or new regulatory requirements.

    Output:

    • Revised Epics: Updated or new Epics that reflect the latest business and customer needs.
    • Ongoing R&D Cycle: A continuous process of research, development, and improvement to stay aligned with the strategic objectives.

    Research Tools and Techniques in Epic Development

    1. Agile Project Management Software: Tools like Jira, Trello, or Asana are commonly used for creating and tracking Epics and user stories, as well as for collaboration between cross-functional teams.
    2. User Research: Techniques such as user interviews, surveys, focus groups, and usability testing are essential to gather insights that inform the definition and refinement of Epics.
    3. Competitive Analysis: Analyzing competitor products or services to ensure the Epic delivers superior value.
    4. Risk Analysis: Identifying potential technical, operational, or financial risks that could hinder the progress of the Epic or user stories.
    5. Prototyping and Proof of Concepts (PoC): Creating prototypes or PoCs to validate new ideas and features before committing to full-scale development.

    Conclusion

    The research and development of Epics is a dynamic, collaborative, and iterative process that requires deep understanding of customer needs, business goals, and technological feasibility. By following a structured approach to research, breaking down large initiatives into smaller tasks, and prioritizing efforts based on value and impact, organizations can deliver successful and valuable outcomes while staying flexible in response to evolving conditions. Through continuous feedback and refinement, the R&D of Epics ensures that the final product aligns with strategic objectives and delivers measurable results.

    COURTESY : The EPIC Channel

    References

    1. ^ “Literature: definition”. Oxford Learner’s Dictionaries. Archived from the original on 10 June 2021. Retrieved 24 July 2020.
    2. ^ Rettberg, Scott (2019). Electronic literature. Cambridge, UK Medford, MA: Polity press. ISBN 978-1-5095-1677-3.
    3. ^ Goody 1987.
    4. ^ Jump up to:a b Goody, Jack. “Oral literature”. Encyclopaedia Britannica. Archived from the original on 14 December 2019. Retrieved 27 July 2020.; see also Homer.
    5. ^ A Beginner’s Guide to Literary Fiction” | NY Book Editors.
    6. ^ Girolimon, Mars. “Types of Genres: A Literary Guide”, Southern New Hampshire University, 11 December 2023. Retrieved 3 September 2024.
    7. ^ Jump up to:a b Rexroth, Kenneth. “literature | Definition, Characteristics, Genres, Types, & Facts”. Encyclopedia Britannica. Archived from the original on 29 July 2020. Retrieved 27 July 2020.
    8. ^ Jump up to:a b OED[full citation needed]
    9. ^ Leitch et al., The Norton Anthology of Theory and Criticism, 28
    10. ^ “literature (n.)”. Online Etymology Dictionary. Archived from the original on 22 February 2014. Retrieved 9 February 2014.
    11. ^ Meyer, Jim (1997). “What is Literature? A Definition Based on Prototypes”. Work Papers of the Summer Institute of Linguistics and University of North Dakota Session. 41 (1). Retrieved 11 February 2014.[dead link]
    12. ^ Finnegan, Ruth (1974). “How Oral Is Oral Literature?”. Bulletin of the School of Oriental and African Studies. 37 (1): 52–64. doi:10.1017/s0041977x00094842. JSTOR 614104. S2CID 190730645. (subscription required)
    13. ^ Field, Syd (2005). “Introduction”. Screenplay: The Foundations of Screenwriting. Delta. ISBN 978-0440582731.
    14. ^ Eagleton 2008, p. 9.
    15. ^ Biswas, A.R. (2005). Critique of Poetics. Vol. 2. Atlantic Publishers & Dist. p. 538. ISBN 978-81-269-0377-1. Archived from the original on 14 April 2021.
    16. ^ Jump up to:a b Johnson, Sian (26 February 2020). “Study dates Victorian volcano that buried a human-made axe”. ABC News. Archived from the original on 8 September 2020. Retrieved 9 March 2020.
    17. ^ Matchan, Erin L.; Phillips, David; Jourdan, Fred; Oostingh, Korien (2020). “Early human occupation of southeastern Australia: New insights from 40Ar/39Ar dating of young volcanoes”. Geology. 48 (4): 390–394. Bibcode:2020Geo….48..390M. doi:10.1130/G47166.1. ISSN 0091-7613. S2CID 214357121.
    18. ^ Jump up to:a b John Miles Foley. “What’s in a Sign” (1999). E. Anne MacKay (ed.). Signs of Orality. Brill Academic. pp. 1–2. ISBN 978-9004112735.
    19. ^ Francis, Norbert (2017). Bilingual and Multicultural Perspectives on Poetry, Music, and Narrative: The science of art. Lanham, MD: Rowman and Littlefield. ISBN 978-1-4985-5183-0.
    20. ^ Donald S. Lopez Jr. (1995). “Authority and Orality in the Mahāyāna” (PDF). Numen. 42 (1). Brill Academic: 21–47. doi:10.1163/1568527952598800. hdl:2027.42/43799. JSTOR 3270278. Archived (PDF) from the original on 1 January 2011. Retrieved 22 October 2020.
    21. ^ “Buddhism – The Pali canon (Tipitaka) | Britannica”. www.britannica.com. Archived from the original on 17 March 2023. Retrieved 17 March 2023.
    22. ^ Ong, Walter J. (2002). Orality and Literacy: The Technologizing of the Word. Psychology Press. ISBN 978-0-415-28128-7. Archived from the original on 26 March 2023. Retrieved 17 March 2023.
    23. ^ Reece, Steve. “Orality and Literacy: Ancient Greek Literature as Oral Literature”, in David Schenker and Martin Hose (eds.), Companion to Greek Literature (Oxford: Blackwell, 2015) 43–57. Ancient_Greek_Literature_as_Oral_Literature Archived 1 January 2020 at the Wayback Machine
    24. ^ Michael Gagarin (1999). E. Anne MacKay (ed.). Signs of Orality. Brill Academic. pp. 163–164. ISBN 978-9004112735.
    25. ^ Wolfgang Kullmann (1999). E. Anne MacKay (ed.). Signs of Orality. Brill Academic. pp. 108–109. ISBN 978-9004112735.
    26. ^ John Scheid (2006). Clifford Ando and Jörg Rüpke (ed.). Religion and Law in Classical and Christian Rome. Franz Steiner Verlag. pp. 17–28. ISBN 978-3-515-08854-1. Archived from the original on 20 August 2020. Retrieved 22 October 2020.
    27. ^ Kroeber, Karl, ed. (2004). Native American Storytelling: A Reader of Myths and Legends. Malden, MA: Blackwell Publishing. pp. 1. ISBN 978-1-4051-1541-4.
    28. ^ Kroeber, Karl, ed. (2004). Native American Storytelling: A Reader of Myths and Legends. Malden, MA: Blackwell Publishing. pp. 3. ISBN 978-1-4051-1541-4.
    29. ^ Jump up to:a b c Kroeber, Karl, ed. (2004). Native American Storytelling: A Reader of Myths and Legends. Malden, MA: Blackwell Publishing. pp. 2. ISBN 978-1-4051-1541-4.
    30. ^ Doucleff, Michaeleen; Greenhalgh, Jane (13 March 2019). “How Inuit Parents Teach Kids To Control Their Anger”. NPR. Archived from the original on 26 October 2020. Retrieved 29 April 2019.
    31. ^ Diko, Mlamli (28 July 2023). “The retainment of South African indigenous languages: a systemic literature review”. International Journal of Research in Business and Social Science (2147- 4478). 12 (5): 306–314. doi:10.20525/ijrbs.v12i5.2427. ISSN 2147-4478.
    32. ^ See, e.g., Thomas Conley, Rhetoric in the European Tradition (University of Chicago, 1991).
    33. ^ See, for instance Parlor, Burkean; Johnstone, Henry W. (1996). “On schiappa versus poulakos”. Rhetoric Review. 14 (2): 438–440. doi:10.1080/07350199609389075.
    34. ^ Green, M.W. (1981). “The Construction and Implementation of the Cuneiform Writing System”. Visible Language. 15 (4): 345–372.
    35. ^ Foster 2001, p. 19.
    36. ^ Black, Jeremy; Cunningham, Graham; Robson, Eleanor, eds. (2006). The literature of ancient Sumer. Oxford: OUP. p. xix. ISBN 978-0-19-929633-0.
    37. ^ Foster 2001, p. 7.
    38. ^ Lichtheim, Miriam (1975). Ancient Egyptian Literature, vol 1. London: University of California Press. ISBN 0-520-02899-6.
    39. ^ Jacobs 1888, Introduction, page xv; Ryder 1925, Translator’s introduction, quoting Hertel: “the original work was composed in Kashmir, about 200 B.C. At this date, however, many of the individual stories were already ancient.”
    40. ^ Ryder 1925 Translator’s introduction: “The Panchatantra is a niti-shastra, or textbook of niti. The word niti means roughly “the wise conduct of life.” Western civilization must endure a certain shame in realizing that no precise equivalent of the term is found in English, French, Latin, or Greek. Many words are therefore necessary to explain what niti is, though the idea, once grasped, is clear, important, and satisfying.”
    41. ^ Baxter (1992), p. 356.
    42. ^ Allan (1991), p. 39.
    43. ^ Zheng Xuan 鄭玄 (AD 127–200), Shipu xu 詩譜序.
    44. ^ A Hyatt Mayor, Prints and People, Metropolitan Museum of Art/Princeton, 1971, nos 1–4. ISBN 0-691-00326-2
    45. ^ “Chinese philosophy” Archived 2 May 2015 at the Wayback Machine, Encyclopædia Britannica, online
    46. ^ Lin, Liang-Hung; Ho, Yu-Ling (2009). “Confucian dynamism, culture and ethical changes in Chinese societies – a comparative study of China, Taiwan, and Hong Kong”. The International Journal of Human Resource Management. 20 (11): 2402–2417. doi:10.1080/09585190903239757. ISSN 0958-5192. S2CID 153789769. Archived from the original on 21 April 2021. Retrieved 21 October 2020.
    47. ^ see e.g. Radhakrishnan & Moore 1957, p. 3; Witzel, Michael, “Vedas and Upaniṣads“, in: Flood 2003, p. 68; MacDonell 2004, pp. 29–39; Sanskrit literature (2003) in Philip’s Encyclopedia. Accessed 2007-08-09
    48. ^ Sanujit Ghose (2011). “Religious Developments in Ancient India Archived 30 July 2022 at the Wayback Machine” in Ancient History Encyclopedia.
    49. ^ Gavin Flood sums up mainstream estimates, according to which the Rigveda was compiled from as early as 1500 BC over a period of several centuries. Flood 1996, p. 37
    50. ^ James G. Lochtefeld (2002). The Illustrated Encyclopedia of Hinduism: A-M. The Rosen Publishing Group. p. 399. ISBN 978-0-8239-3179-8. Archived from the original on 19 October 2020. Retrieved 21 October 2020.
    51. ^ T. R. S. Sharma; June Gaur; Sahitya Akademi (New Delhi, Inde). (2000). Ancient Indian Literature: An Anthology. Sahitya Akademi. p. 137. ISBN 978-81-260-0794-3. Archived from the original on 19 October 2020. Retrieved 21 October 2020.
    52. ^ “Ramayana | Summary, Characters, & Facts”. Encyclopedia Britannica. Archived from the original on 12 April 2020. Retrieved 18 February 2020.
    53. ^ Lutgendorf, Philip (1991). The Life of a Text. University of California Press. p. 1.
    54. ^ Chadwick, John (1967). The Decipherment of Linear B (Second ed.). Cambridge: Cambridge University Press. p. 101. ISBN 978-1-107-69176-6. “The glimpse we have suddenly been given of the account books of a long-forgotten people…”
    55. ^ Jump up to:a b c Ventris, Michael; Chadwick, John (1956). Documents in Mycenaean Greek. Cambridge: Cambridge University Press. p. xxix. ISBN 978-1-107-50341-0. Archived from the original on 14 April 2021. Retrieved 15 November 2020.
    56. ^ Croally, Neil; Hyde, Roy (2011). Classical Literature: An Introduction. Routledge. p. 26. ISBN 978-1136736629. Archived from the original on 10 August 2017. Retrieved 23 November 2016.
    57. ^ Wilson, Nigel (2013). Encyclopedia of Ancient Greece. Routledge. p. 366. ISBN 978-1136788000. Archived from the original on 10 August 2017. Retrieved 22 November 2016.
    58. ^ Romilly, Jacqueline de (1985). A Short History of Greek Literature. University of Chicago Press. p. 1. ISBN 978-0226143125. Archived from the original on 10 August 2017. Retrieved 22 November 2016.
    59. ^ Graziosi, Barbara (2002). Inventing Homer: The Early Reception of Epic. Cambridge University Press. p. 15. ISBN 978-0521809665. Archived from the original on 10 August 2017. Retrieved 22 November 2016.
    60. ^ Ahl, Frederick; Roisman, Hanna (1996). The Odyssey Re-formed. Cornell University Press. ISBN 978-0801483356. Archived from the original on 10 August 2017. Retrieved 23 November 2016.
    61. ^ Latacz, Joachim (1996). Homer, His Art and His World. University of Michigan Press. ISBN 978-0472083534. Archived from the original on 10 August 2017. Retrieved 22 November 2016.
    62. ^ Too, Yun Lee (2010). The Idea of the Library in the Ancient World. OUP Oxford. p. 86. ISBN 978-0199577804. Archived from the original on 5 August 2020. Retrieved 22 November 2016.
    63. ^ MacDonald, Dennis R. (1994). Christianizing Homer: The Odyssey, Plato, and the Acts of Andrew. Oxford University Press. p. 17. ISBN 978-0195358629. Archived from the original on 30 June 2017. Retrieved 22 November 2016.
    64. ^ Aristophanes: Butts K.J.Dover (ed), Oxford University Press 1970, Intro. p. x.
    65. ^ Frei 2001, p. 6.
    66. ^ Romer 2008, p. 2 and fn.3.
    67. ^ Riches, John (2000). The Bible: A Very Short Introduction. Oxford: Oxford University Press. p. 134. ISBN 978-0-19-285343-1.
    68. ^ Duckworth, George Eckel. The nature of Roman comedy: a study in popular entertainment. Archived 4 August 2020 at the Wayback Machine University of Oklahoma Press, 1994. p. 3. Web. 15 October 2011.
    69. ^ Donner, Fred (2010). Muhammad and the Believers: at the Origins of Islam. London: Harvard University Press. pp. 153–154. ISBN 978-0-674-05097-6.
    70. ^ “الوثائقية تفتح ملف “اللغة العربية””. الجزيرة الوثائقية (in Arabic). 8 September 2019. Archived from the original on 16 June 2022. Retrieved 18 June 2020.
    71. ^ “Western literature – Medieval literature”. Encyclopedia Britannica. Archived from the original on 29 April 2015. Retrieved 21 October 2020.
    72. ^ Elizabeth L. Eisenstein, The Printing Press as an Agent of Change. Cambridge University Press, 1980
    73. ^ Margaret Anne Doody, The True Story of the Novel. New Brunswick, NJ: Rutgers University Press, 1996, rept. 1997, p. 1. Retrieved 21 October 2020.
    74. ^ Polenz, Peter von. (1991). Deutsche Sprachgeschichte vom Spätmittelalter bis zur Gegenwart: I. Einführung, Grundbegriffe, Deutsch in der frühbürgerlichen Zeit (in German). New York/Berlin: Gruyter, Walter de GmbH.
    75. ^ Thomas Christensen (2007). “Did East Asian Printing Traditions Influence the European Renaissance?”. Arts of Asia Magazine (to appear). Retrieved 18 October 2006.
    76. ^ Thomas Franklin Carter, The Invention of Printing in China and its Spread Westward, The Ronald Press, NY 2nd ed. 1955, pp. 176–178
    77. ^ L. S. Stavrianos (1998) [1970]. A Global History: From Prehistory to the 21st Century (7th ed.). Upper Saddle River, New Jersey: Prentice Hall. ISBN 978-0-13-923897-0.
    78. ^ Clapham, Michael, “Printing” in A History of Technology, Vol 2. From the Renaissance to the Industrial Revolution, edd. Charles Singer et al. (Oxford 1957), p. 377. Cited from Elizabeth L. Eisenstein, The Printing Press as an Agent of Change (Cambridge University, 1980).
    79. ^ “Court: Institutionalizing English Literature”. oldsite.english.ucsb.edu. Archived from the original on 21 October 2020. Retrieved 20 October 2020.
    80. ^ “Women and Literature”. www.ibiblio.org. Archived from the original on 24 October 2020. Retrieved 23 October 2020.
    81. ^ Saturday Review. Saturday Review. 1876. pp. 771ff. Archived from the original on 1 August 2020. Retrieved 25 October 2020.
    82. ^ Hart, Kathleen (2004). Revolution and Women’s Autobiography in Nineteenth-century France. Rodopi. p. 91.
    83. ^ Lewis, Linda M. (2003). Germaine de Staël, George Sand, and the Victorian Woman Artist. University of Missouri Press. p. 48.
    84. ^ Eisler, Benita (8 June 2018). “‘George Sand’ Review: Monstre Sacré”. WSJ. Archived from the original on 23 September 2019. Retrieved 6 November 2018.
    85. ^ Thomson, Patricia (July 1972). “George Sand and English Reviewers: The First Twenty Years”. Modern Language Review. 67 (3): 501–516. doi:10.2307/3726119. JSTOR 3726119.
    86. ^ Forsas-Scott, Helena (1997). Swedish Women’s Writing 1850-1995. London: The Athlone Press. p. 63. ISBN 0485910039.
    87. ^ …remains the most translated Italian book and, after the Bible, the most widely read… by Francelia Butler, Children’s Literature, Yale University Press, 1972.
    88. ^ Nikolajeva, María, ed. (1995). Aspects and Issues in the History of Children’s Literature. Greenwood. ISBN 978-0-313-29614-7. Archived from the original on 27 July 2020. Retrieved 25 October 2020.
    89. ^ Lyons, Martyn. 2011. Books: a living history. Los Angeles: J. Paul Getty Museum.
    90. ^ Sullivan, Patrick (1 January 2002). “”Reception Moments,” Modern Literary Theory, and the Teaching of Literature”. Journal of Adolescent & Adult Literacy. 45 (7): 568–577. JSTOR 40012241.
    91. ^ Matthew Schneider-Mayerson, “Popular Fiction Studies: The Advantages of a New Field”. Studies in Popular Culture, Vol. 33, No. 1 (Fall 2010), pp. 21-3
    92. ^ Boyd, William. “A short history of the short story”. Archived from the original on 21 June 2018. Retrieved 17 April 2018.
    93. ^ “The Nobel Prize in Literature”. nobelprize.org. Archived from the original on 13 July 2019.
    94. ^ John Sutherland (13 October 2007). “Ink and Spit”. Guardian Unlimited Books. The Guardian. Archived from the original on 11 November 2007. Retrieved 13 October 2007.
    95. ^ Oebel, Guido (2001). So-called “Alternative FLL-Approaches”. Norderstedt: GRIN Verlag. ISBN 9783640187799. Archived from the original on 14 April 2021. Retrieved 15 November 2020.
    96. ^ Makin, Michael; Kelly, Catriona; Shepher, David; de Rambures, Dominique (1989). Discontinuous Discourses in Modern Russian Literature. New York: Palgrave Macmillan. p. 122. ISBN 978-1349198511.
    97. ^ Cullingford, Cedric (1998). Children’s Literature and its Effects. London: A&C Black. p. 5. ISBN 0304700924.
    98. ^ Hogan 2011, p. 10.
    99. ^ Hogan 2011, p. 11.
    100. ^ Damon, William; Lerner, Richard; Renninger, Ann; Sigel, Irving (2006). Handbook of Child Psychology, Child Psychology in Practice. Hoboken, NJ: John Wiley & Sons. p. 90. ISBN 0471272876.
    101. ^ Paris 1986, p. 61.
    102. ^ Paris 1986, p. 25.
    103. ^ Nezami, S.R.A. (February 2012). “The use of figures of speech as a literary device—a specific mode of expression in English literature”. Language in India. 12 (2): 659–.[dead link]
    104. ^ Riches, John (2022) [2000]. “The Bible in high and popular culture”. The Bible: a Very Short Introduction. Volume 14 in Very Short Introductions Series (2 ed.). Oxford: Oxford University Press (published 2021). p. 115. ISBN 978-0198863335. Archived from the original on 23 February 2022. Retrieved 23 February 2022. In its various translations, [the Bible] has had a formative influence on the language, the literature, the art, the music of all the major European and North American cultures. It continues to influence popular culture in films, novels, and music.
    105. ^ “Islamic arts – Islamic literatures”. Encyclopedia Britannica. Archived from the original on 22 June 2021. Retrieved 12 November 2020.
    106. ^ Riches, John (2000). The Bible: A Very Short Introduction. Oxford: Oxford University Press. p. 134. ISBN 978-0-19-285343-1.
    107. ^ “Hinduism – Vernacular literatures”. Encyclopedia Britannica. Archived from the original on 11 March 2022. Retrieved 12 November 2020.
    108. ^ “The King James Translation of the New Testament | Religious Studies Center”.
    109. ^ “When the King Saved God”. Vanity Fair. 2011. Archived from the original on 24 December 2020. Retrieved 10 August 2017.
    110. ^ “Why I want all our children to read the King James Bible”. The Guardian. 20 May 2012. Archived from the original on 29 November 2020. Retrieved 10 August 2017.
    111. ^ Jump up to:a b “poetry, n.” Oxford English Dictionary. OUP. Archived from the original on 30 June 2020. Retrieved 13 February 2014.(subscription required)
    112. ^ Jump up to:a b Preminger 1993, p. 938.
    113. ^ Jump up to:a b Preminger 1993, p. 939.
    114. ^ Preminger 1993, p. 981.
    115. ^ Preminger 1993, p. 979.
    116. ^ Lipsky, Abram (1908). “Rhythm in Prose”. The Sewanee Review. 16 (3): 277–289. JSTOR 27530906. (subscription required)
    117. ^ Ross, Trevor (1996). “The Emergence of “Literature”: Making and Reading the English Canon in the Eighteenth Century.”” (PDF). ELH. 63 (2): 398. doi:10.1353/elh.1996.0019. S2CID 170813833. Archived (PDF) from the original on 21 February 2014. Retrieved 9 February 2014.
    118. ^ Finnegan, Ruth H. (1977). Oral poetry: its nature, significance, and social context. Indiana University Press. p. 66.
    119. ^ Magoun, Francis P. Jr. (1953). “Oral-Formulaic Character of Anglo-Saxon Narrative Poetry”. Speculum. 28 (3): 446–467. doi:10.2307/2847021. JSTOR 2847021. S2CID 162903356. (subscription required)
    120. ^ Alison Booth; Kelly J. Mays. “Glossary: P”. LitWeb, the Norton Introduction to Literature Studyspace. Archived from the original on 18 March 2011. Retrieved 15 February 2014.
    121. ^ Eliot T.S. ‘Poetry & Prose: The Chapbook. Poetry Bookshop: London, 1921.
    122. ^ For discussion of the basic categorical issues see (Preminger 1993, “Narrative Poetry”).
    123. ^ Graff, Richard (2005). “Prose versus Poetry in Early Greek Theories of Style”. Rhetorica. 23 (4): 303–335. doi:10.1525/rh.2005.23.4.303. JSTOR 10.1525/rh.2005.23.4.303. S2CID 144730853. (subscription required)
    124. ^ “Literature”, Encyclopaedia Britannica. online
    125. ^ Sommerville, C. J. (1996). The News Revolution in England: Cultural Dynamics of Daily Information. Oxford: OUP. p. 18.
    126. ^ “Essay on Romance”, Prose Works volume vi, p. 129, quoted in “Introduction” to Walter Scott’s Quentin Durward, ed. Susan Maning. Oxford: Oxford University Press, 1992, p. xxv. Romance should not be confused with Harlequin Romance.
    127. ^ Doody (1996), p. 15.
    128. ^ Jump up to:a b “The Novel”. A Guide to the Study of Literature: A Companion Text for Core Studies 6, Landmarks of Literature. Brooklyn College. Archived from the original on 22 February 2014. Retrieved 22 February 2014.
    129. ^ Goody 2006, p. 19.
    130. ^ Goody 2006, p. 20.
    131. ^ Goody 2006, p. 29.
    132. ^ Franco Moretti, ed. (2006). “The Novel in Search of Itself: A Historical Morphology”. The Novel, Volume 2: Forms and Themes. Princeton: Princeton UP. p. 31. ISBN 978-0-691-04948-9.
    133. ^ Antrim, Taylor (2010). “In Praise of Short”. The Daily Beast. Archived from the original on 18 February 2014. Retrieved 15 February 2014.
    134. ^ “What’s the definition of a “novella,” “novelette,” etc.?”. Science Fiction and Fantasy Writers of America. Archived from the original on 19 March 2009.
    135. ^ Boyd, William. “A short history of the short story”. Prospect Magazine. Archived from the original on 3 July 2014. Retrieved 8 March 2014.
    136. ^ Colibaba, Ştefan (2010). “The Nature of the Short Story: Attempts at Definition” (PDF). Synergy. 6 (2): 220–230. Archived (PDF) from the original on 21 March 2014. Retrieved 6 March 2014.
    137. ^ Susan B. Neuman; Linda B. Gambrell, eds. (2013). Quality Reading Instruction in the Age of Common Core Standards. International Reading Association. p. 46. ISBN 978-0872074965. Archived from the original on 14 April 2021. Retrieved 18 October 2020.
    138. ^ Cuddon 1998, p. 472.
    139. ^ Elam, Kier (1980). The Semiotics of Theatre and Drama. London and New York: Methuen. p. 98. ISBN 978-0-416-72060-0.
    140. ^ Cody, Gabrielle H. (2007). The Columbia Encyclopedia of Modern Drama (Volume 1 ed.). New York City: Columbia University Press. p. 271.
    141. ^ “Definition of copyright”. Oxford Dictionaries. Archived from the original on 21 December 2018. Retrieved 20 December 2018.
    142. ^ “Definition of Copyright”. Merriam-Webster. Archived from the original on 21 December 2018. Retrieved 20 December 2018.
    143. ^ Nimmer on Copyright, vol. 2, § 8.01.
    144. ^ “Intellectual property”, Black’s Law Dictionary, 10th ed. (2014).
    145. ^ “Understanding Copyright and Related Rights” (PDF). www.wipo.int. p. 4. Archived (PDF) from the original on 27 December 2019. Retrieved 6 December 2018.
    146. ^ Stim, Rich (27 March 2013). “Copyright Basics FAQ”. The Center for Internet and Society Fair Use Project. Stanford University. Archived from the original on 11 June 2018. Retrieved 21 July 2019.
    147. ^ Daniel A. Tysver. “Works Unprotected by Copyright Law”. Bitlaw. Archived from the original on 2 March 2016. Retrieved 25 October 2020.
    148. ^ Lee A. Hollaar. “Legal Protection of Digital Information”. p. Chapter 1: An Overview of Copyright, Section II.E. Ideas Versus Expression. Archived from the original on 28 October 2020. Retrieved 25 October 2020.
    149. ^ The Statute of Anne 1710 and the Literary Copyright Act 1842 used the term “book”. However, since 1911 the statutes have referred to literary works.
    150. ^ “Copyright, Designs and Patents Act 1988”. legislation.gov.uk. Archived from the original on 29 October 2021. Retrieved 11 October 2021.
    151. ^ “University of London Press v. University Tutorial Press” [1916][full citation needed]
    152. ^ Agency for Cultural Affairs. 環太平洋パートナーシップ協定の法律） (PDF) (in Japanese). Agency for Cultural Affairs. Archived (PDF) from the original on 19 January 2021. Retrieved 4 January 2019.
    153. ^ Cuddon 1998, pp. 118–122, “Censorship”.
    154. ^ “About Banned & Challenged Books”. ala.org. 25 October 2016. Archived from the original on 8 April 2014. Retrieved 28 October 2020.
    155. ^ Nabokov, pp. 55, 57[full citation needed]
    156. ^ Ulysses has been called “the most prominent landmark in modernist literature”, a work where life’s complexities are depicted with “unprecedented, and unequalled, linguistic and stylistic virtuosity”. The New York Times guide to essential knowledge, 3d ed. (2011), p. 126.
    157. ^ John Stock; Kealey Rigden (15 October 2013). “Man Booker 2013: Top 25 literary prizes”. The Telegraph. Archived from the original on 15 October 2013. Retrieved 8 March 2014.
    158. ^ “Facts on the Nobel Prize in Literature”. Nobelprize.org. Nobel Media AB. Archived from the original on 8 March 2014. Retrieved 8 March 2014.

    Courses & Fees

    Fee Deposit

    Admission

    Online/Distance Learning

    About Us

    Brochure

    Investor-Relation

    Media Gallery

    Facebook Twitter Youtube Linkedin

    Privacy Policy

    Contact

    v-academy.in
    Course & Fees
    Fee Deposite
    Online/Distance Learning
    About Us
    © 2023 Created with v-academy.in
    Translate »
    × How can I help you?