Let the community know what you think. Share your opinions now!
1. What's the service provider's recruiting/staffing process? Is it sustainable and scalable?
2. The capability to adapt to different agile development cycles.
3. Interview developers ensure they are at the all-star level
3.1 walk me through a module they are proud of
3.2 test the problem-solving methodology
4. Code-review process enforcement
5. Unit test justification and methodology
6. Conduct a stress-test to ensure they can work under pressure
7. Alignment on code quality standard
multi program language support
direct deployment options
before started to discover what you want
Start by discovering what you want, and then look for experience that specifcaly matches your demand.
Quality of deliverables and pace.
I look for a proven track record of reliability. I want to be certain that any company hired to provide development services can deliver. In addition I need to feel comfortable that should any problems arise after the initial engagement that adequate support will be provided.
Scalability and Modularity
Scalability , user experience
This are the important things
1) OPPS concept , .Net Architecture
3) ASP.NET MVC 3/ MVC 4 Development
4) Understanding of client side technologies,
5) Database application
5) Modernization And Optimization Services,
6) Systems Integration ,
Asp.net application lifecycle and garbage collector working
1. Ability to develop cross platform applications.
2. Knowledge about other systems\technologies to integrate with.
3. Deliver highly scalable solutions that can withstand load\stress.
4. Ability to deliver highly scalable and customizable solutions.
Broad knowledge of .net Frameworks for developers and deep knowledge of platforms for integrator.
If development focused do they demonstrate understanding of OOP concepts, ability to apply common development patterns in .net and explain their methodology to manage the dev life-cycle such as their flavor of agile. A warrior's arrow fired without fins to guide it is a dangerous thing.
Do they think about the .net world? Curious developers will always evolve and that's a good thing. Ask which two emerging .net frameworks in two years will be on the rise and which two will be on the way to the grave, then ask the dreaded why?
Ask them what platforms they have worked with, when, and if they had to work with that platform again what would they not look forward to doing?
Some providers will be specialists, some generalists, depends on your project's needs, both have their place. If they haven’t used Quartz.NET and are building you a scheduling application, not the end of the world but if they don’t at least know it exists along with similar frameworks, that might be a warning flag.
In summary, determine if their knowledge of frameworks or platforms is sufficient for your project.
Deep integration knowledge with other platforms and services with excellent mobile development experience.