Remove Agile Remove Quality Assurance Remove SCRUM Remove UI/UX
article thumbnail

An Agile Implementation Roadmap: Making the Change and Getting Started With Agile

Gorilla Logic

That being said, the best approach when it comes to going Agile is to jump right into it and start learning from your mistakes. In this article, I am going to share important tips for starting with Agile, key implementation techniques, and reminders of what not to do in order to achieve success. Where do I start?

Agile 105
article thumbnail

How to Lead Multiple Agile Teams Without Sacrificing Sanity

Gorilla Logic

I have been leading Agile teams for some time now and working at Gorilla Logic for almost a year. One of the most impressive things I have seen thus far is the capacity this company has to lead multiple projects at multiple levels in an Agile way. I am currently the Scrum Master for four different teams all with the same client.

Agile 58
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Cross-functional Team: Composition, Benefits, and Good Practices

Existek

In a software development context, a cross-functional team might include developers, designers, quality assurance testers, project managers, and other professionals with different skill sets. They often follow agile methodologies, emphasizing collaboration, flexibility, and iterative development.

article thumbnail

Cross-Functional Teams in Product Development: Definition, Principles and Examples

Altexsoft

Cross-functional teams in Agile Agile project management can be characterized by iterative development. So cross-functional teams play a critical role in Agile as the product increment has to undergo all the stages of development in a short period of time (e.g. Quality assurance engineer. UX/UI Designer.

article thumbnail

iTexico Engineering Teams Activation

iTexico

iTexico jumped in to provide a team specifically crafted to solve this particular issue, a team which included: a Scrum master, one UI/UX Designer, two people for the frontend, and one more of the backend acting as DevOps for the project. We’ve started taking a new approach with our software engineer teams recently.

UI/UX 9