Welcome to our Seilevel Photo Op.
Do we have good requirements? I hear that question asked all the time as I work with our various customers. Many organizations are looking to measure whether or not they have good requirements. Researchers are working on new methods to measure the quality of requirements. Unfortunately, both groups are trying …
In my time at Seilevel, I’ve had a chance to work with a number of different clients, operating in a range of industries. Oftentimes, these clients begin projects with a number of legacy systems that need updated or integrated with; it is a rare opportunity for a project team to …
Don Reinersten, in the Principles of Product Development Flow: Second Generation Lean Product Development, describes a mechanism called Weighted Shortest Job First for prioritizing work. You can read more about the method in the Scaled Agile Framework’s abstract, but the idea itself is simple and sensible. You use economic theory …
Managing a Product Backlog when there is only one development team in an organization creating one solution at a time is relatively straight forward. However, large enterprises have multiple development teams creating a multitude of solutions with interdependencies between them. Managing product backlogs in these situations becomes very tricky, especially …
“You don’t tell the market what you are selling, the market tells you what it will buy” – I talk to a lot of people about starting businesses and a lot of them still think that a comprehensive business plan that takes months to develop is a key component to …
The Business Objective Model (BOM) is one of the foundational models we use as part of the Seilevel requirements methodology. The BOM defines the rationale for doing a project. Every BOM has the following key component parts. 1. Problems – the business problems to be solved or addressed 2. Objectives …
Projects with clearly defined business objectives can and do fail even if they deliver functionality that syncs closely with the business objectives defined for the project, but do not meet user expectations. This may seem counter intuitive at first blush since the primary purpose of any enterprise software development effort …
One of the projects I’ve been working on over the past year has been particularity challenging; it’s one of those everything that can go wrong does go wrong projects. This is a back office product which automates a process updating data records. The updates are transactional. We were almost done …
I am on the opinion that there is a clear difference between overall project success and the performance of the IT team associated with the project. You can find my detailed discussion on this viewpoint here. Given that there is a fundamental dichotomy in the outcomes between the related and …
I attended BA World – Atlanta a few weeks back, and attended a wonderful presentation by Paul Mulvey, “Why Should a Business Analyst Care About Essential Processes?” Paul started off his session with a story about his daughter, and how she asked for a new iPhone. His first question was …
