Agile Project Management, Frameworks and Development Process

Apply the scaled agile framework (SAFe) to foster an agile organization across the enterprise, aligning business strategy with execution to deliver value on a regular and predictable cadence.

Identify five elements common to agile organizations. Apply them as a system: network of teams, people-centric culture, rapid learning, fast decision cycles, technology enablement, and create value for all stakeholders.

Aligns agile organizations around a shared purpose and vision, sensing opportunities, flexible resource allocation, channel strategy guidance, and continuous stakeholder feedback to create value for customers and partners.

Build flexible, networked organizational structure with autonomous, accountable performance cells and cross-functional teams. Empower self-managing teams, prioritize work, and sustain open partnerships, governance, ecosystem, and communities of practice.

Agile organizations pursue rapid decision and learning cycles, rapid iteration, and minimal viable products, shifting away from waterfall approaches to accelerate innovation, transparency, and continuous learning.

Empower people at the center of agile organizations by building cohesive communities, leadership that develops talent, and role mobility that fosters intrapreneurship, collaboration, and continuous skill growth.

Adopt next-generation technology and model-based software architecture to speed delivery. Coordinate cross-functional collaboration using tools, containers, cloud services, and automated testing to continuously develop, test, deploy, and release customer-centric products.

Transform organizations from machines into living organisms by aligning people, technology, and processes around end-to-end teams. Embrace agile, small cycles to balance stability with dynamism amid digital disruption and talent.

Explores softer development models and life cycle models, guiding how to select a model based on project goals and how the chosen model shapes testing scope, techniques, and timing.

Explore the software development lifecycle (SDLC), a structured process for delivering high-quality software through stages like planning, design, development, testing, deployment, and maintenance, with defined entry and exit criteria.

Explore the software development lifecycle phases, from requirements gathering and specification to design, coding, testing, deployment, and maintenance, and learn how model-driven approaches define each phase and its deliverables.

Explains the waterfall model, a sequential life cycle where each phase finishes before the next and testing occurs after development, making defect fixes costly, best suited for small, well-defined projects.

Explore the agile development model as an incremental, rapid-cycle approach delivering small, tested releases that build on prior functionality, emphasizing customer collaboration, frequent delivery, and adaptability.

Explore the agile methodology, emphasizing adaptive planning, early delivery, and continuous improvement through iterations, customer collaboration, and delivering working software.

Learn how Scrum, an agile project management framework, uses sprints, product backlog, and daily standups to deliver incremental value through collaboration and active stakeholder involvement.

Explains how Scrum rests on six principles forming its foundation, with transparency, inspection, self-organization, collaboration, value-based prioritization, and time boxing driving value.

Map the scrum organization from customer to product owner, scrum master, and scrum team, enabling value delivery through incremental releases and clear acceptance criteria in the spring review meeting.

Understand Scrum coaching, its role in guiding agile adoption, preventing impediments, and recognize the key traits of an effective coach who leads organizational change.

Learn scrum team size guidelines from four to nine, with ten plus for dependencies and multi-site development. Start with six to seven members for your first project to optimize collaboration.

Kanban emphasizes a pull-based, priority-driven workflow from to do to doing to done, with flexible roles and close collaboration to prevent bottlenecks. It encourages open communication and adaptability.

Explore kanban boards and how cards and columns visualize a team's workflow. Learn to apply work in progress limits, commitment points, delivery points, and continuous improvement to reduce lead time.

Explore kanban boards' five components: visual signals, work in progress limits, backlog, commitment point, and delivery point, to optimize flow, reduce lead time, and maximize efficiency.

Master work in progress limits (WIPA limits) in the Cambon framework, learning to set per-status limits, reveal bottlenecks, and accelerate value delivery through a balanced development flow.

Explore agile project management using scrum and the Campbell framework to manage software projects with sprints, backlogs, ceremonies, and work-in-progress limits for rapid, adaptable delivery.

Discover agile ceremonies derived from scrum that organize time-boxed sprints and iterations, including backlog grooming, sprint planning, daily stand-ups, reviews, and retrospectives.

