Charis Rooda 🦦✨
You all wanted better design tools. You got Figma, and it's getting pretty awesome. Their responsiveness and auto layout is all getting close to building things on the web. And now you're complaining again!
The fact your designers and developers are not working together is something you should fix in your process, stop blaming your design tool.
argiris
@RyunoKi care to expand on the latter part? Because I think I've seen it most of my career but can't verbalize it well.
Ryuno-Ki
@charis I feel like I want to have better tools that don't run risk of getting bought up and closed.
Plus, that there must be closer communication within product teams.
Still too much „agile waterfall“ in the industry.
Ryuno-Ki
@argiris I left that company when it grew massively without much change management.
Processes like Scrum of Scrums, SAFe etc feel icky.
So yeah, some frustration in the above from what I've experienced as developer.
Given that Vitaly is doing consulting and Charis is also working in Smashing I can imagine they went through more variants. Wouldn't be surprised if NDAs prevent them from talking about it.
Ryuno-Ki
@argiris I can only remember one company that ran Usability tests with people to validate assumptions before too much time was invested.
In that company, different disciplines got a seat on the table when requirements were talked through (to avoid designing things that would be too complicated to implement).
Testers could formulate expectations on how things were tested.
That would be an agile approach (according to Scrum).
Ryuno-Ki
@argiris Development doesn't start before design hasn't done requirements engineering with the product manager. Developers are only involved once some design crops were thrown over the wall (like in waterfall).
Quality Assurance only kicks in after a sprint to test for regression (manually, because ain't no time for testing and developers must not write the test suite).
After deployment the whole company frantically clicks through the UI. No test plans or anything.
Ryuno-Ki
@argiris So what I observe is a mix of them:
Basically waterfall but with shorter cycles.
When I am interviewing companies (because looking for employment) I'm asking on how they set up their process.
You can be lucky if you find disciplines outside of development and support.
Designers are shared among teams. QA is done by interns or students. Devs are responsible for Ops.
The waterfall aspect here is this:
Ryuno-Ki
@argiris Frustration with this led to some folks sit together and come up with the Agile Manifesto (easy to find online).
This methodology worked different. Especially with shorter feedback cycles, inspection and parallelisation.
Teams were able to handle the requirements themselves (led to DevOps).
(N.B. it can be applied to any project, not only building software).
But in reality, companies are reluctant to go all in on this.
Ryuno-Ki
@argiris Sure.
So Agile and Waterfall are two methodologies on how to manage a project.
In waterfall (the older of the two), one phase was only started when the previous was completed. Like water that falls down a cascade.
Requirements engineering => concept => design => development => quality assurance => operation => support (roughly speaking).
Once the product is in phase of the customer, feedback is collected and the cycle repeats.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.