{"id":37579,"date":"2023-12-08T23:38:26","date_gmt":"2023-12-08T23:38:26","guid":{"rendered":"https:\/\/masterskills.org\/blog\/moi-kien-thuc-ve-pmi-acp.html"},"modified":"2023-12-10T05:43:49","modified_gmt":"2023-12-10T05:43:49","slug":"moi-kien-thuc-ve-pmi-acp","status":"publish","type":"post","link":"https:\/\/masterskills.org\/blog\/moi-kien-thuc-ve-pmi-acp.html","title":{"rendered":"M\u1eccI KI\u1ebeN TH\u1ee8C V\u1ec0 PMI-ACP"},"content":{"rendered":"<div class=\"article-body article-toc\">\n<h2 style=\"text-align: justify\"><span style=\"color:#333399\"><strong>Session 1: Agile Principles and Mindset<\/strong><\/span><\/h2>\n<ul style=\"text-align: justify\">\n<li style=\"font-weight: 400\">Agile frameworks and terminology<\/li>\n<li style=\"font-weight: 400\">Agile Manifesto\n<ul>\n<li style=\"font-weight: 400\">4 values<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ol style=\"text-align: justify\">\n<li style=\"font-weight: 400\"><strong>Individuals and interactions<\/strong> over processes and tools\u00a0<\/li>\n<li style=\"font-weight: 400\"><strong>Working software<\/strong> over comprehensive documentation<\/li>\n<li style=\"font-weight: 400\"><strong>Customer collaboration<\/strong> over contract negotiation<\/li>\n<li style=\"font-weight: 400\"><strong>Responding to change<\/strong> over following a plan<\/li>\n<\/ol>\n<p style=\"text-align: justify\">=&gt; If you don\u2019t follow the four Agile Manifesto values \u201c<strong>I<\/strong>t <strong>W<\/strong>ill <strong>C<\/strong>reate <strong>R<\/strong>isks\u201d<\/p>\n<ul style=\"text-align: justify\">\n<li>\n<ul>\n<li style=\"font-weight: 400\">12 principles<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ol style=\"text-align: justify\">\n<li style=\"font-weight: 400\">Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. <strong><em>[Customer Satisfaction]<\/em><\/strong><\/li>\n<li style=\"font-weight: 400\">Welcome changing requirements, even late in development. Agile processes harness change for the customer\u2019s competitive advantage. <strong><em>[Welcome Changes]<\/em><\/strong><\/li>\n<li style=\"font-weight: 400\">Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. <strong><em>[Frequently Delivery]<\/em><\/strong><\/li>\n<li style=\"font-weight: 400\">Business people and developers must work together daily throughout the project. <strong><em>[Collocated Teams] _ [work with business]<\/em><\/strong><\/li>\n<li style=\"font-weight: 400\">Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. <strong><em>[Motivated Individuals]<\/em><\/strong><\/li>\n<li style=\"font-weight: 400\">The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. <strong><em>[Face-to-face Contact]<\/em><\/strong><\/li>\n<li style=\"font-weight: 400\">Working software is the primary measure of progress. <strong><em>[Working Software]<\/em><\/strong><\/li>\n<li style=\"font-weight: 400\">Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant Masterskills indefinitely. <strong><em>[Constant Masterskills]<\/em><\/strong><\/li>\n<li style=\"font-weight: 400\">Continuous attention to technical excMasterskillsnce and good design enhances agility. <strong><em>[Continuous Attention]<\/em><\/strong><\/li>\n<li style=\"font-weight: 400\">Simplicity \u2014 the art of maximizing the amount of work not done \u2014 is essential. <strong><em>[Simplicity]<\/em><\/strong><\/li>\n<li style=\"font-weight: 400\">The best architectures, requirements, and designs emerge from self-organizing teams. <strong><em>[Self-Organization]<\/em><\/strong><\/li>\n<li style=\"font-weight: 400\">At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. <strong><em>[Regular Reflection]<\/em><\/strong><\/li>\n<\/ol>\n<p style=\"text-align: justify\">\u00a0<\/p>\n<ul style=\"text-align: justify\">\n<li style=\"font-weight: 400\">Agile methods and approaches:\u00a0\n<ul>\n<li style=\"font-weight: 400\">Scrum, XP, Kanban, FDD, DSDM, Agile UP<\/li>\n<li style=\"font-weight: 400\">Scaled Approach: Lean, Scrum of Scrums, LeSS, Disciplined Agile, SAFe, Crystal Methods<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Agile process overview<\/li>\n<li style=\"font-weight: 400\">Kanban\n<ul>\n<li style=\"font-weight: 400\">Five principles:\u00a0\n<ol>\n<li style=\"font-weight: 400\">Visualize the workflow,\u00a0<\/li>\n<li style=\"font-weight: 400\">Limit WIP (work in progress),\u00a0<\/li>\n<li style=\"font-weight: 400\">Manage flow,\u00a0<\/li>\n<li style=\"font-weight: 400\">Make process policies explicit,\u00a0<\/li>\n<li style=\"font-weight: 400\">Improve collaboratively<\/li>\n<\/ol>\n<\/li>\n<li style=\"font-weight: 400\">Pull system: move work through the development process, When it completes an item of work, it triggers a \u201cpull\u201d to bring in the next item they will work on.<\/li>\n<li style=\"font-weight: 400\">WIP limits: Capping the number of items that can be in a given state of progress. Once the limit at the top of a column is reached, no new items may be moved into that column until another item is moved out.<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Leadership practices and principles\n<ul>\n<li style=\"font-weight: 400\">Management vs. leadership: We can best amplify team productivity through a combination of management and leadership.\n<ol>\n<li style=\"font-weight: 400\">Tasks\/things vs People<\/li>\n<li style=\"font-weight: 400\">Control vs Empowerment<\/li>\n<li style=\"font-weight: 400\">Efficiency vs Effectiveness<\/li>\n<li style=\"font-weight: 400\">Doing things right vs Doing the right things<\/li>\n<li style=\"font-weight: 400\">Speed vs Direction<\/li>\n<li style=\"font-weight: 400\">Practices vs principles<\/li>\n<li style=\"font-weight: 400\">Command vs CommMasterskillstion<\/li>\n<\/ol>\n<\/li>\n<li style=\"font-weight: 400\">Servant leadership (4 duties):\n<ol>\n<li style=\"font-weight: 400\">Shield the team from interruptions<\/li>\n<li style=\"font-weight: 400\">Remove impediments to progress<\/li>\n<li style=\"font-weight: 400\">CommMasterskillste (and re-commMasterskillste) the project vision<\/li>\n<li style=\"font-weight: 400\">Carry Food and water<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Lean\n<ul>\n<li style=\"font-weight: 400\">7 Core concepts:\n<ol>\n<li style=\"font-weight: 400\">Eliminate waste<\/li>\n<li style=\"font-weight: 400\">Empower the team<\/li>\n<li style=\"font-weight: 400\">Deliver fast<\/li>\n<li style=\"font-weight: 400\">Optimize the whole<\/li>\n<li style=\"font-weight: 400\">Build quality in<\/li>\n<li style=\"font-weight: 400\">Defer decisions<\/li>\n<li style=\"font-weight: 400\">Amplify learning<\/li>\n<\/ol>\n<\/li>\n<li style=\"font-weight: 400\">7 wastes\n<ol>\n<li style=\"font-weight: 400\">Partially done work<\/li>\n<li style=\"font-weight: 400\">Extra processes<\/li>\n<li style=\"font-weight: 400\">Extra features<\/li>\n<li style=\"font-weight: 400\">Task switching<\/li>\n<li style=\"font-weight: 400\">Waiting<\/li>\n<li style=\"font-weight: 400\">Motion<\/li>\n<li style=\"font-weight: 400\">Defects<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Scrum\u00a0\n<ul>\n<li style=\"font-weight: 400\">3 Pillars:\n<ol>\n<li style=\"font-weight: 400\">Transparency<\/li>\n<li style=\"font-weight: 400\">Inspection<\/li>\n<li style=\"font-weight: 400\">Adaptation<\/li>\n<\/ol>\n<\/li>\n<li style=\"font-weight: 400\">Values\n<ol>\n<li style=\"font-weight: 400\">Openness<\/li>\n<li style=\"font-weight: 400\">Respect<\/li>\n<li style=\"font-weight: 400\">Courage<\/li>\n<li style=\"font-weight: 400\">Focus<\/li>\n<li style=\"font-weight: 400\">Commitment<\/li>\n<\/ol>\n<\/li>\n<li style=\"font-weight: 400\">Activities\n<ol>\n<li style=\"font-weight: 400\">Backlog Refinement<\/li>\n<li style=\"font-weight: 400\">Sprint Planning Meeting<\/li>\n<li style=\"font-weight: 400\">Daily Scrum<\/li>\n<li style=\"font-weight: 400\">Sprint Review<\/li>\n<li style=\"font-weight: 400\">Sprint Retrospective<\/li>\n<\/ol>\n<\/li>\n<li style=\"font-weight: 400\">Artifacts\u00a0\n<ol>\n<li style=\"font-weight: 400\">Product Increment<\/li>\n<li style=\"font-weight: 400\">Product Backlog<\/li>\n<li style=\"font-weight: 400\">Sprint Backlog<\/li>\n<\/ol>\n<\/li>\n<li style=\"font-weight: 400\">Team roles\n<ol>\n<li style=\"font-weight: 400\">Development Team<\/li>\n<li style=\"font-weight: 400\">Product Owner<\/li>\n<li style=\"font-weight: 400\">Scrum Master<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">XP\n<ul>\n<li style=\"font-weight: 400\">Core practices\u00a0\n<ol>\n<li style=\"font-weight: 400\">Whole Team<\/li>\n<li style=\"font-weight: 400\">Planning Games<\/li>\n<li style=\"font-weight: 400\">Small Releases<\/li>\n<li style=\"font-weight: 400\">Customer Tests<\/li>\n<li style=\"font-weight: 400\">Collective Code Ownership<\/li>\n<li style=\"font-weight: 400\">Code Standards<\/li>\n<li style=\"font-weight: 400\">Sustainable Masterskills<\/li>\n<li style=\"font-weight: 400\">Metaphor<\/li>\n<li style=\"font-weight: 400\">Continuous Integration<\/li>\n<li style=\"font-weight: 400\">Test-Driven Development<\/li>\n<li style=\"font-weight: 400\">Refactoring<\/li>\n<li style=\"font-weight: 400\">Simple Design<\/li>\n<li style=\"font-weight: 400\">Pair Programming<\/li>\n<\/ol>\n<\/li>\n<li style=\"font-weight: 400\">Core values\u00a0\n<ol>\n<li style=\"font-weight: 400\">Simplicity<\/li>\n<li style=\"font-weight: 400\">CommMasterskillstion<\/li>\n<li style=\"font-weight: 400\">Feedback<\/li>\n<li style=\"font-weight: 400\">Courage<\/li>\n<li style=\"font-weight: 400\">Respect<\/li>\n<\/ol>\n<\/li>\n<li style=\"font-weight: 400\">Team roles\n<ol>\n<li style=\"font-weight: 400\">Coach<\/li>\n<li style=\"font-weight: 400\">Customer<\/li>\n<li style=\"font-weight: 400\">Programmers<\/li>\n<li style=\"font-weight: 400\">Testers<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n<p style=\"text-align: justify\">\u00a0<\/p>\n<h2 style=\"text-align: justify\"><span style=\"color:#333399\"><strong>Session 2: Value-Driven Delivery<\/strong><\/span><\/h2>\n<ul style=\"text-align: justify\">\n<li style=\"font-weight: 400\">Agile contracting\n<ul>\n<li style=\"font-weight: 400\">Multi-tiered structure<\/li>\n<li style=\"font-weight: 400\">Emphasize value delivered<\/li>\n<li style=\"font-weight: 400\">Not-to-exceed time and materials<\/li>\n<li style=\"font-weight: 400\">Dynamic scope option<\/li>\n<li style=\"font-weight: 400\">Team augmentation<\/li>\n<li style=\"font-weight: 400\">Favor full-service suppliers<\/li>\n<li style=\"font-weight: 400\">Fixed-price increments.<\/li>\n<li style=\"font-weight: 400\">DSDM Contract<\/li>\n<li style=\"font-weight: 400\">Money for Nothing and Change for Free<\/li>\n<li style=\"font-weight: 400\">Graduated Fixed-Price Contract<\/li>\n<li style=\"font-weight: 400\">Fixed-Price Work Packages<\/li>\n<li style=\"font-weight: 400\">Customized Contracts<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Agile project accounting principles\u00a0<\/li>\n<li style=\"font-weight: 400\">Agile risk management:\n<ul>\n<li style=\"font-weight: 400\">Risk-adjusted backlog\u00a0<\/li>\n<li style=\"font-weight: 400\">Risk burndown charts<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Agile tooling: Low-Tech, High-Touch Tools<\/li>\n<li style=\"font-weight: 400\">Compliance\/regulatory compliance: is one instance of where \u201c<strong>just because<\/strong>\u201d comes into play.\n<ul>\n<li style=\"font-weight: 400\">Doing the compliance work <strong>\u201cas you go\u201d<\/strong><\/li>\n<li style=\"font-weight: 400\">Doing the compliance work <strong>after product development<\/strong><\/li>\n<li style=\"font-weight: 400\"><strong>Hybrid approach<\/strong><\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Cumulative flow diagrams (CFDs): <strong>tracking <\/strong>and <strong>forecasting <\/strong>the <strong>delivery of value<\/strong>.<\/li>\n<li style=\"font-weight: 400\">Little\u2019s Law: The more WIP and the longer cycle times we have on the project, the higher the amount of potential scrap.<\/li>\n<li style=\"font-weight: 400\">Customer-valued prioritization: working on the items that <strong>yield the highest value to the customer first<\/strong>.\u00a0<\/li>\n<li style=\"font-weight: 400\">Earned value management (EVM) for agile projects\n<ul>\n<li style=\"font-weight: 400\">Projected progress, Planned value (PV), Planned features<\/li>\n<li style=\"font-weight: 400\">Scope built, Earned value (EV), Completed features<\/li>\n<li style=\"font-weight: 400\">Planned cost, Projected spending<\/li>\n<li style=\"font-weight: 400\">Actual cost (AC), Actual spending<\/li>\n<li style=\"font-weight: 400\">Schedule variance (SV) = EV &#8211; PV<\/li>\n<li style=\"font-weight: 400\">Cost variance (CV) = EV &#8211; AC<\/li>\n<li style=\"font-weight: 400\">SPI = Completed features \/ Planned features<\/li>\n<li style=\"font-weight: 400\">CPI = Earned value \/ Actual cost<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Frequent verification and validation: Agile uses regular testing, checkpoints, and reviews to address problems before they get bigger.\n<ul>\n<li style=\"font-weight: 400\">Gulf of evaluation: What one person describes is often very different from how the listener interprets it.<\/li>\n<li style=\"font-weight: 400\">Pair programming<\/li>\n<li style=\"font-weight: 400\">Unit test<\/li>\n<li style=\"font-weight: 400\">Customer collaboration<\/li>\n<li style=\"font-weight: 400\">Stand-up meetings<\/li>\n<li style=\"font-weight: 400\">Acceptance test<\/li>\n<li style=\"font-weight: 400\">Iteration demo<\/li>\n<li style=\"font-weight: 400\">Release<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Incremental delivery: deliver the \u201cplain-vanilla\u201d version to get an early return on investment.<\/li>\n<li style=\"font-weight: 400\">Managing with agile KPIs:\n<ul>\n<li style=\"font-weight: 400\">Rate of progress.<\/li>\n<li style=\"font-weight: 400\">Remaining work.<\/li>\n<li style=\"font-weight: 400\">Likely completion date.<\/li>\n<li style=\"font-weight: 400\">Likely costs remaining.<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Minimal viable product (MVP): package of functionality that is <strong>complete enough to be useful to the users or the market<\/strong>, yet <strong>still small enough that it does not represent the entire project<\/strong>.<\/li>\n<li style=\"font-weight: 400\">Minimal marketable feature (MMF)\u00a0<\/li>\n<li style=\"font-weight: 400\">Prioritization schemes\u00a0\n<ul>\n<li style=\"font-weight: 400\">Simple Schemes: \u201cPriority 1,\u201d \u201c Priority 2,\u201d \u201c Priority 3,\u201d. \u201c high,\u201d \u201cmedium,\u201d and \u201c low\u201d<\/li>\n<li style=\"font-weight: 400\">Kano analysis: Delighters\/exciters, Satisfiers, Dissatisfiers, Indifferent<\/li>\n<li style=\"font-weight: 400\">MoSCoW: <strong>M<\/strong>ust have, <strong>S<\/strong>hould have, <strong>C<\/strong>ould have, <strong>W<\/strong>ould like to have<\/li>\n<li style=\"font-weight: 400\">Monopoly Money: <strong>distribute funds <\/strong>amongst the system features, <strong>prioritizing business features<\/strong>.<\/li>\n<li style=\"font-weight: 400\">100-Point Method: each stakeholder is given 100 points, distribute the 100 points in any way.<\/li>\n<li style=\"font-weight: 400\">Dot Voting or Multi-Voting: Each stakeholder is<strong> limited to a total of dots<\/strong> to distribute as they wish.<\/li>\n<li style=\"font-weight: 400\">Requirements Prioritization Model:\u00a0 the <strong>benefit<\/strong>, <strong>penalty<\/strong>, <strong>cost<\/strong>, and <strong>risk <\/strong>of every proposed feature is rated on a relative scale of <strong>1 (lowest) to 9 (highest)<\/strong>.<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Relative prioritization\/ranking: A single prioritized list of work-to-be-done.<\/li>\n<li style=\"font-weight: 400\">ROI\/NPV\/IRR\n<ul>\n<li style=\"font-weight: 400\">Return on Investment (ROI): measures the profitability of an investment by calculating the ratio of the benefits received from the investment to the money invested in it.<\/li>\n<li style=\"font-weight: 400\">Present Value: Present value is a way of calculating the value of a future amount in today&#8217;s terms, given an assumed interest rate and inflation rate.<\/li>\n<li style=\"font-weight: 400\">Net Present Value (NPV): The present value of a revenue stream (income minus costs) over a series of time periods.<\/li>\n<li style=\"font-weight: 400\">Internal Rate of Return (IRR): The discount rate at which the project inflows (revenues) and project outflows (costs) are equal.<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Software development practices\u00a0\n<ul>\n<li style=\"font-weight: 400\">Continuous Integration: developers to frequently incorporate new and changed code into their project code repository.\u00a0<\/li>\n<li style=\"font-weight: 400\">Exploratory testing: find edge cases, system boundaries, and unanticipated behavior<\/li>\n<li style=\"font-weight: 400\">Usability testing: observing users as they interact with the system for the first time.<\/li>\n<li style=\"font-weight: 400\">Red, Green, Refactor: The process of writing a test that initially fails, adding code until the test passes, and then refactoring the code.<\/li>\n<li style=\"font-weight: 400\">TDD\/TFD: Tests should be written before the code is written.<\/li>\n<li style=\"font-weight: 400\">ATDD: Moves the testing focus from the code to the business requirement.<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Task\/Kanban boards: a whiteboard with columns that show various stages of work.<\/li>\n<li style=\"font-weight: 400\">Value-driven delivery: One of the key ways agile teams try to maximize value is by delivering value early.\u00a0<\/li>\n<li style=\"font-weight: 400\">Work in progress (WIP): work that has been started but has not yet been completed.\u00a0\n<ul>\n<li style=\"font-weight: 400\">WIP <strong>consumes investment capital and delivers no return<\/strong> <strong>on the investment<\/strong><\/li>\n<li style=\"font-weight: 400\"><strong>WIP hides bottlenecks<\/strong> in processes<\/li>\n<li style=\"font-weight: 400\"><strong>WIP represents risk in the form of potential rework<\/strong><\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">WIP limits: <strong>restrict the amount of work in the system<\/strong> and help <strong>ensure that WIP limits are not exceeded<\/strong>.\n<ul>\n<li style=\"font-weight: 400\">Identify bottlenecks and Remove bottlenecks<\/li>\n<li style=\"font-weight: 400\">Reduce the risks of tied-up capital, rework, and waste<\/li>\n<li style=\"font-weight: 400\">Optimize throughput of work, not to optimize resource utilization.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p style=\"text-align: justify\">\u00a0<\/p>\n<h2 style=\"text-align: justify\"><span style=\"color:#333399\"><strong>Session 3: Stakeholder Engagement<\/strong><\/span><\/h2>\n<ul style=\"text-align: justify\">\n<li style=\"font-weight: 400\">Active listening\u00a0<\/li>\n<li style=\"font-weight: 400\">Agile chartering\u00a0<\/li>\n<li style=\"font-weight: 400\">Agile modeling\u00a0<\/li>\n<li style=\"font-weight: 400\">Assessing and incorporating community and stakeholder values\u00a0<\/li>\n<li style=\"font-weight: 400\">Brainstorming Collaboration\n<ul>\n<li style=\"font-weight: 400\">Collaboration games\u00a0<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">CommMasterskillstion management\u00a0\n<ul>\n<li style=\"font-weight: 400\">Face-to-face (F2F)\u00a0<\/li>\n<li style=\"font-weight: 400\">Social media\u00a0<\/li>\n<li style=\"font-weight: 400\">Two-way (trustworthy,conversation-driven)<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Conflict resolution\u00a0\n<ul>\n<li style=\"font-weight: 400\">Levels of conflict\u00a0<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Definition of &#8220;done&#8221;\u00a0<\/li>\n<li style=\"font-weight: 400\">Emotional intelligence\u00a0<\/li>\n<li style=\"font-weight: 400\">Facilitation\u00a0<\/li>\n<li style=\"font-weight: 400\">Information radiators\u00a0<\/li>\n<li style=\"font-weight: 400\">Knowledge sharing\/written commMasterskillstion commMasterskillstion<\/li>\n<li style=\"font-weight: 400\">Negotiation<\/li>\n<li style=\"font-weight: 400\">Participatory decision models (convergent, shared collaboration)\u00a0\n<ul>\n<li style=\"font-weight: 400\">Decision spectrum\u00a0<\/li>\n<li style=\"font-weight: 400\">Fist-of-five voting\u00a0<\/li>\n<li style=\"font-weight: 400\">Simple voting\u00a0<\/li>\n<li style=\"font-weight: 400\">Thumbs up\/down\/sideways\u00a0<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Personas\u00a0<\/li>\n<li style=\"font-weight: 400\">Stakeholder management (stewardship)\u00a0<\/li>\n<li style=\"font-weight: 400\">Wireframes\u00a0\u00a0<\/li>\n<li style=\"font-weight: 400\">Workshops<\/li>\n<\/ul>\n<p style=\"text-align: justify\">\u00a0<\/p>\n<h2 style=\"text-align: justify\"><span style=\"color:#333399\"><strong>Session 4: Team Performance<\/strong><\/span><\/h2>\n<ul style=\"text-align: justify\">\n<li style=\"font-weight: 400\">Adaptive leadership\u00a0<\/li>\n<li style=\"font-weight: 400\">Agile team roles\u00a0<\/li>\n<li style=\"font-weight: 400\">Building agile teams\u00a0\n<ul>\n<li style=\"font-weight: 400\">Self-directing\u00a0<\/li>\n<li style=\"font-weight: 400\">Self-organizing\u00a0<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Burndown\/burnup charts\u00a0<\/li>\n<li style=\"font-weight: 400\">Caves and common\u00a0<\/li>\n<li style=\"font-weight: 400\">Co-location (physical and virtual)<\/li>\n<li style=\"font-weight: 400\">Developmental mastery models\u00a0\n<ul>\n<li style=\"font-weight: 400\">Dreyfus (skill acquisition)\u00a0<\/li>\n<li style=\"font-weight: 400\">Shu-Ha-Ri (mastery)\u00a0<\/li>\n<li style=\"font-weight: 400\">Tuckman (team formation)\u00a0<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Global, cultural, and team diversity\u00a0<\/li>\n<li style=\"font-weight: 400\">Osmotic commMasterskillstion\u00a0\n<ul>\n<li style=\"font-weight: 400\">Co-located teams (proximity)\u00a0<\/li>\n<li style=\"font-weight: 400\">Distributed teams (digital tools)<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Tacit knowledge\u00a0<\/li>\n<li style=\"font-weight: 400\">Team motivation\u00a0<\/li>\n<li style=\"font-weight: 400\">Team sMasterskills\u00a0<\/li>\n<li style=\"font-weight: 400\">Training, coaching, and mentoring\u00a0\n<ul>\n<li style=\"font-weight: 400\">Individual vs. team coaching\u00a0<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Velocity<\/li>\n<\/ul>\n<p style=\"text-align: justify\">\u00a0<\/p>\n<h2 style=\"text-align: justify\"><span style=\"color:#333399\"><strong>Session 5: Adaptive Planning<\/strong><\/span><\/h2>\n<ul style=\"text-align: justify\">\n<li style=\"font-weight: 400\">Affinity estimating\u00a0<\/li>\n<li style=\"font-weight: 400\">Agile discovery\u00a0<\/li>\n<li style=\"font-weight: 400\">Agile sizing and estimating techniques\u00a0<\/li>\n<li style=\"font-weight: 400\">Daily stand-ups\u00a0\n<ul>\n<li style=\"font-weight: 400\">Ground rules\u00a0<\/li>\n<li style=\"font-weight: 400\">Three Questions\u00a0<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Defining and testing acceptance criteria\u00a0<\/li>\n<li style=\"font-weight: 400\">Estimating initial velocity\u00a0<\/li>\n<li style=\"font-weight: 400\">Estimating tasks\u00a0<\/li>\n<li style=\"font-weight: 400\">Fast failure<\/li>\n<li style=\"font-weight: 400\">Ideal time\u00a0<\/li>\n<li style=\"font-weight: 400\">Iteration planning process\u00a0<\/li>\n<li style=\"font-weight: 400\">Planning poker\u00a0<\/li>\n<li style=\"font-weight: 400\">Product roadmap\u00a0<\/li>\n<li style=\"font-weight: 400\">Progressive elaboration\u00a0<\/li>\n<li style=\"font-weight: 400\">Relative sizing\u00a0<\/li>\n<li style=\"font-weight: 400\">Release planning process<\/li>\n<li style=\"font-weight: 400\">Rolling wave planning\u00a0<\/li>\n<li style=\"font-weight: 400\">Slicing stories\u00a0<\/li>\n<li style=\"font-weight: 400\">Spikes\u00a0\n<ul>\n<li style=\"font-weight: 400\">Architectural spike\u00a0<\/li>\n<li style=\"font-weight: 400\">Risk-based spike<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Story maps\u00a0<\/li>\n<li style=\"font-weight: 400\">Story points\u00a0<\/li>\n<li style=\"font-weight: 400\">Timeboxing\u00a0<\/li>\n<li style=\"font-weight: 400\">T-shirt sizing\u00a0<\/li>\n<li style=\"font-weight: 400\">User stories\u00a0<\/li>\n<li style=\"font-weight: 400\">User story backlog\u00a0\n<ul>\n<li style=\"font-weight: 400\">Refining (grooming) the backlog\u00a0<\/li>\n<li style=\"font-weight: 400\">Requirements reviews\u00a0<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Value-based analysis and decomposition\u00a0<\/li>\n<li style=\"font-weight: 400\">Wideband Delphi<\/li>\n<\/ul>\n<p style=\"text-align: justify\">\u00a0<\/p>\n<h2 style=\"text-align: justify\"><span style=\"color:#333399\"><strong>Session 6: Problem Detection and Resolution<\/strong><\/span><\/h2>\n<ul style=\"text-align: justify\">\n<li style=\"font-weight: 400\">Control limits\u00a0<\/li>\n<li style=\"font-weight: 400\">Cost of change\u00a0<\/li>\n<li style=\"font-weight: 400\">Cycle time\u00a0<\/li>\n<li style=\"font-weight: 400\">Defect rate\u00a0<\/li>\n<li style=\"font-weight: 400\">Escaped defects\u00a0<\/li>\n<li style=\"font-weight: 400\">Expected monetary value\u00a0<\/li>\n<li style=\"font-weight: 400\">Failure and success modes\u00a0<\/li>\n<li style=\"font-weight: 400\">Lead time<\/li>\n<li style=\"font-weight: 400\">Problem Solving\u00a0\n<ul>\n<li style=\"font-weight: 400\">As continuous improvement\u00a0<\/li>\n<li style=\"font-weight: 400\">Team-based\u00a0<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Risk-adjusted backlog\u00a0<\/li>\n<li style=\"font-weight: 400\">Risk burndown graphs\u00a0<\/li>\n<li style=\"font-weight: 400\">Risk severity\u00a0<\/li>\n<li style=\"font-weight: 400\">Technical debt\u00a0<\/li>\n<li style=\"font-weight: 400\">Throughput\/productivity<\/li>\n<li style=\"font-weight: 400\">Trend analysis\u00a0\n<ul>\n<li style=\"font-weight: 400\">Lagging metrics\u00a0<\/li>\n<li style=\"font-weight: 400\">Leading metrics\u00a0<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400\">Variance analysis\u00a0\n<ul>\n<li style=\"font-weight: 400\">Common cause\u00a0<\/li>\n<li style=\"font-weight: 400\">Special cause<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p style=\"text-align: justify\">\u00a0<\/p>\n<h2 style=\"text-align: justify\"><span style=\"color:#333399\"><strong>Session 7: Continuous Improvement<\/strong><\/span><\/h2>\n<ul>\n<li style=\"font-weight: 400;text-align: justify\">Agile hybrid models\u00a0<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Approved iterations\u00a0<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Continuous improvement\u00a0<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Feedback methods\u00a0<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Fishbone Analysis\u00a0<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Five Whys\u00a0<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Kaizen\u00a0<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Learning cycle\u00a0<\/li>\n<li style=\"font-weight: 400;text-align: justify\">PMI\u2019s Code of Ethics and Professional Conduct<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Process analysis\u00a0\n<ul style=\"text-align: justify\">\n<li style=\"font-weight: 400\">Anti-patterns\u00a0<\/li>\n<li style=\"font-weight: 400\">Success criteria\u00a0<\/li>\n<li style=\"font-weight: 400\">Success patterns\u00a0<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Process tailoring\u00a0\n<ul style=\"text-align: justify\">\n<li style=\"font-weight: 400\">Risks\u00a0<\/li>\n<li style=\"font-weight: 400\">Recommendations\u00a0<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Product feedback loop\u00a0<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Project pre-mortems (kh\u00e1m nghi\u1ec7m)<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Retrospectives (intraspectives)\u00a0\n<ul style=\"text-align: justify\">\n<li style=\"font-weight: 400\">Five-step process\u00a0<\/li>\n<li style=\"font-weight: 400\">Three problem-solving steps<\/li>\n<\/ul>\n<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Reviews\u00a0<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Self-assessment tools and techniques\u00a0<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Systems thinking\u00a0<\/li>\n<li style=\"font-weight: 400;text-align: justify\">Value stream mapping\u00a0\n<ul>\n<li style=\"font-weight: 400\">Non value-added time<\/li>\n<li style=\"font-weight: 400\">Process cycle efficiency\u00a0<\/li>\n<li style=\"font-weight: 400\">Total cycle time\u00a0<\/li>\n<li style=\"font-weight: 400\">Value-added time<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul>\n<li style=\"font-weight: 400;list-style-type: none\">\n<ul>\n<li style=\"list-style-type: none\">\n<ul>\n<li style=\"list-style-type: none;text-align: justify\">\u00a0<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Session 1: Agile Principles and Mindset Agile frameworks and terminology Agile Manifesto 4 values Individuals and interactions over processes and tools\u00a0 Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan =&gt; If you don\u2019t follow the four Agile Manifesto values \u201cIt Will Create Risks\u201d 12 principles Our [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[250],"tags":[],"_links":{"self":[{"href":"https:\/\/masterskills.org\/blog\/wp-json\/wp\/v2\/posts\/37579"}],"collection":[{"href":"https:\/\/masterskills.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/masterskills.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/masterskills.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/masterskills.org\/blog\/wp-json\/wp\/v2\/comments?post=37579"}],"version-history":[{"count":0,"href":"https:\/\/masterskills.org\/blog\/wp-json\/wp\/v2\/posts\/37579\/revisions"}],"wp:attachment":[{"href":"https:\/\/masterskills.org\/blog\/wp-json\/wp\/v2\/media?parent=37579"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/masterskills.org\/blog\/wp-json\/wp\/v2\/categories?post=37579"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/masterskills.org\/blog\/wp-json\/wp\/v2\/tags?post=37579"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}