What advice do you have for others considering Microsoft Azure DevOps?

I recommend Microsoft Azure DevOps. It is user-friendly. I'd rate the solution eight out of ten.

We are working with the SaaS (Software as a Service) version of the solution, which is on the cloud. Since Microsoft provides the latest upgrades and patches, it should be the latest version. We start by creating backlog items. Whenever we get a requirement, we log it into Azure DevOps and plan the backlog. The backlog includes what features we need to develop and what tasks we need to assign to each developer. Each developer is part of the DevOps. Once you have created that backlog, we assign it to different developers based on a sprint. Suppose we are going to run a four-week development cycle. So, we plan the development cycle, pick a few items from the backlog, assign them to that sprint, assign them to the developer, and then manage the execution of that development cycle. Once that's completed, we will transfer it to the test team so they can test it in Azure DevOps. They have test scripts that are documented in Azure DevOps. They run tests, record videos, and capture screenshots in Azure DevOps. After the test verification, we deploy the solution. In addition to backlog management and product management, we use Azure DevOps for build and release deployment. We don't manually go and build the software. Our code repository is also part of DevOps. As soon as we check in the new code, Azure DevOps automatically builds the solution and then deploys it in the development environment. Once it's confirmed, the same is deployed to quality and production. We use the solution to do everything end to end, other than ITSM. Specifically, Azure DevOps is integrated with deployment for us. When we manually deploy a solution, it's prone to errors. We use Azure for website deployment and Azure DevOps for Apple app or Google app deployment. As soon as the approval is done in Azure DevOps, apps are automatically published. It will publish an app on the Google Play Store, Apple Play Store, and Azure, which we use for web hosting. So, it is integrated with web hosting, Apple Store, and Google Play Store. The solution does not really need any maintenance. Once you enable the testing solution, you can start creating your test plans and test scripts directly. Every time you do a deployment, you just need to run those test scripts, which is pretty easy. It's more about creating your test script than configuring the tool. Even if I do it in Excel, I need to spend time on that. The solution's analytics and reporting are pretty easy. We use them very often on an ad hoc basis whenever we discuss and plan what to deploy and what the next steps are. It's pretty easy, and we haven't faced an issue where we weren't able to take out any reports just by doing it on an ad hoc basis. It's pretty easy, and you don't need to write code or anything. The tool is pretty flexible and easy to use. I suggest starting with the cloud version because you can create your project easily. Since it's free for five users, organizations with budget constraints can start playing with limited users. I would say start with the cloud-based version and start playing with it. Once you get comfortable with it, you can expand it for other projects. The tool serves a wide variety of use cases. The biggest key trend these days is fast deployments or quick releases. Given how competitive the market has become, you need to keep on adding features to your product. Azure DevOps supports the sprint methodology, which supports fast deployment. On top of that, it supports automated build release deployment. That was a headache when I started working. Sometimes, you forget a file when deploying in production, and your system will go down. The solution's features support the latest fast or quick deployment trend. Overall, I rate the solution a seven out of ten.

We used Azure DevOps to collaborate on migrating a legacy banking application from a mainframe to a Windows platform. The project aimed to demonstrate the feasibility of migrating legacy banking systems. Azure Repos improves code version control and collaboration by providing a centralized repository for source code. It enables multiple developers to work on the same project, track revision history, and merge code changes efficiently, essential for collaborative development environments. Using Azure Test Plans significantly improves software quality by enabling structured test planning and automation. This ensures that code is thoroughly tested, enhancing solution integrity and mitigating risks associated with code implementation. Integrating Azure DevOps with other tools and services is straightforward and intuitive. I found it easy to integrate monitoring and other tools with Azure DevOps. Before implementing Microsoft Azure DevOps, new users should be aware that it is a complex software requiring careful planning and design. Conduct a proof of concept to ensure it meets your needs, and engage specialists to design your environment accordingly. Additionally, be prepared for a cultural shift in utilizing the tool effectively. Overall, I would rate Azure DevOps as a nine out of ten. I always recommend it to all of my customers.

Microsoft Azure DevOps is the best choice because it is an end-to-end solution. Everything is integrated and trackable from every point. Right from my operations team to developers, everyone gets a clearer picture of everything. Overall, I rate the product a 9 out of 10.