Adopt agile programs by replacing waterfall with iterative development, testing, and releases; use roadmaps, initiatives, a product owner, and a prioritized backlog to enable rapid customer feedback and flexible delivery.

Design simple, scalable workflows for agile teams using defined statuses from to do to done, including review and definition of done, with WIP limits and Jira as a tool.

Explore how epics, stories, themes, initiatives, and teams organize agile work, from user stories and epics to initiatives that span multiple teams toward a common goal.

Explore epics as high-level design requirements, their executive summaries, and how they break into user stories to drive an agile roadmap, delivery, and key performance indicators.

Define user stories as the smallest agile task unit, building blocks of epics and initiatives, guiding sprints and backlog to deliver customer value.

Explore how initiatives sit above epics and organize teams around strategic priorities, with stories assigned to one team and metrics for estimating and allocating resources.

Master agile estimation with story points to measure relative effort, involve stakeholders about requirements and user stories, break down work, and prioritize the backlog for delivery.

Explore agile project metrics to track progress and forecast delivery, using burndown charts, velocity, control charts, and cumulative flow diagrams to deliver the right product on time for the market.

Measure velocity to predict sprint capacity and guide planning by using completed story estimates, track trend across sprints, and forecast workload for future releases.

Learn to use a velocity chart and velocity report to forecast release dates, plan backlog effort, and compute program velocity across sprints.

Understand how velocity forecasts sprint scope by date, and why incomplete stories are excluded. Learn to relate velocity to story points and use sprint averages for forecasting.

Learn how to estimate story points in an agile project. Use relative sizing and the fibonacci scale to assign baselines and relate points to velocity and task hours.

Master requirement gathering as a collaborative process with customers to collect business requirements through meetings, workshops, and documents, translating them into technical specifications and wireframes, with sign-off and change management.

Collect customer and business requirements through workshops to design an ecommerce platform with login, product views, search, cart, payments, and define architecture with templates for pc, laptops, tablets, and mobile.

Maps the user experience flow of an e-commerce app, from home page banners to login or anonymous PayPal checkout, and supports global search, deals of the day, and product listings.

Explore database architecture for an ecommerce app, outlining model choices for products, product options, categories, orders, customers, suppliers, stores, and inventory items.

Present a final ecommerce app design featuring home, registration, login, global search with results, product pages, cart, checkout, and user profiles.

Sign off on requirements anchors validation and traces defects to the original requirements, preventing scope creep through BRD sign-offs, change requests, and stakeholder approvals.

Prioritize the product backlog to align requirements with business value. The product owner and development team refine user stories, estimate effort with story points, and pull work for iterative delivery.

Refine the product backlog through backlog grooming to add stories and epics, define acceptance criteria, and estimate effort with the right team members, reducing uncertainty and speeding sprint planning.

Align agile projects with business value by linking user stories to revenue and costs, measuring value delivery through story points, and balancing investment with potential market and regulatory benefits.

Explore methods to measure value in agile projects, including cost-benefit ratio, return on investment, net present value, break-even point, and real options analysis.

Prioritize business value in user stories using net present value, time value of money, cash flow analysis, and return on investment to guide prioritization decisions.

Explore best practices for business value evaluation: release early to validate value with customers and involve stakeholders; use context-dependent metrics that evolve over time.

Learn to create user stories with templates, specify acceptance criteria, define done, and ensure readiness with database, registration, and login requirements.

Learn to write user stories with the 'as an actor, I want action, so that business value' template, define actors and actions, and discuss them on sticky notes.

Apply the invest criteria to write good user stories—independent, negotiable, valuable, estimable, small, and testable. Prioritize and break down stories, define done, and set acceptance criteria for testing.

Write user stories to capture expressed needs and prevent premature design lock-in. Break epics into smaller stories to support backlog negotiation and user-focused participatory design.

Organize the ecommerce app product backlog by translating customer requirements into detailed user stories with priority and sprint value, guided by wireframes and catalogs.

Define acceptance criteria for an e-commerce app's registration workflow by outlining user stories, mandatory fields, form validation, and data handling from registration to profile updates.

