Blog
... latest news about Spotlight

News for April 2013

How Spotlight Embraces Continuous Deployment

Continuous DeploymentA recent article from Wired described LinkedIn’s recent transition to a form of continuous deployment for their software development. It has been a resounding success, leading to software releases several times a day as opposed to once a month as it was before. This has allowed them to implement new features such as new company pages and a home page redesign quite quickly.

Spotlight is engrained in the continuous deployment process, releasing code to the production environment weekly and sometimes more often. Here we look at our experience with continuous deployment and how it may be worth considering for your business’s development process.

What is Continuous Deployment?

Continuous integration/deployment is the term used in software development to describe a practice where small chunks of code are deployed in production on a regular, frequent basis. After passing through various staging processes, the new code is released to its end users.

How is Continuous Deployment implemented for Spotlight Development?

The codes are basically maintained in a source code repository, which is also called a version control system. The changes or new development done by the developers are integrated in the working version of the code known as the mainline or trunk. These integrations happen as frequently as possible and currently, Spotlight is on a weekly release basis.  The build servers are used to carry the integration process. There are ample reasons of having a build server, such as standard workflow independent of local development environment and easy access to code/test metrics. The build servers have automated test suites deployed to replicate the requirements of production environment. With a developer’s new code commit, build server gets triggered for integration and the test suites begin to run. These automated tests and some amount of manual testing produce results in the form of “Ready to Release” or “Roll Back”.

In case the code gets committed, it is available for release to the production server and its end users immediately. If the code does not pass the test requirements, all the coding is halted for the time the team takes to fix the code and make it releasable.

It is also possible to commit sections of code that are found OK in the test suite run. For example, pieces of future features can even be checked in without them being visible to the users.

Benefits of Using Continuous Development

Spotlight has been developed on a completely distinctive ideology of merging social media benefits to the project management concept. Since the idea is comparatively new to the market, the Spotlight team uses feedback from the end user and believes in quickly adapting new features and updates to this feedback.

Going by the traditional practice of first receiving feedback over a period of time, making changes accordingly and then releasing a new Spotlight product version to the market would involve significant time. In this age of rapid innovation, we know that the present customer demand is for enhanced quality in reduced delivery time.

In achieving this, Spotlight team is adding value to its standard practice as well -

  • With decreased time frame between consecutive builds, the defects can be recognized early in the cycle and hence lessens the effort to resolve them.  This reduces the time needed to resolve the defects and the cost of failure.
  • The practice reduces the overhead of release. For example, as soon as a developer is ready with his release he can deploy it in the line of production.
  • It fosters learning, coordination and project team collaboration since each member is able to learn from the defects produced in the production environment.
  • The team does not have to defer the bugs until the next release and can move ahead with the bug fixes as soon as it is completed.
  • Continuous deployment has reduced waste in the production line process. Changes queued up over a year, meetings to decide if changes are safe enough to release and then the rework if these changes failed in production can significantly slow down the development process. Continuous deployment reduces the software inventory.

Our development team practices continuous deployment, which helps it in achieving faster time to market, earlier feedback from the end users and greater ability to respond to change.

Spotlight would advocate the continuous development practice to all the organizations that share similar ideology. Does you company use this practice for software development? Leave us a comment on how it’s working.

For more information on Spotlight Software and our services, please contact us or visit our FacebookGoogle+LinkedIn, or Twitter profiles.


Friday Findings: Scrum Daily Standups

Daily standups in Agile software projects are a way for a team to connect with each other on a current Sprint’s goals and issues. It’s an opportunity to get organized, collaborate, and engage with each other on the agenda for the day.

Next week we are offering a webinar on daily standups and reporting with a demonstration on how Spotlight actually automates a part of the daily scrum process. So this week, our Friday Findings offer a number of resources to make your daily standups more effective, engaging, and overall more valuable.