Microsoft Azure DevOps is deployed on the cloud in our organization. The product supports our agile project management practices very well. We can configure a process, and it would give you some different types of tasks, like the epics feature, user stories, and tasks. We need very little staff for the solution's deployment and maintenance. For source control, we use Git repositories that are perfectly integrated into our IDE, Visual Studio 2022. Everything is available, and we can create or pull requests from Microsoft Azure DevOps. We can also manage, reject, and accept the requests. I would recommend the solution to other users. Using Azure Boards for tracking work items and bugs is clear and visually appealing. It's easy to add tasks. In our current configuration, every time I go inside the tasks and go back using the browser, it doesn't redirect me to Azure Boards, even if I am coming from there. Since the solution is available as Software as a Service (SaaS), you won't need to do any setup, installation management, etc. It's very straightforward, and there is no particular study required. To a certain degree, the solution is configurable and can suit different use cases. It is working very well in terms of Git repositories. Microsoft Azure DevOps is also very accessible. You can define tasks using Microsoft Azure DevOps and then reference them when you write a commit message or push code. You can open a previous commit in the browser from Visual Studio, and you can use DevOps to compare some files or to check commits done by Visual Studio. So, the solution is perfectly integrated. Overall, I rate the solution a nine out of ten.

Microsoft Azure DevOps gives us an end-to-end solution. We could write the epics feature and user stories. From there, we could create the batches in the repository and create a pipeline to deploy. We can also use test plans to test different application scenarios. We are using Microsoft Azure DevOps as an enterprise-level solution. Azure Boards have been good at improving our project tracking and agility. We are using the Azure repository, and it's working well for us. Microsoft Azure DevOps is deployed on the cloud, and we are using a Software as a Service (SaaS) version. I would recommend the solution to other users because of its pricing and because it is an end-to-end platform for everything, including project management. Overall, I rate the solution a seven out of ten.

We ensure the security of our company's source code uploaded to Azure Repos by using a SonarQube Plugin and then automate its deployment to various environments like development and QA. Once approved by QA, we deploy to the production environment, passing through our firewall for protection. This streamlined process ensures efficient and secure CI/CD pipelines with Azure DevOps. Azure Boards has significantly improved our project tracking and adjustability. It is a powerful tool where we can easily trace work items and monitor the progress of our projects. Azure Boards is a powerful tool for tracing work items and project progress. It simplifies uploading and versioning of project assets and tools, enabling easy refreshes or benchmarks. Overall, I would rate Azure DevOps as a nine out of ten. I would recommend it to others.

In my experience, integrating reporting and analytics into Azure DevOps enhances project visibility and decision-making processes. We can easily generate reports online to track project status and task progress. Additionally, I have integrated Azure DevOps with other tools like SQL Server, enabling us to gather data for generating Power BI reports. The most beneficial integrations with Azure DevOps are integration with other project management tools for seamless collaboration and APIs for importing data into applications. Additionally, integrating with personal models allows for enhanced analytics and reporting on resource performance and other project metrics. The source control management features of Azure DevOps, particularly Azure Repos, are highly effective. We can easily track and manage code changes, commit updates, and maintain a complete history of changes for our applications. I would recommend Azure DevOps to others. Before choosing Azure DevOps, I would advise considering the need for better project management, consolidation of management tools, and streamlining deployment processes. Overall, I would rate Azure DevOps as an eight out of ten.

Considering someone whose organization is thinking to implement Microsoft Azure DevOps, I would suggest it would be a great option.  I would recommend as the setup is easy to follow and there are lots of documentations and support available to guide you through the process.   I would rate it a 9 out of 10.

Whenever you are considering to use Microsoft Azure DevOps in your organization there are a number of key points to take into consideration before implementation.

Firstly, you will need to clearly define your goals that is: your project goals, team requirements, size and desired outcomes. Clearly understand what you want to achieve and this will guide your implementation and configuration to a success.

Also, you will need to learn the Fundamentals of Azure DevOps, such as its components: Boards, Repos, Pipelines, Test Plans and Artifacts. Then customize to fit your workflow as it offers flexibility and customization options to adapt to your team's specific workflow and processes.

Automation is also important where you can leverage Azure Pipelines to automate your build, test, and deployment processes. Automating repetitive tasks reduces manual effort, improves consistency, and accelerates the delivery of software updates. Azure DevOps integrates seamlessly with a wide range of development tools and services such as IDE, version control system, testing framework, and third-party services to create a unified development environment.

Another important factor is to implement security where you would need to configure Azure DevOps projects and pipelines, ensuring proper access controls, encryption, and compliance with regulatory requirements to protect sensitive data and maintain the integrity of your development process.

