D359 Study Guide Review Notes, Study Guides, Projects, Research of Human Resource Management

Download D359 Study Guide Review Notes and more Study Guides, Projects, Research Human Resource Management in PDF only on Docsity!

D359 Study Guide Review Notes

([email protected]) Competency 1: Explains Agile HR (Chapters 1-6) Chapter 1 Question Your Notes

1. How does Agile help HR deliver value? Enhancing Flexibility : Agile HR practices make HR functions more responsive to changes in the business environment. This ensures that HR can quickly adapt to new challenges and opportunities, providing timely support to the organization. Improving Collaboration : By fostering cross- functional teamwork, Agile HR encourages collaboration across departments, leading to more integrated and effective solutions. Increasing Employee Engagement : Agile HR focuses on continuous feedback, regular check- ins, and involving employees in decision- making, which boosts engagement and satisfaction. Driving Continuous Improvement : Agile methodologies promote a culture of ongoing improvement, where HR processes are regularly reviewed and refined based on feedback and performance data. Aligning with Business Goals : Agile HR ensures that HR initiatives are closely aligned with the strategic objectives of the organization, enhancing overall business performance.
2. What is a human-centric approach? Employee Well-being : Prioritizing the health, happiness, and well-being of employees, ensuring they have the support they need to

([email protected])

1. How does Agile HR change the traditional operating model? Shifting from Hierarchical to Collaborative Structures : Traditional HR models often rely on rigid hierarchies. Agile HR promotes flat structures and cross-functional teams that collaborate closely. Focusing on Iterative Processes : Instead of long-term planning and inflexible processes, Agile HR uses short cycles and iterative improvements to adapt quickly to changes. Emphasizing Continuous Feedback : Traditional models may rely on annual reviews. Agile HR emphasizes regular, real-time feedback to continuously improve performance. Enhancing Employee Empowerment : Agile HR gives employees more autonomy and involvement in decision-making, fostering a sense of ownership and accountability. Integrating Technology : Agile HR leverages modern HR technologies to streamline processes, enhance data-driven decision- making, and improve overall efficiency.

([email protected])

1. What is the difference between Agile for HR and HR for Agile? Agile for HR : This refers to applying Agile methodologies to HR practices. It means transforming traditional HR functions (like recruitment, performance management, and learning and development) using Agile principles such as flexibility, collaboration, and continuous improvement. HR for Agile : This refers to HR’s role in supporting and facilitating an Agile transformation across the entire organization. It involves HR developing strategies, policies, and practices that enable and sustain Agile ways of working, such as fostering an Agile culture, supporting Agile leadership, and providing Agile training and resources. Chapter 2 Concept Your Notes

([email protected])

1. What impact has digitalization had on HR? Streamlined Recruitment : Digital platforms and tools facilitate more efficient recruitment processes, including job postings, applicant tracking, and automated resume screening. Enhanced Employee Experience : Digital HR solutions improve the employee experience through self-service portals, mobile access to HR services, and personalized communication. Data-Driven HR Decisions : Digital tools provide HR with the ability to collect and analyze employee data, leading to more informed decisions regarding talent management, employee engagement, and performance. Improved Learning and Development : E- learning platforms and digital training tools enable personalized and flexible learning opportunities for employees, supporting continuous development. Efficient Performance Management : Digital performance management systems enable continuous feedback, goal tracking, and performance reviews, making the process more transparent and effective. Better Compliance and Reporting : Digital tools ensure compliance with legal requirements and streamline Chapter 3 Question Your Notes

([email protected])

1. What is the waterfall approach to projects? The waterfall approach to projects is a linear and sequential project management method. It involves completing one phase of a project before moving on to the next, with each phase being dependent on the completion of the previous one. Typical phases include requirement analysis, design, implementation, testing, deployment, and maintenance. This approach is characterized by its structured, methodical progression and comprehensive documentation at each stage
2. Give an example of when the waterfall approach can be beneficial to HR. The waterfall approach can be beneficial to HR in situations where requirements are well- understood and unlikely to change. For example, implementing a new payroll system with clearly defined requirements, regulatory compliance needs, and a fixed timeline can benefit from the structured and detailed planning that the waterfall approach provides. This ensures that each phase, such as requirements gathering, system design, development, testing, and deployment, is thoroughly completed before moving on to the next.

([email protected]) iteratively, respond to changing needs, and focus on delivering value quickly and efficiently.

1. Who created Agile? Agile was created by a group of seventeen software developers who met in February 2001 at the Snowbird resort in Utah. This group included prominent figures such as Kent Beck, Robert C. Martin, and Martin Fowler. They came together to discuss new ways of developing software and collectively created the Agile Manifesto.
2. What is the Agile Manifesto? The Agile Manifesto is a foundational document for Agile methodologies, outlining key values and principles for Agile software development. It consists of four core values and twelve principles aimed at improving the efficiency and effectiveness of software development. The values prioritize: -Individuals and interactions over processes and

([email protected])