The Findings

  • TechWell offers a helpful guide to conducting daily standups and how to resolve common issues that pop up. There are also tips for the distributed Scrum, which we use everyday.
  • Sometimes daily standup meetings get stuck in a routine that loses team members attention to a certain extent. Try adding some variation to the daily standup with new questions or format to keep it engaging.
  • Here’s a unique and fun way to keep your meetings less than 15 minutes while keeping your team on their toes.
  • Daily standups generally consist of the Scrum Manager and project team. But it may be beneficial to include the Product Owner from time to time.
  • This article is an excerpt from the book A Practical Guide to Distributed Scrum and discusses how to handle some of the challenges encountered with distributed scrum teams and meetings.
  • Avoid these common mistakes when conducting standup meetings during your software project. One major tip: hold a standup everyday no matter what the make up of your team is.
  • Base 36 offers 11 great tips for running effective standup meetings. Make sure they are short, on target, and collaborative.
  • We all know one of the main reasons of having a daily standup meeting is to answer what you did yesterday, what you’ll do today, and any issues. But here are 10 other reasons for the meeting you may not have thought of.

Effective daily standup meetings during a software project can greatly enhance team communication and collaboration. This, in turn, leads to quicker identification of potential issues, code that may require some paired programming, and mutual understanding of goals. Be sure to stop in for our webinar next Wednesday to learn more about the daily standup meeting and how Spotlight improves the process for your team.

For more information on Spotlight Software and our services, please contact us or visit our FacebookGoogle+LinkedIn, or Twitter profiles.

Author Profile
Seth Weedin (seth.weedin@spotlightppm.com) is the Director of Marketing at Spotlight Software.

Posted: April 26th, 2013
Categories: Friday Findings
Tags: , , , ,
Comments: No Comments.

An Elancer’s View of Social Project Management

This week features a guest post from Soneeka Jaiswal, who came together with Spotlight Software through Elance as a content specialist. She describes Spotlight and it’s social project management features from the viewpoint of an Elancer working from the other side of the world.

I was first introduced to Spotlight to do its user guide. And here I was browsing through this social project management tool to write the first-hand account of how to start in software management using this application. Let me share my experience and impression of Spotlight with you.

People Working CollaborativelyWhat is Spotlight and Social Project Management?

Like any other socially active person, I can say I’m an avid user of social media sites. The basic benefits or say interesting points I see in social media sites is effective communication and virtually staying connected with each other through status messages and comments. Why I’m mentioning social media while writing about Spotlight is the fact that the main quotient of this application is to stay connected the same way, but in an official group – a software project team.

Spotlight is unique for combining the social project management benefits to Agile software development methodology. The application is also available as a web and mobile app for access anywhere, at any time, and from any device.

Who can use Spotlight?

This product has been designed for associates of software companies working for small or medium projects. The major highlight is that these associates are virtual users sitting at different parts of the world and still working together. Spotlight’s goal is to make a virtual team project a great success by maintaining communication and hence collaboration between their members using social project management.

How to use Spotlight

Communicating and Planning

These different members are grouped together in Spotlight by creating a project. When a project is created, you have different hierarchies such as Project Manager, Lead, Developers, and Testers, etc. Their roles can be defined further, as to who can delegate tasks, view client reports, change accounts, department settings, etc. The project can then be framed as sprints and tasks based on the Agile development methodology, which can be tied to each team member’s task sheet.

Now, how these people stay connected is the most interesting feature of this product and contributes to its social project management ideal. A Status Update Control in each member’s profile enables them to update their current status on the task assigned to them. One can either update the status proactively or when requested by other project members or leads. This is broadcasted to everyone in the group as soon as it is updated. The task bar shows the progress made in the task from which the estimated/actual hours can be made out.  The other members can leave a comment on a member’s status and thus initiate further communication if required.

Imagine how comfortable it becomes not bugging a resource by email or phone every time you want to know the progress of a task. In turn, if you look at it from a team member’s perspective, it becomes valiant to know where and what your boss has been doing instead of thinking “Gosh is he passing the entire buck to me?!!!!”

When communication is the key focus, how can one forget about team member status and availability? So, as rightly expected, Spotlight has this online availability window, showing when and until ‘What time’ the team member is available/not available.

A detailed look can also show what other tasks are in the pipeline for the member. So, knowing the status and upcoming tasks, one can easily judge the team’s progress and project timeliness. Knowing this status allows the manager to plan ahead of time.

So, what I could find while browsing Spotlight was that it is a highly interactive, interesting and informative application. Without having to consolidate updates, one can identify the team’s and in turn the project’s progress.

For Software development and Reporting

So, until now I found all the ingredients for a great management tool. Where is this Agile methodology applicable? Agile Software development methodology is the biggest success in software project management as of date. What it means in layman’s term is that it involves all the stakeholders from the start, divides the entire project into incremental stages called sprints, finds the priority of the tasks and allocates them accordingly. At the end of each day, manager’s get the status report as to what has been done, what is the immediate plan moving forward, and impediments if any.

