Can someone explain what all this is about, going from projects to products?
8 replies (most recent on top)
The OP is probably asking the question from an infrastructure perspective, not a developer perspective.
I'll speak for Network Engineering as I worked in that field in the past.
Network Engineering is inherently waterfall. All parts must be working day 1. You can't have a prod network without a BCP network either.
Think of building a new neighborhood. The new houses aren't liveable if the connections to the sewer main won't be available until a future sprint. No tenant would move in until the infrastructure is fully in place.
There may be some value in tracking status as the infrastructure is built out. But there is no value for the tenants until it is all completed.
Same thing, different name.
Allegedly the product owner is supposed to be from the business but WF doesn’t let the business control what development does here as they should.
We never used to write a line of code without a user review, and our systems never broke. Imagine that.
It's just the latest shiny management fad. Something for the pretty hair and golf club set to talk about.
It won't change anyones job at all, and it'll go away, like all the other fads before it.
You HAVE heard of Google, right? Google it.
When done correctly (not how Wells Fargo does it) the Agile approach to delivering a minimum viable product (MVP) means you deliver the basic features and functionality through short bursts of coding (sprints) and this allows your users or customers to review and validate functionality. Then the user or customer provides feedback to add additional features in the next iteration. Unfortunately the brilliant minds in Mortgage Credit policy leadership have zero idea about agile because they don't follow it, therefore when you deliver the first iteration and its not 100% perfect, they call it a defect and raise all kind of suspicion from their higher ups. Then they spend 99% of their time focused on the very low 1% or less of "defects" that aren't really defects --- they are just an early, unperfected iteration of the requirements which were provided by people talking in non-specific generalities and they expect you can read their minds.
WF is never going to learn and will never be fully successful at scaling Agile.
Why has this board become about everything but layoffs? Talk to your manager or search on Teamworks.
Are you saying that you own the product
After the “project” is complete?
agile