Requirements

This category contains 27 posts

Empathy, Mapping Customer Job Stories, and Business Modeling

It’s been some time since I wrote about customer job stories and the connection to empathy maps and solution design (initial post here), so I thought I would revisit this topic and provide more context. In the beginning. . . Empathy. Always. Not only at the start, but through every stage. There are multiple ways … Continue reading

When focusing on Minimum Viable Product is the wrong thing to do #Agile #MVP

There isn’t too many things more sacred than Minimum Viable Product in the Agile circles. Maybe Planning Poker, Automated Testing, and Continuous Integration. But usually Minimum Viable Product is also right up there. What if I told you that focusing on Minimum Viable Product is sometimes the wrong thing to do? Would I be branded … Continue reading

Birth of #Agile #Agile2014

Reading through all of the Agile 2014 tweets, my memory flipped back to my university years where I consider the seeds of Agile were sown. Although I am sure people at that time didn’t think that was the CASE. (pun intended) I was taking my Advanced System Analysis course and the final chapter was on … Continue reading

#1 skill for #agile and #traditional project team members – “Enough-ness Sense” #pmot #baot

I’ve had the good fortune on being on small, medium, and large traditional and agile teams. As I’ve worked on Agile teams recently, I’ve come to realize that both types of teams require one non-technical skill above all others. (In my humble opinion) Interestingly enough, this skill is required on both traditional and agile projects … Continue reading

When is a plan good enough? Provisional Project Planning

As I’ve taken the journey along the Agile path I’ve come to learn two things I am certain about: 1) A detailed Work Breakdown Structure is one of the largest wastes and mistakes that can exist in a project 2) That not creating a temporal plan at some level can also lead to rework and … Continue reading

#Agile Enterprise Data Model – #holistic and #iterative

I’ve recently been working on a Data Warehouse project that I am trying to do in an Agile way. Unlike Agile Software Development, Agile Data projects have some complexities that cause you to adapt the common Agile methods and practices. I am a big fan of User Story Mapping and creating a User Story Map … Continue reading

Top 10 practices for estimating Agile projects successfully

I’ve had multiple posts in the past that provided my passionate opinion on why I believe we should estimate Agile projects. (Both from the perspective of the client and the team) But rather than get into that discussion once again, I thought it would be more valuable if I shared the 10 practices that we … Continue reading

#Agile’s Sub-Optimal Value Stream

As I review proposals from people in the Agile community to push the boundaries of Agile, I believe that Agile is in danger of becoming more and more Sub-Optimal. Before I proceed, let me just review my definition of Optimal and Sub-Optimal Systems: “An Optimal system is a system where the optimization of the system … Continue reading

My #Agile #Pretotype experience

Two months ago I was introduced to the concept of Pretotyping. If I remember correctly, the introduction was through an excellent InfoQ article. The concept and practice intrigued me and I was able to apply it to a project I was working on recently. This is a recap of that experience in the hopes that … Continue reading

#Agile Product Management vs. #Agile Project Management

I think the time has come where the Agile proponents (myself included) need to be very clear on whether they are speaking from an Agile Product Management or Agile Project Management point of view. Some of the more controversial posts on Agile Practices seem to be aligned very well with Agile Product Management, but perhaps … Continue reading