Overall, I rate the product a seven out of ten.

Overall It offers a comprehensive array of features with accessibility and support for customizations and performance enhancements. Its extensive feature set covers various aspects, making it highly versatile. I strongly recommend Azure's demo for exploring CI/CD pipelines, boards, and customization options. It will undoubtedly streamline development activities, reducing effort and boosting productivity significantly. Overall, I would rate it eight out of ten.

Overall, I would rate the solution an eight out of ten. I would strongly recommend using this solution.

My advice to those looking to use Azure DevOps would be to make good use of the documentation available on their website. It is a valuable resource that can help answer questions and provide clarity on various aspects of the platform. Overall, I would rate Microsoft Azure DevOps as an eight out of ten.

Azure DevOps or TFS is a very good tool for development teams. It's easy to use. However, you would need the help of a consultant who has a lot of experience with the tool. This is because the tool let's you do things in many ways, but not all of them will be the right way to do it. It would be better to invest in the services of an experienced consultant. Overall, I would rate TFS or Azure DevOps at nine out of ten.

I rate the solution nine out of ten. If someone is considering developing and deploying the infrastructure in this solution, then using this tool is perfect because it's fully integrated with the pipelines and with a server core repository. When you are building infrastructure, then you are able to use the same tool to deploy the server, deploy infrastructure, and all within a few minutes. This gives you access to the same tool, task management, dashboards, pipelines, and the server core repository. So everything you need to develop a server is integrated into the same tool.

I'm just a customer and an end-user. I'd advise new users to plan very carefully the way that they would like to set up projects. The model that you choose is extremely important and you might have to do a lot of rework if you don't get it right the first time. I'd rate the solution an eight out of ten. It's Microsoft. It's backed by the mighty, mega Microsoft. You can't get fired for choosing the top product run by a top multinational company. The downside for us here is, in South Africa, there are only two points of presence. For the data, if it's fully hosted, we only have Capetown and Johannesburg. When it comes to back hall speeds for internet, it could be better if we had points of presence in all the major cities, however, I suppose it's too much investment for Microsoft to make.

The voice of the customer is very important. Develop the software based on the voice of the customer. I rate Microsoft Azure DevOps a seven out of ten.

Mostly, because of the pricing, I would rate Microsoft Azure DevOps a seven out of ten.

My organization is a Microsoft partner. I have Microsoft certifications. I always develop in Visual Studio, .NET, or Core, and now I work with Azure DevOps and also in Azure Portal. I deployed in a hybrid environment as the clients have a lot of things on-premises. For example, the databases I use, for example, Redgate, plus Azure DevOps, or Apex with Azure DevOps, to deploy databases. In some cases, a lot of banks prefer their data on-premise. In other cases, I deploy to Azure App Services, for example, in the cloud. Also, I see things with Amazon Web Services and telephone, like multi-cloud. I would rate the solution at a ten out of ten as it never gives me any problems.

Get to know the product because it is complex and has many different possibilities. It is worth having it, but you have to have an in-depth understanding and know what it is capable of doing. Otherwise, you're going to install it, and then it will be like having a very nice car in your garage that you don't know how to drive. On a scale from one to ten, I would rate Microsoft Azure DevOps at eight.

I would recommend this solution to others. I rate Microsoft Azure DevOps an eight out of ten.

I would advise organizing and doing the right assessment for all teams that are going to use it. When it is being set up, more people within the program need to be involved in the setup, not just the developers. You need to know about the requirements for design, development, testing, integrations, and architecture. You need to solicit requirements on what each one of these teams needs from the tool before the tool is configured. When you set something up only from the development perspective, you forget that there would be a need to extract information for data testing and training. So, you need to assess who all are going to use the tool so that you set it up for maximum usage. At this time, I'd rather not recommend it because it wasn't set up correctly. It wasn't set up with other teams involved. In a year's time, if I'm working on it again, I may have a different opinion. I would rate it a five out of 10.

It's a great product for the CI/CD process, but DevOps lacks some features for project management, guide, user story, etc., so it's far from perfect. Compared to monday.com, JIRA, or others, they have some work to do.

All people who work on projects must have good staff in development in .net, and need to have certificates. The minimal certificate is the AZ-204 Azure developer, it is obligatory. I rate Microsoft Azure DevOps a nine out of ten.

My only advice would be to go for the cloud version of DevOps, it's a better product. I rate the solution eight out of 10.

I rate this solution eight out of 10.

