Get Started

I have been involved in a project for last 4-6 weeks and the requirements are still not nailed down. The project involves integrating a vendor software to our current applications. The product is supposed to solve certain business use case and requirements are coupled based on the product capabilities .

Being an agile project everyone from technical teams, architects, and business are involved in designing the user story. Since everyone is involved, architecture flow is not getting blessed. Every time the architect designs the flow, business or the tech leads have their own version of how the product capabilities should be merged.
I feel sorry for the architect and product owners. Their project is getting delayed unnecessarily.
Strong leads and product owners are very much required when running an agile project. In every project there are some known and some unknown or ambiguities.
Take those to separate discussions or parking lot and resolve those.
Create the user stories for what is agreed on and get the project going. Waiting for resolving all things will never get the project developed on time.
Another thing I am seeing that is missing is meeting face to face and white boarding. If a requirement are not finalized in couple of meetings, book half a day or whole day meeting and make it mandatory for key stakeholders to attend, then nail it down. Management does not want to pay for lunch or travel, they are missing the point. When a product release is postponed by a quarter, management has lost lot more in terms of revenue

Comments

Post a Comment

Popular posts from this blog

Customer Obsession's for an Architect

 As an Architects I am always solving problems on everyday basis, little do I get a chance to think about this topic. Let's come to the basics who is the customer for the architect. If I am working on the website, it easy to identify. If I am UX person, I am already there. But who is the customer for an architect. Most times I am working on the internals like a mechanic and no one gets to see what has gone on the inside. Like any projects there are many stakeholders, so for the architect, it is business or the product owner, then comes the technology team and there are other like project sponsor, project manager, etc. Most importantly the product is for someone or to solve some use case. I think that is the most important customer, the final user or the system that is going to be using it. This where the obsession needs to be. I am currently working on a new user case that is going to implement a feature called ZRF, will add more details when the products is live. This feature does...
Read more

System Architecture Role

 Having been a systems architect for last four years, I feel I can talk about being an architects better now, than I could 4 years back. Before being an architect, I admired the documents, the artifacts and  the diagrams they created, honestly I was intimidated by it. Now after 4+ years, I feel that is the easiest thing to do as an architect. I have put some of my thought together, and these are somethings that have worked for me. Architect I feel is just a liaison between the business team and the technology team, well, the statement seems too simple, it does get complicated as you dive deeper. For someone to be a good architect, most important thing is to understand the business requirement and also be technically competent.  If you are in sync with the product owner or the analyst, 90% of the battle is won. The product owner wants to build an application, they have a release date, the product goal, and the budget. Now the architect has to make it happen based on it....
Read more

Passing AWS Cloud Practitioner

 I passed the AWS Cloud Practitioner exam 3 weeks, back I should I written a blog about it as soon as it got done. Better late than never. My goal was always to get AWS Solution Architect Associate, but it seemed too ambitious. I was not serious about it for a while, then last year Las Positas College was providing a cloud computing course. It was broken into 4 course, first 2 course was catered towards practitioner and next 2 towards Solution Architect Associate. This Spring, the next 2 courses did not happen for whatever reason. I was kind of stuck now, so I decided to focus on Practitioner. First to prepare, I wanted to get a book that would provide the exact curriculum with reading material. I just cannot focus 100% when the recorded video is on. So I reached out to my professor in Las Positas Debbie Fields and she suggested "AWS Certified Cloud Practitioner Study Guide" by Ben Piper and David Clinton, It is a Sybex publisher.  Then I signed up for some practice tests Ude...
Read more