Now, the most common practice currently is to maintain a spreadsheet wherein an account of all the tasks are created and consolidated. But spotlight has replaced this requirement and offers a innovative way to successfully delivery Agile software projects.

Hence, I see that Spotlight is using social project management principles to make software projects highly interactive, interesting. This in turn, builds a highly productive team environment capable of making a software project a great success!

For more information on Spotlight Software and our services, please contact us or visit our FacebookGoogle+LinkedIn, or Twitter profiles.


Friday Findings: Project Team Communication

Effective team communication and collaboration is key to project success in software development. A software project is constantly changing, new tasks are being introduced, and requirements are altered. Communication between all team members, from developers to QA, is vital to keep the project on track for delivery.

Our new weekly webinar series starting next Wednesday, April 24th highlights how effective team communication is accomplished using Spotlight. The team dashboard and status updates keep the project team in sync and moving in unison towards delivery.

Aligning with our webinar, this week’s Friday Findings features tips and tricks for achieving quality team communication and collaboration.

The Findings

  • One of the fundamental values of Agile Management is communication. This paper from Agile Modeling looks at achieving effective team communication in an Agile project.
  • Gina Abudi of Abudi Consulting Group discusses using effective communication as a best practice to increase the success of a virtual project team. Here she offers tips on building a communication plan when first starting a software project with a virtual team.
  • The PMI Institute looks at communication between the client and project team during a technology or software project. Having open dialogue that clearly communicates the goals of the project to the project team helps deliver a successful product.
  • Kelly Project Solutions offers 6 tips for effective project team communication. They stress the importance of communication across all levels, from executives to the project team.
  • SmartBear discusses 10 reasons development teams don’t communicate. Learn how to deal with each one to make your software project team more effective.
  • Small business computing looks at ways to effectively use social media to improve project team communication. Managing projects in Spotlight allows you to communicate using the social network tools you are already used to, integrated right in the app.
  • eHow Money gives us 5 tips on achieving successful communication in a software project. Having an environment that encourages open team communication keeps project team members on the same page.
  • Another good article from the PMI Institute provides 6 tips to improve communication in distributed Agile teams. Agile teams that are distributed are becoming more popular, especially with software projects, and these tips can make your project successful.
  • This article from Agile Buddha looks at the main challenges that surface with distributed Agile teams and how to solve them. Addressing the people on the team and the communication challenges will help you successfully deliver a software project driven by a distributed team.
  • Serena Software conducted a survey that showed while the Agile methodology is working well for software projects, communication is the biggest challenge. Check out the infographic showing the state of communication in Agile projects.

Communication between project team members is a big determinant of a successful project, whether in software development or another industry. Come join us next Wednesday, April 24th for a short webinar featuring our social network communication platform in Spotlight. Learn some great strategies and tactics for using effective communication to your advantage in delivering a successful software project.

For more information on Spotlight Software and our services, please contact us or visit our FacebookGoogle+LinkedIn, or Twitter profiles.

Author Profile
Seth Weedin (seth.weedin@spotlightppm.com) is the Director of Marketing at Spotlight Software.


3 Tips for Successful Software Testing in Agile

Software Testing for BugsMaking the transition from the waterfall approach to Agile software development can be an involved process. Documentation has to be updated, project team members trained, and new roles defined to accommodate the change. The transition is well worth it though, with Agile offering faster delivery times, higher quality software, and improvement on project ROI.

Businesses have to make this transition carefully. Several new processes have to be implemented and sometimes things tend to get overlooked. Software testing is often a process that falls victim to this.

Bug tracking and QA require a major change when moving from waterfall to Agile. What used to be a process of testing at the end of development with waterfall has morphed into constant testing throughout the duration of the project. For traditional testers used to waterfall, this is an entirely new way of thinking.

But some nurturing of the traditional QA process can make it very successful in Agile. Here are a few tips to help make the transition smooth for software testing procedures in an Agile project.

Involve Everyone

In Agile, everyone on the team—from tester to developer to product manager—needs to be aware of quality throughout the development process. Making software testing part of the daily workflow can lead to faster discovery and remediation of defects. This will help reduce time, effort, and cost in the QA process.

