Clone Baseline - Requirements Management
Clone Baseline - Requirements Management
OpenRose - Requirements Management
An Open Source and FREE Requirements Management Application / Tool
Direct Link to YouTube Video : https://www.youtube.com/watch?v=mBbspg6X5hk
Video Transcript :
Hi, welcome to OpenRose, a free and open-source requirements management application. Find more information at https://github.com/openrose. Today we are going to talk about cloning baselines.
Let's first go to the project "Bay St" for the personal customer project and expand the project to see all its data. Currently, we have the first requirement "What's covered by the Tariff," traced down to "Eligibility for Premier Banking," which is also traced further down to "Premier Current Account," which is inside "Borrowing from Us." The Premier Current Account also has a parent link to a Parking Lot item, which is "Bas Mortgage Arrangement Fees." This is something Bas is looking into, but it's not yet completely defined and approved, which is why it is sitting inside the Parking Lot. When I jump over to it, we can see this requirement is sitting in the Parking Lot. This particular requirement is also connected not only to the Premier Customer Account but also to the Student Account or Student Editions. This Student Edition is nothing but a requirement set in "Borrowing from Us."
When it comes to the Premier Current Account, we can see that the eligibility for Premier Banking is that the customer should have a gross annual income of £75,000, or they should have a balance of £100,000 in their saving accounts. These are the structure of data and the traceability in the current project.
Now, let's take the first snapshot. Let's go to the Baseline inside the project and create the snapshot for the whole project. When I create the snapshot for the whole project, all the data that you see here will be included in the snapshot. Let's say this is the January 2025 snapshot, and here is the description for the January 2025 snapshot. Let's create this snapshot, and you can now see all this data is part of my snapshot, which is inside my Baseline preview. I can see all that data.
Because Barley's Mortgage Arrangement Fee is in the Parking Lot, we are not going to deliver this as part of the January 2025 snapshot, so we will exclude it from the list. This means the Premier Current Account, which had traceability to Bas Mortgage Arrangement Fee, is not visible anymore because we have de-scoped that requirement. The same would be the case for the Student Editions, where you can see that the Mortgage Arrangement Fee is not visible as traceability.
Let's say we started to deliver against the set of requirements classified as January 2025. We're coming to the end of the month, and we figure out that certain business environment and decisions have changed in terms of how we want to deliver service to our customers. In that case, what we want to do is take the second snapshot, but not from the current live project. We don't want to go back to the project where requirements might have changed, traceability might have changed, it might have evolved further to capture new requirements, and it might have changed the structure, descriptions, or data. Requirements are fluid; they keep changing depending on market needs, our service, our product, our team's decisions, our funding, and our availability of skill set to deliver against the requirement. The project requirement may change further, but we do have a snapshot of January 2025, which was taken in the past.
In that case, we can go over to our Baselines, where we can see the January Baseline itself. We can say, "I want to clone the existing Baseline," which means I want to take another copy but not from the live project. Rather, I want to take it from a previously taken snapshot. When I select "Clone Existing Baseline," I have a list of existing Baselines here. Let's call this "February 2025 Snapshot" with the description "February 2025 Snapshot."
When I create a clone of an existing snapshot and go inside the clone, all the decisions we had taken for January 2025 up to this point will also be carried forward into February 2025. What I mean is, the Parking Lot Mortgage Arrangement Fees, which was excluded, will remain excluded. This decision taken in January 2025 is now carried forward into the February 2025 snapshot. When you look at the Premier Current Account, again, the traceability to Mortgage Arrangement Fees will not be visible. The same applies to the Student Editions, where traceability to something excluded from the Baseline is not visible.
We can make further decisions for February 2025. Let's say we are not going to include this particular requirement for February 2025, so I'm going to exclude that. This is the difference between January and February snapshots; it can evolve independently. Now, we can see under "Eligibility for Premier Banking," the link to the excluded requirement "Premier Current Account" is not visible anymore because this particular requirement has been excluded.
You can take a snapshot of the snapshot to allow further changes based on the changes in the business environment and the circumstances for the product and services you are delivering as part of the next snapshot. In this example, I used months like January and February to represent different phases of deliveries and changes in terms of inclusion and exclusion of requirements, which is putting requirements in scope or out of scope for particular deliveries.
The same can be done if you are taking a snapshot by item type. Let's consider a scenario where we have Barclays Bank, a large organization, with separate departments for debit card-related activities, loans and mortgages, borrowing from Barclays, investment banking, savings, and many other products. They want to take a snapshot of a particular area or item type worked upon by a particular department. In that case, I can go into "Borrowing from Us," which is an item type, and take a snapshot for that borrowing aspect. Create a snapshot by item type and select "Borrowing from Us." This is "Loans January 2025," with the description "Loans for January 2025." Let's create a specific snapshot mainly for the loans department or borrowing department.
Then, go inside the Treeview. We can only see "Borrowing from Us" data. I can go ahead and include or exclude items as required. Then, I can go back to my project. In the project details, we have the "Borrowing from Us" or "Loans January 2025" snapshot, and we can clone that further. In February, we will call this "Loans February 2025" based on January 2025, with the description "Loans February 2025." Let's create that snapshot. Now, I can go ahead in this snapshot and decide to include items that were excluded or exclude items that were included in the past. Now, my February and January snapshots are evolving independently, considering that the loans department or borrowing department within Barclays Bank will work on delivering these requirements. These are fine-grained, elicited, and well-defined requirements that they are supposed to work on.
This is an example of how we can use OpenRose to capture baselines and create baselines based on existing baselines. Any decisions that the team or users have taken during the baseline that was already taken as a snapshot, while executing or negotiating the delivery against that snapshot, will be carried forward in the next snapshot if it is created based on the previous snapshot or Baseline. You can make further changes in terms of inclusions and exclusions of subsequent snapshot data.
With that, I would like to thank you for attending this session and watching this video. Thanks a lot and have a great day! Bye-bye.
Document Ref:
Comments
Post a Comment