You would really have to do a comparison, and you would need some training. It really depends on your project management and reporting requirements. DevOps is simple to use, but it is severely limited in terms of project management. JIRA is complete, but it's a lot more complicated. I only use it for project management and the tools associated with project management. I know it's popular among those who use it for source code control and release management. It appears to be more satisfactory for that purpose. I would rate Microsoft Azure DevOps a five out of ten.

I would rate this solution 9 out of 10.

We’re a customer and an end-user. I’m a big fan of DevOps. It’s a good project and I haven’t seen anything else like it. As we’re on the cloud deployment of the solution, we’re always on the latest version. I’d advise new users, if they are a Microsoft shop, to choose DevOps over Jira. It just makes more sense. I’d rate the solution at a ten out of ten.

My advice to others is for them to do their research before implementing this solution. I rate Microsoft Azure DevOps a seven out of ten.

We are both a reseller and a partner of Microsoft. We always use the latest version of the solution. I would recommend this product to other companies and users. If a company or a team doesn't know how to work with Azure DevOps, the advice I would give is to find someone that knows the tool and do a POC first to make sure you understand everything a bit better before diving right in. In general, I would rate the solution at an eight out of ten.

I'm somewhat critical of the documentation for certain things, but overall, the documentation is really good. In general, Microsoft is really good at documentation. It's worth taking a few hours to read it and then you'll know a little about how Access works. If you set up a sandbox, you're not going to destroy anything and you'll learn by trying things out. I would still read the documentation and go in parallel so you can at least know enough and be aware that it's safe to get in there. We are very heavy users in creating small projects and then sometimes deleting them because they weren't useful but I like that model. Create a little sandbox and go build. We have done our own workflows and they are always tested in a sandbox before going live. That would be my suggestion. I rate the solution eight out of 10.

I'd say Visual Studio is a nine out of 10. If you're thinking about adopting Visual Studio, research the kind of functionality you need. The nice thing about Visual Studio Code is that it's a modular design. So if you're working on a strange language that has a different syntax, you can just get a plugin that'll format your code for you based on the language it's in.

I'm an implementor. I work with a variety of clients. I'd rate the solution at a nine out of ten. It's great for agile and we've been pretty happy with it as an end-to-end solution. If you're moving into an agile CI/CD, DevOps is the way to go. If you're still thinking about old manual start testing, Micro Focus is probably the way to go. That said, more standalone manual testing is better supported by Micro Focus.

To run it, to use the tool the way it's designed, you need someone who understands Scrum or Agile project management. I have used GitLab and other pipeline tools like Jenkins. Azure DevOps combines all of them together, and it beats all of them at everything they do. On a scale from one to ten, I would rate this solution at nine and advise others to go for it.

It is an Agile tool. We were using the tool calling that we were Agile, but we were really doing things in the Waterfall methodology. It was our square peg in the round hole, and that's where I realized that we didn't have the capabilities in DevOps to use it as a Waterfall tool, which makes sense because Agile is a different approach. We've evolved since then, and now, we're doing a bit more Agile when we use the tool. So, a tool is just a tool. There has to be that thinking alignment. Otherwise, it is a square peg in a round hole, and it doesn't quite fit. Your organization and your team have to understand that. Just using the tool doesn't make you agile. The only problem we had was when we rolled this out, we didn't realize how Waterfall we really were. So, I had to go back and have PMs create additional data elements for us to capture what we really wanted to capture to report in Waterfall. Dependencies weren't tracked, and we had to go back. It almost felt like we had to do rework, and people weren't too happy about that. I haven't used its mobile device capabilities, but that's definitely something that I would hope to evaluate in the future. I would rate Microsoft Azure DevOps an eight out of 10. Overall, I'm pleased with the tool, but there is definitely some room for improvement.

I'd rate the solution at an eight out of ten. So far, we've been very pleased with its capabilities.

My advice to others wanting to implement this solution is they need to think about their inter-process before moving to this kind of solution. In many cases, we start to configure some projects using the tools, but if we do not have our roadmap and do not define our goals, we cannot take full advantage of the tools. There should be a lot of planning before moving to the projects. I rate Microsoft Azure DevOps a nine out of ten.

I would recommend this solution. I rate Microsoft Azure DevOps an eight out of ten.

I would recommend this solution to new users if it's a simple project. If you want JIRA, you'll need to have JIRA software for backlog management. On a scale from one to ten, I would give Microsoft Azure DevOps an eight.

We plan to continue offering this product to our customers and I would recommend it. I rate Microsoft Azure DevOps a seven out of ten.