While the tester is in charge and ultimately responsible for the QA process, it never hurts to have another set of eyes looking at the product. During our sprints, our entire development team is keeping an eye out for bugs and reporting them directly to the lead QA tester. Our lead then enters any bugs found directly into the Agile task management system for developer follow-up. It’s a process that is quick and efficient.

Early and Often

In Agile projects, development takes place in small iterations, or sprints, that always end with a functional release. As a result, software testing has to take place early and often in the project. This doesn’t just mean testing the app for bugs, but includes unit tests, functional tests, load and stress tests with every sprint beginning right away.

During development, some changes or updates in the next sprint may require going back and testing something again. But consistent testing, even if it requires some repeat, will ensure earlier detection of issues that could otherwise stall the entire project. We have our QA leads create test scripts as they go through the application. This ensures that anyone else who comes aboard knows exactly what process to go through when software testing, saving a lot of time.

(Over)communicate

Consistent communication back and forth between QA and the development team ensures little bugs don’t turn into project-halting rework. Create an open communication environment by encouraging constant status updates from QA to development on testing progress. A tactic we also use is to include all QA team members in our daily scrum meetings. This keeps them apprised on all tasks the development team is working on so they know what to expect in the coming days. Not only will this help find defects quicker, but also improve teamwork that can often speed up overall project delivery.

Oftentimes, a project management tool for software projects can help manage QA tasks and improve communication among the team to make sure nothing gets overlooked. Spotlight does this by allowing the team to collaborate on a centralized dashboard using social network-like communication tools.

Conclusion

Software testing can be very successful in an Agile setting and actually much more effective than with traditional waterfall. Defects can be found quicker and remedied sooner, propelling the project to a faster completion. Involving QA testers in the entire project results in a new level of teamwork that can move software projects through the development life cycle much quicker. Additionally, increased and improved teamwork just makes everyone’s job more enjoyable.

Obviously we believe software testing is a very important part of successfully delivering a software project. This is why we decided to implement the functionality for our next release with the new Bug Tracking & QA Flags feature. Join us for a webinar on Wednesday, April 17th at 10 am Pacific (1 Eastern) to get a first look at the new feature before official release!

For more information on Spotlight Software and our services, please contact us or visit our FacebookGoogle+LinkedIn, or Twitter profiles.

Author Profile
Seth Weedin (seth.weedin@spotlightppm.com) is the Director of Marketing at Spotlight Software.


Friday Findings – QA Testing

Spotlight is introducing a new feature for bug tracking and QA flags that will automate the process of tracking but resolutions throughout the life of a Sprint. Check out this new feature in our webinar next Wednesday, April 17th at 10 am PDT before the official release!

In the spirit of this awesome new feature, this week’s Friday Findings looks at QA testing in a variety of scenarios and from several points of view.

The Findings

  • Testers often run into limited time and resources hampering their ability to test every detail of a project. Here are some tips on managing time wisely with testing tasks.
  • Ensure you are meeting your customer’s needs for quality when building software. David Nielsen offers up 9 tips on software testing that will improve quality immediately.
  • Be prepared when the testing phase starts in a large software development project. Here are 5 essentials for successful software testing.
  • The challenges encountered in Agile software testing can be different from the traditional waterfall method. Understand how QA testing works in the Agile and Scrum process in this slideshare presentation.
  • Keeping QA in sync with the development team will result in quicker identification of issues and faster resolution. This blog from Jamie Saine at uTest looks at why it pays off for developers and testers to work together.
  • The explosion of mobile enabled websites and apps has added another element to testing that has to be approached in a new way. Here is another great article from Jamie Saine at uTest on the state of mobile QA testing.
  • Ole Lensmar of Network World gives an interesting take on the art of software testing and why testing that “breaks stuff” is absent from companies and conferences. Take note of the 3 bullet points at the end on the importance of QA testing.
  • Michael Bolton, author of Rapid Software Testing, outlines 5 important principles of rapid software testing in this article from SiliconIndia. His book discusses how to do excellent software testing that is very fast, inexpensive, credible, and accountable.
  • QA in the Scrum framework is much more than writing test cases and reporting bugs to development. Priyanka Hasija talks about his 2 year experience as a QA analyst on a Scrum team in this article on InfoQ.

QA testing is of the utmost importance in delivery a quality product at the end of a software project lifecycle. Come join us in the webinar next Wednesday, April 17th to learn about our new bug tracking and QA flag feature and some good advice on making software testing successful for your team.

