Unfortunately “iteration” is the biggest lie of most agile teams. In practice very little iteration happens. Instead another waitress gets thrown onto the conveyor belt. Often as a result of pressure from the business.
-
Prikaži ovu nit
-
Ironically developers often hate having to ditch features or do rework. However because very little upfront thinking has happened, and because this is the big lie of agile, PMs end up getting the “blame” for changing things.
0 proslijeđenih tweetova 17 korisnika označava da im se sviđaPrikaži ovu nit -
PMs find themselves in the tough situation of having to explain to the business what the business is getting and when, without having done the necessary upfront thinking/planning. With no true product vision, things understandably change more than they could.
0 proslijeđenih tweetova 15 korisnika označava da im se sviđaPrikaži ovu nit -
Designers are frustrated with product because they’re not allowed to think about things deeply in advance. Developers are frustrated with product because things keep changing and product are therefore at fault.
3 proslijeđena tweeta 25 korisnika označava da im se sviđaPrikaži ovu nit -
While product managers are sat in the middle being beaten up by both sides, and then having to go back to “the business” to explain why their scope, time and cost estimates were wildly off. I’m glad I’m not a PM.
1 reply 0 proslijeđenih tweetova 16 korisnika označava da im se sviđaPrikaži ovu nit -
Product management is seriously the hardest job in tech. When things go right designers, developers and business people take the credit. When things go wrong, those problems are laid at the feet of the product managers.
3 proslijeđena tweeta 28 korisnika označava da im se sviđaPrikaži ovu nit -
However anytime somebody puts their hands up and says “I wonder if the process we’re using could be contributing to this problem” they get beat down by agile zealots, which doesn’t seem very “agile” to me.
0 proslijeđenih tweetova 20 korisnika označava da im se sviđaPrikaži ovu nit -
Not every problem can or should be broken down to fit the largely arbitrary length of a typical agile sprint. Agile projects need to properly embrace iteration rather than just giving it lip service.
1 reply 0 proslijeđenih tweetova 21 korisnik označava da mu se sviđaPrikaži ovu nit -
Ultimately Agile is a great process for delivery but struggles with discovery. Some designers and PMs are all about delivery so fit in nicely. Others straddle both, and invariably struggle.
5 proslijeđenih tweetova 37 korisnika označava da im se sviđaPrikaži ovu nit -
In companies where discovery is basically a group of execs deciding they want a thing and a PM writing a bunch of tickets, that’s fine. In companies where discovery involves developing user empathy and solving business problems before they manifest in code, not so much.
5 proslijeđenih tweetova 37 korisnika označava da im se sviđaPrikaži ovu nit
Dual track that Cagan et al talk about a lot can actually work. The important thing being those in discovery bringing in tech folks to help spike out ideas during discovery and sharing often ideas of where it is going for adaption. This is super hard to get a business to buy into
-
-
Odgovor korisnicima @raymosley @paulpod
Yep. Think
@cagan is generally on the money here.1 reply 0 proslijeđenih tweetova 0 korisnika označava da im se sviđa -
Lots of agile coaches haven’t worked with design teams makes the problem worse. Sometimes the other way too, designers not knowing how the process fits. It’s the comms that matters most - not silo off vital inputs of discovery. Still looking for the org where I can do it though
1 reply 0 proslijeđenih tweetova 1 korisnik označava da mu se sviđa - Još 2 druga odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.