Geeks With Blogs
Geeks with Blogs, the #1 blog community for IT Pros
Start Your Blog
Personal Website / Bio
| 148 Comments
Founder & CEO of Stackify.
My Other Recent Posts
Agile Development Requires Agile Support
Stackify Gives Devs a Crack at the Production Server
Stackify Aims to Put More ‘Dev’ in ‘DevOps’
Production Server Access - Development teams do not scale without it!
Stackify featured in the KC Business Journal
What is Stackify?
Citrix Netscaler vs F5 Big-IP: Load Balancers & Web Application Acceleration
Silverlight is Lighting Up March Madness and 2009
Silverlight WCF Service Reference Usage Simplified
Anti-SPAM Gateway Solution
“It's not easy being drunk all the time. If it were, everybody would do it." -- Tyrion Lannister,
about 529 days ago
So Snapchat might be worth a billion dollars but yet has no revenue... That's insane because it is also likely a fad that will die soon.
about 530 days ago
If it works, stop coding. Nobody cares how it works.
about 532 days ago
How about support for
about 533 days ago
I am. 14 employees total and I still code as CEO!
about 534 days ago
can we be a stop on crawl?
about 538 days ago
can Stackify join in some home
about 538 days ago
about 539 days ago
I will be driving it to every SKC game. So see you there!
about 539 days ago
Hey you're not allowed this far south!
about 539 days ago
February 2013 (1)
January 2013 (2)
November 2012 (2)
October 2012 (3)
September 2012 (5)
June 2012 (2)
May 2012 (1)
December 2009 (1)
March 2009 (1)
February 2009 (2)
January 2009 (1)
November 2008 (2)
February 2008 (2)
November 2005 (4)
October 2005 (7)
September 2005 (2)
August 2005 (1)
October 2004 (1)
September 2004 (2)
July 2004 (1)
April 2004 (5)
February 2004 (1)
January 2004 (8)
December 2003 (1)
November 2003 (4)
October 2003 (11)
Software developer, product visionary, and master of #dadops
<< Stackify Gives Devs a Crack at the Production Server
Access Log Files >>
Agile Development Requires Agile Support
Agile development has become the standard methodology for application development. The days of long term planning with giant Gantt waterfall charts and detailed requirements is fading away. For years the product planning process frustrated product owners and businesses because no matter the plan, nothing ever went to plan. Agile development throws the detailed planning out the window and instead focuses on giving developers some basic requirements and pointing them in the right direction. Constant collaboration via quick iterations with the end users, product owners, and the development team helps ensure the project is done correctly.
The various agile development methodologies have helped greatly with creating products faster, but not without causing new problems. Complicated application deployments now occur weekly or monthly. Most of the products are web-based and deployed as a software service model. System performance and availability of these apps becomes mission critical. This is all much different from the old process of mailing new releases of client-server apps on CD once per quarter or year.
The steady stream of new products and product enhancements puts a lot of pressure on IT operations to keep up with the software deployments and adding infrastructure capacity. The problem is most operations teams still move slowly thanks to change orders, documentation, procedures, testing and other processes. Operations can slow the process down and push back on the development team in some organizations. The
movement is trying to solve some of these problems by integrating the development and operations teams more together.
Rapid change introduces new problems
The rapid product change ultimately creates some application problems along the way. Higher rates of change increase the likelihood of new application defects. Delivering applications as a software service also means that scalability of applications is critical. Development teams struggle to keep up with application defects and scalability concerns in their applications.
Fixing application problems is a never ending job for agile development teams. Fixing problems before your customers do and fixing them quickly is critical. Most companies really struggle with this due to the divide between the development and operations groups. Fixing application problems typically requires querying databases, looking at log files, reviewing config files, reviewing error logs and other similar tasks. It becomes difficult to work on new features when your lead developers are working on defects from the last product version.
Developers need more visibility
The problem is most developers are not given access to see server and application information in the production environments. The operations team doesn’t trust giving all the developers the keys to the kingdom to log in to production and poke around the servers. The challenge is either give them no access, or potentially too much access. Those with access can still waste time figuring out the location of the application and how to connect to it over VPN. In addition, reproducing problems in test environments takes too much time and isn't always possible. System administrators spend a lot of time helping developers track down server information.
Most companies give key developers access to all of the production resources so they can help resolve application defects. The problem is only those key people have access and they become a bottleneck. They end up spending 25-50% of their time on a daily basis trying to solve application issues because they are the only ones with access. These key employees’ time is best spent on strategic new projects, not addressing application defects. This job should fall to entry level developers, provided they have access to all the information they need to troubleshoot the problems.
The solution to agile application support is giving all the developers limited access to the production environment and all the server information they need to see. Some companies create their own solutions internally to collect log files, centralize errors or other things to address the problem. Some developers even have access to server monitoring or other tools. But they key is giving them access to everything they need so they can see the full picture and giving access to the whole team. Giving access to everyone scales up the application support team and creates collaboration around providing improved application support.
Stackify enables agile application support
Stackify has created a solution that can give all developers a secure and read only view of the entire
production server environment
without console or remote desktop access.They provide a web application that provides real time visibility to the important information that developers need to see. An application centric view enables them to see all of their apps across multiple datacenters and environments. They don’t need to know where the application is deployed, just the name of the application to find it and dig in to see more. All your developers can see server health, application health, log files, config files, windows event viewer, deployment history, application notes, and much more. They can receive email and text alerts when problems arise and even safely query your production databases.
Stackify enables companies that do agile development to scale up their application support team by getting more team members involved. The lead developers can spend more time on new projects. Application issues can be fixed quicker than ever. Operations can spend less time helping developers collect server information.
Agile application support
starts with Stackify.
Visit Stackify.com to learn more.
Posted on Monday, September 10, 2012 3:30 PM |
Back to top
Comments on this post: Agile Development Requires Agile Support
re: Agile Development Requires Agile Support
Stackify has created a solution that can give all developers a secure and read only view of the entire production server environment without console or remote desktop access.They provide a web application that provides real time visibility to the important information that developers need to see. An application centric view enables them to see all of their apps across multiple datacenters and environments. They don’t need to know where the application is deployed, just the name of the application to find it and dig in to see more. All your developers can see server health, application health, log files, config files, windows event viewer, deployment history, application notes, and much more. They can receive email and text alerts when problems arise and even safely query your production databases.
to provide agile support by giving developers production access to their applications, servers, and databases to improve their ability to do application support and troubleshooting.
on Nov 19, 2012 5:00 AM
Nice post. Agile development has become the benchmark methodology for submission development. The days of long term designing with monster Gantt waterfall charts and comprehensive obligations is fading away. For years the merchandise designing method frustrated merchandise proprietors and enterprises because no issue the design, nothing ever went to plan.
remote access servers
on Apr 25, 2013 11:44 PM
Email: (never displayed)
(will show your
Allowed tags: blockquote, a, strong, em, p, u, strike, super, sub, code
Copyright © Matt Watson | Powered by:
Popular Posts on Geeks with Blogs
Feedback-Centric Development - The One Hacker Way
Mathematica Data Visualization by Nazmus Saquib, Packt Publishing Book Review
APress Deal of the Day 15/November/2014 - Microsoft Dynamics CRM API Development for Online and On-Premise Environments
#stldodn #dodn14 Jonathan Mills rocks
SQL Saturday #365–Melbourne Feb 7 2015
Geeks With Blogs Content Categories
Team Foundation Server
Brand New Posts on Geeks with Blogs
Testing EntityFramework with Moq
Working with Hardware
Visual Studio 2015 Preview available
Visual Studio 2013 – Update 4 now available
A new open source solution – CommonWindows