For more information on Spotlight Software and our services, please contact us or visit our FacebookGoogle+LinkedIn, or Twitter profiles.

Posted: April 12th, 2013
Categories: Friday Findings
Tags: , , , ,
Comments: No Comments.

The Virtual Daily Scrum: Can it Work?

Virtual Daily ScrumDaily scrums are the first step in building team trust in Agile software development. They keep development teams communicating and working in sync towards the project goals. Scrums keep projects on track, help identify issues early, and increase overall productivity.

Virtual teams made up of freelancers or contractors are increasingly being utilized to execute software projects for businesses. One team member may be in Mexico while another is in Chicago. With different time zones, little face-to-face interaction, and different schedules, how can a daily scrum possibly be executed? We offer 5 tips for holding daily scrums with virtual teams.

Maximize Communication

Daily scrums only allow you to get your entire team together for 15 minutes every day. Maximize that time to the fullest with open and quality team communication. Whether you use video or web conferencing, the traditional conference call, or even a group chat, ensure that it’s not 15 minutes of only one person speaking. Silence from team members can mean a number of things so don’t just infer there are no issues if this is the case.

At Spotlight, we have all team members log into a Go To Meeting session daily. They communicate three things:

  • What tasks did I do yesterday?
  • What tasks will I do today?
  • Are there any issues that need addressed?

As a result, developers will end up doing some paired programming on any issues that are brought up during the meeting, further strengthening team trust and camaraderie.

Include EVERYONE

The daily scrum process may be a little different for every business or Scrum Master. Some will include only development team leads and others will include all developers. We have found that including everyone, from QA to Designers to developers, keeps the team operating at the highest efficiency. In a virtual team setting, information is more likely to get lost or forgotten if communication is not optimal. Having the entire project team collaborate in the scrum ensures there are no surprises and keeps the entire team moving forward in unison.

All phases of a software development project are interrelated so one piece can’t operate without the others. Having all members of the team participate in the scrum lets development know when design is ready and so on.

Consistency

Once you decide on a method of communication and time for the daily scrum, try to keep it consistent every day. Ideally, it will be first thing in the morning so the team can discuss what went on the day before and the tasks they have coming up that day. If any issues are brought to the table, the developers have the rest of the day to find a resolution.

One of the beautiful things about working virtually is the ability to be flexible with schedules. If your developers don’t work the typical 8 to 5 workday, schedule the daily scrum at the beginning of their shift. Our development team typically works from late afternoon well into the night. The daily scrum is scheduled when they get online so they have a full workday’s opportunity to address any concerns.

Keep it short

Keep your daily scrums short, typically around 15 minutes. Developers don’t have time to sit there on the phone or in a web conference listening to a conversation that doesn’t concern them. Virtual daily scrums can get especially time consuming if every team member is taking time to speak in this manner. Clearly communicate the answers to the 3 questions of daily scrums and adjourn so everyone can get to work.

Schedule follow-up meetings

Abbreviated daily scrums lead us to the next tip: schedule follow-up meetings. If team members get into a conversation on an issue or development task during the scrum, have them jump back on the conference call later to discuss further. This allows the rest of the team to go about their daily agenda while the other team members work together on the issue brought up in the scrum.

The Scrum Master can then assist with any specific issues directly if need be or take a question back to the product manager.

Your Experience

Daily scrums keep the communication channels open within virtual Agile software teams to keep the entire team in sync with each other. This helps tasks get completed faster and bugs identified sooner. All of this adds up to faster time to delivery.

Do you have other unique ways of executing scrum meetings in a virtual setting? Leave us a comment with your experience!

For more information on Spotlight Software and our services, please contact us or visit our FacebookGoogle+LinkedIn, or Twitter profiles.

Author Profile
Seth Weedin (seth.weedin@spotlightppm.com) is the Director of Marketing at Spotlight Software.


Friday Findings: User Stories

Happy Friday! The role of user stories in Agile software projects has always been a popular subject so we decided to focus our findings around the topic this week. Below are 10 articles we found that highlight the advantages of using user stories in your software development projects.

The Findings

  • Agile teams often encounter a common pain point when creating user stories: Who writes user stories when we don’t have any users? Here’s how you address that question.
  • Sometimes user stories become too big, making it hard to understand and implement. So what is the ideal size for a user story?
  • Watch out for these 5 common mistakes when creating user stories for your project from the Scrum Alliance.
  • Use the ACTION acronym for a user story to set clear goals, clarify the amount of detail in the story, and write a story that communicates just enough detail to make the team and customer happy.
  • A great overview on how to write good user stories using these 10 tips.

