Tag Archives: Waterfall

Agile Manifesto – Personal Reflection

Individuals and Interactions over Process and Tools

Stereotypical software developers are introverts, heads down, coding. Articulating where they are in the development lifecycle sometimes heavily relies upon tools for measuring progress such as JIRA, Product Backlog status of User Stories, e.g. “In Progress” with an Effort estimation of 3.

“Blocked” User Stories may require the implementation team to “break out of their shell” and work with their teammates to “unblock” Product Backlog items. It breaks people out of their comfort zone. We need to discuss options and opportunities for removing blockers. “All for One, and One for all”

Working Product over Comprehensive Documentation

Over a decade or so ago, the measure of my merit was the complete test coverage of requirements for software implementation. Back then I was a QA lead, and my focus was to make sure all use cases for the software under development had complete test coverage.

Requirements changes from our business through our business analysts must be vetted with the QA team so use cases/test cases must be updated to ensure coverage. Sometimes a dependency of one requirement had a ripple effect throughout the software, so lots of documentation updates were required. Milestone dates were in many cases fixed, so teams were squeezed to do more with less time.

Flash forward to today, and leveraging Agile principles, I breathe a slight sigh of relief. Iterating product delivery via sprints every 2 weeks is supremely better than attempting to traverse updates to Business Requirements Documents (BRD), and technical specs. User Stories in a Backlog are much more succinct, and in some cases, a bit more abstract leaving functionality open to some level of ambiguity and interpretation.

Sprint Close scrum ceremonies every two weeks with our Product Owner, the central mouthpiece for the definition of the software product helps define the path forward. Did we get it right? Where do we need to make changes? There is no substitute for an evolving product and accompanying dialog with our Product Owner.

Customer Collaboration over Contract Negotiation

Both sides of the aisle seem to agree, building a solution with iterative input from the customer enables the product vision to be realized far better than without frequent touchpoints.

Statements of Work (SoW) to engage 3rd party solutions integrators (SI) may be abstract in some way. Holding vendors accountable for loosely formed requirements is tenuous at best. Quibbling about he said, she said is a waste of time.

Fail fast, engage regularly and often with our [Business] Product Owner enables us to collaborate on a working solution. The focus is on the evolving product vision and not the paper trail.

Responding to Change over Following a Plan

A “last-minute” change request? It could push back our timelines and accompanying milestones. Dates can’t change, and teams need to absorb the changes, i.e. nights and weekends. Responding to incremental changes at a regular cadence is a sustainable life cycle.

Agile’s Watergate

A relic of the Waterfall model is the construct of a “gate” process. In order for a project to achieve a milestone, the project/solution would need to achieve certain criteria that would allow it to go to the next phase of the project. For example, going from solidifying requirements in a Business Requirements Doc (BRD) to the software implementation phase.

In Agile, we leverage the Product Owner (PO) and the Product Backlog to determine what gets done and when. A Product Backlog item (PBI) may cover the full lifecycle of a Feature, from requirements to implementation. The Product Owner dictates acceptance of the PBI based on the status/transparency of the Backlog, such as the criticality of the Bugs linked to the PBI. Product quality and implemented functionality are transparent to the PO, who will determine the next steps such as release the software, and/or go through another iteration/sprint. Iterations are a defined cadence agreed to by the implementation team and the Product owner, typically, 2-week sprints.

Agile, Hybrid Environments: Opportunities for Synergy

Epics, Features, Product Backlog Items, and Tasks are object types in a Backlog that enable the PO and the team to link objects and plan over multiple sprints. Epics or Themes of Sprints are “high level”, potentially strategic initiatives. Features roll up into Epics as a part of several sprints. Either Epics or Features may be high enough level to link to Psydo Project Milestones for a product roadmap of deliverables, and solicitation outside the team.

Aggregation of Product Backlog Items, Effort Estimations, roll up into Features, and then up into Epics, which roughly equate to milestone timelines.

The “Definition of Done” (DoD) for a Product Backlog Item may require 0 outstanding Bugs with the severity of “Critical” linked to this PBI. The DoD criteria could be analogous to a traditional Quality Assurance gate.

Tasks that are production rollout activities, without a project plan, should be planned for in future sprints, akin to estimating when items may be completed in the proper sequence. Some of the Tasks may be placed conservatively in “early” sprints and may require items to be “pushed forward” after each of the iterations.

When Stakeholders Collide

Requirements Expedition

Maybe you’ll meet them during the Project Kickoff. Maybe you’ll first hear from them during a biweekly Steering Committee. Or maybe you will first hear from them three months into the project at a quarterly meeting with the CIO and the rest of his portfolio. Maybe you will never hear from them directly.

