-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publicación de blog: Managed services & Staff Augmentation #96
Open
aguselmaizal
wants to merge
147
commits into
nayracoop:main
Choose a base branch
from
fiqus:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Blog post FP
Post intercoop
adding phruzz matcher posts spanish and english
…nto violencia-genero
adding post emprendimientos moda
adding post visita ipna
adding post equivocarse es bueno
Violencia genero
blog post build fix
adding the post from el maizal
Se borra el dominio de las configuraciones
adding archivos del sur blog post
Update archivos-del-sur.md
Add files via upload
Agregar toma de decision post
Fix imagen y link
* Adding post about graphq; * review changes
* Adding post about graphq; * review changes * improving date format
* se agrega url showcase y archivo estatico para mostrar * se agrega title a iframe y reduce padding bottom * redirect to pdf file * remove command for newer node * hack applied to PageWrapper to reload the showcase pdf --------- Co-authored-by: Agustin Recouso <[email protected]>
* se agrega url showcase y archivo estatico para mostrar * se agrega title a iframe y reduce padding bottom * redirect to pdf file * remove command for newer node * hack applied to PageWrapper to reload the showcase pdf * add package lock --------- Co-authored-by: Martin Vallone <[email protected]> Co-authored-by: Agustin Recouso <[email protected]>
Co-authored-by: Agustin Recouso <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Managed services & Staff Augmentation
Let's get to know the different methodologies
What do we mean when we say "Staff Augmentation" and when we say Managed services? What are the differences and which is the best option when it comes to hiring devs?
In this post we will show you all the differences between both hiring models.
Staff Augmentation is the hiring of individual developers to increase the staff of your company while the managed service is the outsourcing, that is, you hire a team that is in charge of finding a solution according to your problems. Now, what does this mean?
While in Staff Augmentation the profiles are added as they are needed, in Managed Service the client hires the entire development process, i.e. delegates the responsibility and the solution to an external team.
Another difference that can be found between the two models is the management of the team: while in Staff Augmentation the client manages the team with individually contracted devs, in Managed Service the team is managed, in this case, by Fiqus and works by objectives. In other words, in this type of model, a whole team that has been working together for years is hired and the management and delivery of the product is included. In Staff Augmentation, on the other hand, the client is responsible for assembling the IT team and managing it.
So what is the best hiring option? 🤔 The reality is that it all depends on what you are looking for: if you need to add professionals to a pre-existing team, Staff Augmentation is the solution. On the other hand, if you need to develop an idea or create a satellite application to the core with a team of experienced developers and stay focused on the business model, the solution is Managed Service 🦾