1. How do the Agile principles relate to the Agile mindset? The Agile principles provide a practical framework for embodying the Agile mindset in day-to-day work. They emphasize: Customer Satisfaction : Delivering valuable software frequently to ensure customer satisfaction. Embracing Change : Welcoming changing requirements, even late in development, to provide a competitive advantage. Continuous Delivery : Delivering working software frequently, with a preference for shorter timescales. Collaboration : Ensuring close, daily cooperation between business people and developers. Motivation and Trust : Building projects around motivated individuals, giving them the environment and support they need, and trusting them to get the job done. Face-to-Face Conversation : Encouraging face-to-face communication as the most efficient and effective method of conveying information. Working Software : Considering working software as the primary measure of progress. Sustainable Development : Promoting sustainable Chapter 4 Concept (^) Your Notes

Downloaded by jackson muthiga

1. What is the purpose of the business challenge step? The purpose of the business challenge step is to clearly define the problem or opportunity that needs to be addressed. This step involves understanding the context, setting objectives, and aligning the team on the goals of the project. It helps to ensure that everyone is focused on solving the right problem and achieving the desired outcomes.
2. Describe one of the tools used in the empathize step and how it can used effectively. One of the tools used in the empathize step is user interviews. User interviews involve speaking directly with users to understand their experiences, needs, and pain points. To use this tool effectively: Prepare open-ended questions that encourage users to share their thoughts and feelings. Create a comfortable environment where users feel safe to speak openly. Listen actively and empathetically, without interrupting or leading the conversation. Record the interviews for later analysis to identify common themes and insights.
3. What type of data is analyzed in the categorize step? In the categorize step, qualitative data collected during the empathize step is analyzed. This includes observations, interview transcripts, user stories, and feedback. The goal is to identify patterns, themes, and insights that can inform the next steps in the design thinking process.
4. What is the deliverable of the define step? The deliverable of the define step is a clear and concise problem statement or design challenge.

Downloaded by jackson muthiga This statement outlines the specific problem to be solved, the target users, and the criteria for a successful solution. It serves as a guiding reference for the ideation and prototyping phases.

1. Is it better to pilot or prototype? Both piloting and prototyping have their benefits, but in the context of design thinking and Agile HR, prototyping is often preferred. Prototyping allows for quick and cost-effective creation of tangible models or mock-ups of the proposed solutions. It facilitates early testing and feedback, enabling iterative refinement before investing in a full-scale pilot.
2. What obstacles must be overcome in the test step? In the test step, the following obstacles must be overcome: User Resistance : Users may be hesitant to try new solutions. Resource Constraints : Limited time, budget, or materials for testing. Incomplete Feedback : Ensuring feedback is comprehensive and representative. Technical Issues : Addressing any technical
3. Define Minimum Viable Product (MVP). A Minimum Viable Product (MVP) is a version of a product with the minimum features necessary to meet the needs of early adopters and provide feedback for future development. The MVP allows teams to validate assumptions, learn from real user interactions, and iteratively improve the product based on user

Downloaded by jackson muthiga

1. What questions might you consider in creating Agile development teams? What skills and expertise are needed to achieve our project goals? How can we ensure a diverse mix of perspectives and experiences? How will team members communicate and collaborate effectively? What roles and responsibilities will each team member have? How can we foster a culture of trust, openness, and continuous improvement?
2. What is a backlog? Why is it important? A backlog is a prioritized list of work items, features, tasks, or bugs that need to be addressed by the Agile team. It is important because it provides a clear and organized overview of the work that needs to be done, helping the team stay focused on delivering value. The backlog also enables efficient planning, tracking progress, and ensuring that the most important tasks are completed first.
3. How can release planning benefit the team? Release planning benefits the team by providing a roadmap for delivering increments of the product over time. It helps the team set realistic goals, manage expectations, and coordinate efforts across different sprints. Release planning also ensures that stakeholders are kept informed about progress and can provide feedback, allowing for adjustments and improvements to be made as needed. The Definition of Done (DoD) ensures that all completed work meets a consistent and agreed-

([email protected])

1. What does the Definition of Done (DoD) ensure? upon standard of quality. It defines the criteria that a backlog item must satisfy before it can be considered "done," including aspects such as testing, documentation, and acceptance by stakeholders. The DoD helps maintain high quality and prevents incomplete or substandard work from being released. Backlog refinement, also known as backlog grooming, is the process of continuously reviewing and updating the backlog. During refinement, the team: Clarifies and elaborates on backlog items. Prioritizes items based on their value and urgency. Estimates the effort

([email protected])

1. Describe the purpose of a Retrospective or retro. at the end of each sprint or iteration to reflect on the team's performance. The purpose of the retrospective is to: Identify what went well and should be continued. Discuss challenges and areas for improvement. Develop action plans to enhance future performance. Retrospectives foster a culture of continuous learning and help the team adapt and improve their processes over time. Closing an Agile project does not necessarily mean that all backlog items have been marked done. It means that the project has achieved its primary goals and deliverables, and any

([email protected])

1. Explain the 3-5-3 Rule. The 3-5-3 rule in Scrum refers to the framework's structure: 3 Roles: Scrum Master, Product Owner, and Development Team. 5 Events: Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. 3 Artifacts: Product Backlog, Sprint Backlog, and Increment.
2. What are the 3 Scrum roles? Scrum Master : Facilitates the Scrum process, helps remove obstacles, and ensures the team follows Agile practices. Product Owner : Represents the stakeholders and customers, manages the Product Backlog, and prioritizes tasks based on business value. Development Team : A cross-functional group that works on delivering the product increment within the Sprint.