The politics of requirements gathering and prioritization is a daunting process. I’m not going to drudge up all the stories and categorize them here because it’s a painful process.

Why are some of your milestones in your project plan:

• the milestone exists within someone’s year end evaluation

• the requirements of a milestone are so bipolar, they are bound to fail. Need a project to bucket the requirements to say “we tried”, and we can pin it to a project.

• backing into established project timelines based on expectations set at the highest levels, e.g. regulatory compliance

Legal and Compliance Stakeholders

Global representation of legal and compliance requirements are a dichotomy of legal precedence between jurisdictions.

Agile Product Owner verse Waterfall Stakeholder Committee(s)

Many a project managed using waterfall kept me balancing the needs and wants of Stakeholders from all walks of life, some exuberantly voicing their opinions regardless of their position of power, or lack therein. The Agile Product Owner (PO) is a relief of burden, a single mouthpiece of the business, which dictates backlog priority.

Does Agile make the requirements gathering and prioritization pain go away? Possibly. There are various implementations of Agile, hybrid situations, and there are lots of tools out there to help manage the Product Backlog (requirements). Another exercise, developing User Journeys, working with your Personas / actors to derive their story, that is telling and lots of fun.

Continuing Certification Requirements for Project Management Professional (PMP)

The years seem to have flown by, and it’s that time again to complete my Continuing Certification Requirements for my PMP cert.

I randomly searched the web for PMP courses, then found myself back at PMI.org “Searching Activities”.  Seems like the easiest way to lookup activities because they define the activities, and the correlated list of Professional Development Units, categorized by:

  • Technical
  • Leadership
  • Strategic & Business

Based on the activities I’ve already completed, my majority of work has been accomplished in the Technical category.  I need to focus on attaining Leadership and Strategic & Business categories.

PMP 2019 Continuing Certification Requirements
PMP 2019 Continuing Certification Requirements

Here are a few activities I thought were interesting, and took each one of these Online or Digital Media courses.  Pluralsight provides an excellent set of courses at a relatively low price.  I highly recommend Pluralsight for your learning needs.  I also took a few of the LinkedIn courses and found it to be an excellent learning platform with a wide array of courses that can be applied as PDU credits.

Customizing Your Team Workflow with the Best of Kanban and Scrum

If you have doubts choosing which methodology to use, this course will give you a comparison of Kanban and Scrum, making your choice easier. By watching this course you will learn how to take the best of both, Scrum and Kanban, and how to make a winning combination for your team and project.

Leadership: 1.25

Crisis Communication and Technology: Communicating with Colleagues

Crisis communication is one of the most challenging communication types an organization or individual can face, bringing together emotional vulnerability, ethical challenges, and high-stakes decisions amplified by informational and persuasive goals. When managed well, this communication can neutralize and calm an evolving crisis. When managed poorly, though, crisis communication makes a situation worse. This course takes viewers through the most important parts of preparing for crisis communication, including understanding crisis types and strategies, preparing foundational documents, and how to create communication in the moment. By the end of the course, viewers will have a concrete understanding of how to manage crisis communication for their own organizations, providing invaluable insight and immediate benefit.

Leadership: 1.50

Scrum Master Fundamentals – Growing Yourself and Your Team

Are you a Scrum Master ready to advance your craft? This course will teach you specific strategies for coaching each member of your team and show you how to build on your experience as a Scrum Master to advance your own career to the next level.

Leadership: 1.25

Product Owner Fundamentals – Foundations of Product Ownership

Did you know that one of the most common reasons Scrum Teams fail is the lack of a skilled Product Owner? If you’ve suddenly found yourself in this role, this course will teach you how you can use the role to help your team deliver a great product.

Technical: 0.75   Strategic & Business: 0.50

PMI-ACP®: Value-driven Delivery and Adaptive Planning (3 of 11)

This course will provide an in-depth understanding of Agile adaptive planning and value-driven delivery practices, requirements definition practices, as well as principles and practices related to stakeholder management. This course is part of the PMI-ACP Agile Project Management series.

Technical:  0.75  Strategic & Business: 1.75

Design Thinking: Lead Change in your Organization

Design thinking is a user-centered way of solving problems. It involves extensive collaboration, using strategies such as mapping customer journeys, concept creation, and prototyping. This course teaches leaders how to help their teams adopt a design thinking mindset, and provides examples from author Turi McKinley’s work at frog, a global design and strategy firm that transforms businesses at scale by creating systems of brand, product, and service.

Leadership: 2.00

Organizational Change Management for the ITIL® Practitioner

Organizational change management is as essential skill for all leaders. This course will teach you how to successfully navigate the people side of change.

Leadership: 1.50