How does your business implement user stories in your Agile software projects? What kind of success have you had with them?

For more information on Spotlight Software and our services, please contact us or visit our FacebookGoogle+LinkedIn, or Twitter profiles.

Author Profile
Seth Weedin (seth.weedin@spotlightppm.com) is the Director of Marketing at Spotlight Software.


Using Agile to Reduce Software Project Risks

Risky BehaviorDevelopment projects are unique. They are hard to predict, change rapidly, and introduce a number of software project risks. These risks can often be mitigated through Agile project management and practices, helping to deliver the project faster and cheaper. Here we list five software project risks and how Agile techniques can reduce that risk.

Timeline Estimation

The software development lifecycle can be very difficult to predict. One bug here or there or a poorly laid out requirement can delay a project by hours, days, or weeks. With the intangible nature of software, it’s very hard to look ahead and accurately estimate a timeline of milestones.

Agile can mitigate this software project risk by directly involving the development team in planning and estimating. Years of experience give developers a great sense of estimating their work, especially if the requirements analysis is thorough. Using sprints, or short increments of planning and execution, the speed at which the team will move through the project can be quickly identified. Now project stakeholders will have an accurate idea of how the project will proceed at the beginning so they can make appropriate decisions throughout.

Inaccurate Requirements Analysis

A requirements analysis is of the utmost importance before a project even begins. Project Managers and Business Analysts will play a key role in this by having conversations with the customer on what goals they want their software to achieve. Even with a thoroughly thought out requirements analysis, there is always the risk of “feature creep”. As the project progresses, more and more features are added, threatening the estimates and timeline of the project.

Agile reduces this software project risk by building in time for discussions about features and changes during every sprint. Changes in the requirements and new features are expected through the project with Agile, thus teams are prepared for it. Instead of trying to include all these features for the next release, Agile teams prioritize changes based on importance. This means they will push less time-sensitive features to the bottom of the product backlog, allowing teams to anticipate what’s coming and be prepared.

Requirement Specification Errors

After the requirements analysis is complete, a project is broken down into specifications that are more detailed. When the initial development phase begins, it becomes obvious if the specifications are incomplete, have conflicting requirements, or too many tasks for the timeline. This can lead to major project delays as a result of having to circle back around to the beginning and rewrite the specifications.

This software project risk is mitigated by the Agile methodology through the role of product manager to readily make decisions on the project. When there is specification breakdown, a product manager has full project visibility to make key decisions on how to proceed. Oftentimes, traditional projects may lack this role causing delayed decisions, which can derail a project.

Project Team Productivity

Software projects can often be long and drawn out, resulting in motivation and urgency loss among team members as time goes on. Unmotivated teams will result in timeline delays and overall wasted time just trying to get them back on track and engaged in the project again.

Agile practices reduce this software project risk by using short iterations with frequent deadlines. This creates a constant sense of urgency that keeps teams motivated and working together towards the end goal. Agile also encourages frequent project team communication and team member accountability through daily stand-up meetings and progress reports. This creates a very productive working environment that can decrease the time to delivery for projects.

Project Team Turnover

Things outside of a manager’s control will cause teams to have turnover during a software project. Key personnel leaving the project take their knowledge and information with them, often resulting in significant delays or project failure. The number of great software developers available for hire is unlimited, but it always takes time to bring them up to speed on a project.

Agile project teams practice lots of information sharing techniques such as paired programming and daily reporting in stand-up meetings. When all team members share key information every day, this software project risk of critical knowledge leaving with the employee is small. Agile also reduces the bigger problem of key team members leaving by offering a highly collaborative environment that developers thrive in.

Conclusion

Agile techniques offer a number of advantages for software development projects. It will not eliminate all risks with the rapidly changing nature of software development, but you can implement many of the practices to decrease the chance of an unforeseen road bump. Are there other software project risks that Agile practices can mitigate? Leave us a comment with your suggestions!

For more information on Spotlight Software and our services, please contact us or visit our FacebookGoogle+LinkedIn, or Twitter profiles.

Author Profile
Seth Weedin (seth.weedin@spotlightppm.com) is the Director of Marketing at Spotlight Software.