I would rate Microsoft Azure DevOps and eight out of ten.

I would recommend this solution. It is a nice environment for working in teams and implementing the DevOps philosophy. It provides good support for that. I would rate Microsoft Azure DevOps an eight out of ten.

I would rate Microsoft Azure DevOps a ten out of ten.

We are using the latest version of the product. Our organization has five people who are using it. We plan to continue to use Microsoft Azure DevOps because our development or our environment is one of Microsoft's. My advice to someone considering implementing the product is that it is good. I work in a Microsoft school so this is the environment with which everyone is acquainted. I would rate this solution a nine out of ten.

It is a really complicated product. All DevOps stuff is complicated. The advice that I would give to anybody doing DevOps is to have a goal in mind of what you want to do. Then the product will do what you wanted it to do. I would rate Microsoft Azure DevOps a four out of ten because I don't know it enough to rate it.

Overall, on a scale from one to ten, I would give this solution a rating of nine. If Microsoft Azure DevOps were more accessible in south Brazil, I would give it a rating of ten. Although, the reason for this may be due to the price.

On a scale from one to ten, I would give Microsoft Azure DevOps a seven.

I would recommend this solution, it is a good tool to use. I rate Microsoft Azure DevOps an eight out of ten.

I would certainly recommend this product. There are a lot of parts to the toolchain for DevOps, so take each area at a time. My advice is to take one step at a time, don't overdo it, and over time build out all of the capacity difficulties. Automation is also one of the biggest things. Overall, it seems like a really good solution. I would rate it a ten out of ten.

If you're looking for a cross-platform solution that end-to-end does everything in the development life cycle, this would be a very good solution for you. If you're looking for a more siloed product that is specifically focused on one particular area of the lifecycle, this is definitely still an option, but you should also evaluate other options as well (Atlassian, IBM Rational, MIcro Focus ALM, GitHub etc) for completeness. I would rate Microsoft Azure DevOps a solid eight out of ten. It is really good at what it does, but it also has some solid areas of improvement that are needed. Once they have addressed those, it could be hard to beat.

We are just a customer. We intend to move from on-premises to the cloud next year. I'd recommend this solution. It's a worthwhile investment. I would rate the solution at a nine out of ten. We've been quite satisfied with it overall.

I would rate Azure DevOps as an 8 out of 10. I would ensure that DevOps' use is planned, in detail, including the implementation before using the software. I would also ensure you have a thorough knowledge of the main components of the system. This will ultimately save hours of work.

We plan to continue using this solution. I would recommend this solution, but I would not know their business needs. Based on the various features, the deployments, licensing, pricing, and the customer experience, I would rate Microsoft Azure DevOps a seven out of ten.

I would advise potential Microsoft Azure DevOps users to start exploring the free options, which are pretty good. I use it myself as an independent. As soon as you start using it, you'll know that you have to pay because it's a good tool that we can have to manage our code. On a scale from one to ten, I would give Microsoft Azure DevOps an nine.

There are a lot of different tools on the market such as Jira, so I would look at DevOps as one option and how it is going to handle things in your environment. I would rate this solution a six out of ten.

Overall, this is a good product and I recommend it. I would rate this solution an eight out of ten.

It's very easy to start using this solution because the first five licenses are free. As a result, it's easy to track and compare with other solutions and it's easy to scale. I would rate this solution a nine out of 10.

I would recommend Microsoft Azure DevOps for other users who are interested in using it. I would rate this solution an eight out of ten.

We're just Microsoft customers. We don't have any business relationship with the company. I'm not sure which version of the solution we're using. I'd strongly recommend the solution to other organizations. I can't see us ever reversing back now after being on this for a year. Overall, I would rate the solution at an eight out of ten. It's relatively easy to use and it does what we need it to do.

I would give Microsoft Azure DevOps a six out of 10. Microsoft Azure DevOps is not perfected yet, as it needs to be more user friendly. If it can achieve that it will eventually reach a 10.

This is a product that I can recommend to other users. I would rate this solution an eight out of ten.

Before implementing Microsoft Azure DevOps, I would suggest doing your research on how to configure it. It is a product that I recommend I would rate this solution an eight out of ten.

I would recommend this solution. It's a good tool and it's free. Instead of spending money on premium tools, you can at least start with Microsoft Azure DevOps and then upgrade it slowly. You can learn how to use this tool in less than a day. If you have Microsoft 365, this comes with it for free. It doesn't require any maintenance. I would rate Microsoft Azure DevOps an eight out of ten.