Split user stories for an e-commerce app into pages and functionalities, isolating areas like registration, profile information, and payment methods to clarify acceptance criteria and manage the backlog.

Identify and define acceptance criteria to validate user stories, setting boundaries, testable exit points, and business rules that guide delivery for product owners and stakeholders.

Learn to write acceptance criteria for user story, use a checklist to mark completion, while prototype specifies criteria, validates assumptions, and identifies issues in advance and corrects them on time.

Analyze user stories and acceptance criteria early to prevent discrepancies, reduce rework, and avoid waste and extra sprint time during development and testing.

Explore how acceptance criteria guide teams to envision user-facing behavior, remove ambiguity from requirements, and form tests that verify a feature is complete.

Explore acceptance criteria for a customer story about registering and purchasing online, including what information to collect, where it's stored, how payment is stored, and whether to send an acknowledgement.

Define testable acceptance criteria aligned with requirements and the definition of done. Ensure they are easy to test, unambiguous, and reflect the user perspective.

Define acceptance criteria for each backlog item or user story, written beforehand, independently testable, and focused on the end result, including functional criteria, verified by the product owner.

The product owner typically writes acceptance criteria and facilitates discussions. Developers and QAD representatives should contribute to capture customer needs, dependencies, and refine user stories through collaborative dialogue.

Define acceptance criteria before development begins to capture value without writing too early. Move a story into the sprint backlog to write acceptance criteria, then finalize during sprint planning.

Explore media types and structures for acceptance criteria, compare two common formats and a third self-designed option, and see how scenario, given-when-then rules, and rule-oriented checklists fit different agile contexts.

Learn to write acceptance criteria using given-when-then and scenario templates in agile project management. Include user stories, test scenarios, and examples like online registration and product search.

Define the definition of done for user stories as a team checklist applicable to all backlog items, ensuring acceptance criteria, quality, and a shippable product increment.

Differentiate the definition of done and acceptance criteria: the definition of done is a universal checklist for all stories, while acceptance criteria are story-specific test scenarios; both must be met.

Learn to define acceptance criteria for an e-commerce registration and login flow, covering mandatory fields, password formats, error messages, and email confirmation.

In this case study of an eCommerce app, the product backlog defines acceptance criteria for authentication flows, including login, registration, and profile view with encrypted data in the database.

This case study illustrates ecommerce app backlog acceptance criteria for search and category filtering, including dropdown category lists, a global search, and admin tools to populate categories.

Explore a case study of an eCommerce app product backlog, detailing problem page design, column layouts, descriptions, budgets, and acceptance criteria implementation.

A case study on an e-commerce app explains the product backlog and acceptance criteria, detailing database fields (title, subtitle, description, price) and features like search, cart, and quantity control.

Prioritize requirements in agile by structuring the backlog and ordering work to focus on the most strategically important features, balancing vision, urgency, and constraints.

Prioritize product backlog by mapping top items to the next sprint, maintain only level one and two priorities, and use a point system with a separate list for lower-priority ideas.

Apply stack ranking to order backlog items by priority, ranking each item relative to others. Use estimations and a systematic approach to assign clear absolutes like very high priority.

The Kano model categorizes backlog items into must-be, attractive, one-dimensional, indifferent, and reverse, guiding prioritization by balancing must-be requirements with attractive and one-dimensional features.

Prioritize the product backlog using the MoSCoW model by classifying items as must have, should have, could have, and would have; this clarifies guaranteed delivery, importance, and backlog deferral.

Compare the Kano model and the MoSCoW model, two prioritization frameworks that bucket features by need, then blend market-driven insights with must-haves for customer-friendly products.

Use the cost of delay model to quantify delay cost per time unit for each feature. Prioritize by delivering highest cost of delay first, via the shortest job first approach.

The technique number five introduces the relative weighting prioritization model, guiding product owners and agile teams to rank features by financial value and return on investment, considering cost and risk.

Discover how to prioritize backlog items with the priority poker model, where a moderator gathers product owners, designers, developers, experts, and users to score user stories with cards.

Define ecommerce app backlog priorities by ranking uploads, home page visibility, customer profiles, cart, checkout, and search by business value.