In summary, this is a good product but I would like to see better Office integration and API support. I would rate this solution an eight out of ten.

My advice to anybody who is considering Azure DevOps is that it is quite easy to onboard. It is a good product if you really want to work in a close-knit environment. I would rate this solution an eight out of ten.

I would rate this solution a nine out of ten.

We're partners with Microsoft. I'd highly recommend Microsoft, and I recommend it more than any other solution. Everything is very simple and straightforward. The only worry for some organizations may be the cost. You need to be really, really careful. I'd rate the solution overall nine out of ten. I think it's really, really great. If the functions were a bit better, I'd give it a full ten out of ten.

On a scale from one to ten where one is the worst and ten is the best, I would rate Microsoft Azure DevOps as an eight-out-of-ten. It is not quite up to the level of other offerings in some ways but it is improving all the time.

Overall, this is a good product and if the Gantt chart and occupancy reporting features are added then it will be the most powerful one in this space. I would rate this solution an eight out of ten

Overall, this is a good product and one that I recommend. The features it has have helped us, especially with tracking dependencies. I would rate this solution an eight out of ten.

I'm not sure which version of the solution we're using at this time. I personally just love using Microsoft DevOps. I would recommend the solution to anyone. Organizations considering the solution should just go for it and they should get the complete orchestration. I'd rate the solution eight out of ten. I don't think that I have explored everything extensively yet. Any product definitely will have its own gaps, and since I'm not in a position to understand it 100%, I want to play it safe on ranking it at eight.

Personally, I like this product and it is one that I recommend. That said, based on my experience, I cannot say that it is perfect. I would rate this solution a seven out of ten.

We are using the public cloud deployment model. Potential users should not hesitate to move to Azure DevOps. It keeps on progressing and keeps on adding new features all of the time, so it's a solution that I would highly recommend people use. I would rate the solution eight out of ten.

It's a good tool, quite rich, it has a lot of features, and quite a lot of analytical capabilities which are built on top of it so that you can see how your projects are going and all that stuff. It's a good tool. I would rate it a nine out of ten.

My advice for anyone implementing this solution is to have an expert for every fifty users of the solution. This person is responsible for configurations and so forth. If you have a Microsoft environment then this is an easy choice for you, but if you don't then I think that JIRA would be a better choice. I would rate this solution a seven out of ten.

This is a solution that I would recommend. Azure DevOps is a leading platform, but some things can be better. I would rate this solution a seven out of ten.

Deployment of solutions on Azure DevOps is a perfect way to provide Disaster Recovery and High Availability. This is a straightforward solution, and I would suggest not wasting any time looking at others. Right now, this is the best solution. I would rate this solution ten out of ten.

The first thing that I would suggest is to read the documentation for the platform. The online documentation changes pretty much every other week; there is always something new coming out. Practice, practice, and practice. Test, practice, and repeat. You need to know your way around the platform and the only way to do that is by hands-on practice. You can't break the environment, but you can speed things up on the thirteenth hour. It depends on how you configure things since every configuration is different. It's an excellent product that is taking into account current technology, yet also flexible enough to use with future technology. At the moment I would rate Azure DevOps as a nine out of ten. The reason I wouldn't give anything a ten is because it's constantly evolving. There is room for improvement, as this is not the finished article at all. The reason I would give it a nine is the information to get the best usage out of the product is readily available. I've been using Microsoft tech for over 25 years now and back in the day it was difficult to get information out of Microsoft even when you were an MCPN. You would have a special link to go through a Microsoft back door to gain information. That's completely different to the advice that you would get related to Microsoft.com. Now Microsoft is completely different with everything readily available. You can download it in pdot format and the document could be 2000-3000 pages. They leave no stone unturned. The only problem I would say at the moment is a friend of mine said that the Microsoft test book is taking a long time to come out because he wants to take the exam. Some people need to read the information and retain the information that way. Sometimes you go on these courses that are not run by Microsoft directly. They can be very flaky and don't have all the information or experience of using the product in normal working life. If there is anything I would ask for, it's to get the documentation out on hardback so that we can add it to our libraries. That would be very good.

I would advise someone considering this solution to use Microsoft because it is very user-friendly, it can run on small levels of applications, can be calibrated to the application, it can be scaled to a larger scale, from small scale to larger scale. It's very stable, you just need to increase the receptors if you need to scale to a larger scale. I would rate this solution a nine out of ten.