April 2009 Archives

Presentations1.jpgAs promised, the customer, partner and OutSystems presentations that were given at the NextStep '09 conference are now available online.

These include great case studies on Agile development, Agile technical tips and tricks, and discussions on the future of agile, adoption and business value.

 

Also, if you have not yet completed the Agile Adoption Survey - it only takes 2 minutes and we would greatly appreciate your input!

 

Yes, it took an entire weekend to recover from NextStep! But we're back and just wanted to wrap-up an amazing Agile conference.

First, the OutSystems team would like to thank everyone - guest speakers, customers, partners, members of the press and OutSystems employees - for coming to the conference and making it such an information rich, worthwhile and fun Agile event. Thank You!!

nextstep networking.jpgYou can check out the conference slide show with lots of photos that give a good sense of all that happened at last week's event!

prizes2.jpgNext, we want to hear from YOU! Tell us what you thought of the conference in the comments below.   As we pull our notes together and start thinking about NextStep 2010 - we would love to hear from you.

Was the conference worthwhile?    What did you find most interesting?    How can we make things better next year?   Your opinion counts!

Paulo Rosado said that Trend #1 is that Agile Adoption is accelerating - and this conference certainly seems to be proof of this - with all the exceptional sessions on Agile development and delivery experiences, case studies and tips and tricks!  We will be posting information on how you can access the presentation slides in the near future - in the meantime you can read our blog entries on each session in this blog.

(Please be sure to subscribe and/or follow our Tweets at http://twitter.com/outsystems for future blogs that are all About Agility!)

Gem, User Experience Engineer of OutSystems, closed track 2 sessions by talking about how usability and agility can work well together.

Gem started by highlighting the similarities between usability and Agile, including the fact that they are iterative and that they both mean extra value for the company. But, as Gem pointed out, there are also some fundamental differences, including the fact that usability is slower than Agility and most feedback is gathered from outside the team, as opposed to coming from the team.

gem.jpg
Because of this, mixing both can be a challenge, and Gem pointed out some pitfalls that should be avoided. The main point here was that, if you try to mix the traditional way of doing usability - using an independent usability team with a long usability analysis - the usability professionals will struggle and the results will be poor. After all, by the time the usability tests are available, the Agile built application will have change to accommodate the latest user feedback!

Gem shared with the audience some practices to avoid this problem and to ensure that usability goes along with agility. These include setting usability goals per sprint, make sure feedback is gathered along with other sprint feedback, and most importantly that there is a usability expert in each team. If having a usability expert per team is not possible, select someone in the team to play the role of usability advocate.

To give an example of a project where usability and agility worked well together, Gem used OutSystems ECT. According to Gem, ECT is a great example of how usability and functionality work well together, not only providing a good user experience for the end-user, but also providing all the needed information for the agents that will deal with the feedback.

For wrap-up, Gem gave some advices to add usability to your applications. The most important one is that the developer of the application must realize he or she is not the user! Using the OutSystems style guide is also good idea to ensure usability.

Ideally this would all be followed with frequent user testing, but since having few tests is better than having no tests, Gem suggested that if all else fails, cheat! Do hallway tests, do some tests that don't require users, follow standards, and use what worked well for others!

The last session of track 1 was presented by OutSystems Partner Normatica, represented by Alexandre Mano, and OutSystems Customer Dr. Marcelo Mendonça de Carvalho of Gabinete do Secretário de Estado Adjunto da Administração Local.

Alexandre introduced the RJUE Project (Regime Jurídico da Urbanização e Edificação) and gave the floor to Dr. Marcelo de Carvalho who started his presentation by explaining the new legislation and the Simplex program that prompted the creation of the new municipal portal. The simplification of the legislation and the bet on new technologies that the Portuguese government is undertaking led DGAL - Direcção Geral das Autarquias Locais to build a Project in two phases.

RJUE.jpg

Dr Marcelo de Carvalho explained that the first phase of the Project, which automated the process from the perspective of the Town Halls, has been in production for some time in www.portalautarquico.pt and has already virtualized over 900 processes. The new phase of RJUE has just gone live and is going to automate the end-to-end process for people requesting construction permissions.

Focusing on the Agile practices, Dr Marcelo de Carvalho called the audience's attention to the importance of using sprints in order to ensure visibility over what is being delivered and adjusting the prioritization of the new features to be implemented.

Alexandre Mano closed the presentation by reiterating the importance of the OutSystems Agile Platform and Methodology in the Project and expressed his eagerness to continue to promote new projects using this approach.

Ana Paula of Whatever Consulting spoke this afternoon on "OutPractices: Agile Transformations of any Software Development Process". She talked to us about a subject close to her heart - the Eclipse Process Framework (EPF) which aims at producing a customizable software process engineering framework, with exemplary process content and tools, supporting a broad variety of project types and development styles. Ana spoke in particular on how OutSystems customers can leverage the EPF library to further develop their in-house processes especially when they need to include the use of other non-OutSystems processes or methods.

whatever.jpgFirst, she described the The EPF Agile Kernel - they asked "what is the minimum aspects of a process that make a method Agile?"...and came up with the idea of a Kernel which is the smallest process that you can have. Each agile-related method was broken up into small practices (from whichever method - SCRUM, XP etc) that can then be pulled together and have been made available in the EPF library.
 
Ana spoke about how she has documented the OutSystems processes and added them to the library - called OutPractices - within the SCRUM practice library.  Now people can learn about SCRUM with OutSystems guidance over it - which she believe to be very powerful as the OutSystems methods and supporting technology are based on real project experience and heuristics (and not examples about playing poker).

SCRUM roles were replaced with OutSystems roles and the OutSystems lifecycle has been replicated and documented in the EPF library.
 
Why is this important?  Ana asked us to imagine you are in an environment where you are required use RUP and its part of an RFP you're responding to. How will you do that as an OutSystems customer or partner?  Using the EPF library - Ana suggests that the audience can now select the Use Case practice from RUP and bring that into the OutSystems method.
 
Imagine you find yourself required to comply with CMMI-DEV. (much laughter from the audience here...small Portuguese joke that the blogger didn't understand!)  ...which is considered to be very bureaucratic and difficult to use in practice. So, what do you do? Ana suggested that you don't try and rewrite your method to fit within CMMI - but to leverage the EPF library and OutPractices - and for example, with respect to the CMMI Project Planning /Establish Estimate Practice - just select and add a link to the scoping & sizing task!
 
"What matters isn't following a method - but to deliver. Adapt the process you are working with and improve things as you go."

Can the EPF help organizations sustain and scale agile adoption? Not if it is used to develop new process dinosaurs. But, it can help if it enables your team to ride the agile wave and experiment with one practice at a time.
 
Ana asks the audience to remember the Agile Process Development Manifesto:
  • Scale small process up - over tailoring Big Processes Down. (Start small and add just what you need).
  • Incremental practice adoption - over Full Process Adoption
  • Continuous Improvement - over complete replacement (just improve what isn't working)
  • Open Process Collaboration - over closed process development (tell others when you discover a better way to do things and help the whole community advance!)

This last point seems to be the real crux behind the EPF endeavors - and BTW, blog readers - if any English speakers would like to help Ana in her work to document the Agile processes - please raise your hands! :) 

So, here's a question for our Blog readers - If you are using the OutSystems Agile Approach have you had to incorporate other methods as Ana described - and how did it go?

Hugo Sousa, IT Director of Turismo de Portugal, started out by sharing with the audience his commitment to the business goals of Turismo de Portugal. For that, he showed us his project goals: 

  • Measure and get 90% satisfaction 
  • People are all that matters 
  • Do IT better

This is a very important change in IT, where usually the metrics are measured in bandwidth and server uptime!

turismo.jpg

Hugo pointed out that to do this IT Governance was a must. But because the rules can change and need to be adapted, Hugo stated that what he really needed was Agile IT Governance. After looking at several pre-packaged solutions, Turismo de Portugal picked OutSystems because it was the technology that could provide the necessary flexibility to implement IT rules in a simple and agile way.

By using OutSystems technology and implementing with INOV a centralized help desk system, Turismo de Portugal not only surpassed the 90% satisfaction mark, but was also able to gather data on the submitted incidents and have real time visibility on SLAs and satisfaction status.

Hugo highlighted 3 reasons why Turismo de Portugal picked OutSystems: 

  • What you need is what you get 
  • Change is the only constant 
  • Technology is not the most important thing. People are.

Turismo de Portugal plans to continue using OutSystems to expand their solution to support change management and financial management, and also other important projects not only related to Service-Desk (ITIL).

Our next presentation was by Stefan Meier, Associate Director, Software Development, Information Sciences Department at XDx. Xdx is a biotech company that relies on software and technology for their Molecular Diagnostic Technology. They assess patients who have had a heart transplant and whether they are likely to accept or reject the transplant. They are also working on a clinical study to provide the data to find correlations between genetics and pathology in disease/immune system-related areas.

xdx.jpg
 
Prior to Agile & OutSystems - the development team was 5 developers and 2 SQA and 1 project manager using classical waterfall methods - with 3 Web-based EDC systems for clinical trials, 2 internally developed LIMS applications (1 FDA regulated), several custom query/reporting/maintenance applications and Excel spreadsheets for reporting.

One key problem Stefan highlighted was that each member of the development team used their own chosen environment - Java, PHP, .NET and VB! This degree of complexity and development approach caused lower levels of productivity than they would have liked - for example before OutSystems and Agile, a project that should have taken 4 months took 1 year to deliver.
 
With all the requirements of the business and limited ability to increase the size of the development team, the Xdx IT team decided to create a unified software architecture using SOA and deliver new applications while reducing maintenance costs and developing reusable components.

One of the missing pieces of the puzzle turned out to be OutSystems and the Agile approach. They decided to choose a platform and not the method first...(a little different to most as they did not choose the methodology first). Several reasons - including the need for a rapid development platform to keep up with the needs of their scientists. Another nice side-effect of this choice was that it meant Xdx could side-step the platform wars - and introduced a new option - OutSystems and its Agile Platform.
 
After 15 months and many applications built with the Agile Platform - Stefan noted were several effects:

  • Probably the best benefit: A new way to interact with the business users, because with each demo the users could SEE the app as it was being developed, even in the very early stages...and the tangible results (even after the first sprint) helped build user's confidence and adoption of the idea of Agile within the company.

  • The biggest challenge was unanticipated: resistance of the Agile Platform within the development team itself. The resistance was because of perceived platform restrictions and potential skills deterioration. Stefan said that the second issue is probably more difficult to address - and they did it by enabling the developers to move around different projects. Stefan shared that the "Platform restriction" objection often went away as the developers got hands-on with the platform, although criticism was dependent on the profile of the developer. Stefan categorized the profiles as "The Programmers" who were OK with the Platform because they could get so much more done, the "Hacker Genius" who writes entire apps with 1 line of Perl code - who are likely complain the most and may or may not ever be a convert. And, finally the "Theorist" who just thinks the very idea of using a "platform" is just wrong - they may change their mind after getting hands-on with the technology but not always.

  • Integrating the 2-man QA team with the Dev team - the QA team was classically trained on the waterfall method and FDA approval requires rigorous testing. They tried combining the 2 processes - that didn't really work. So, they tried handing over pieces of the app for testing periodically - this worked to a degree but was uncomfortable for the testers since they didn't like testing a product that was incomplete.The third try was to integrate a member of the QA team with the rest of the team from the beginning of the project and they were able to start testing in the sprints...they were then much happier since they knew about all the decisions that were made during development process. Also - the testers were able to provide important input on how to improve system testability during development. The team's next step is to introduce an automated testing tool for regression testing - making QA even happier!

  • "Agile IS as valid a process as waterfall method in a regulated environment" since documentation is being developed along with the application - however it's important to keep the documentation at the appropriate level of details (e.g. patient care require very detailed documentation). Design reviews are the other requirement - and each demo is used as a formal design review - therefore implicitly fulfilling this requirement through the development process.
 
After 15 months with Agile & OutSystems it is now the de facto standard for building web applications at Xdx. They have built 3 apps (7 production releases) and around 5-6 reusable services. A great success so far!

They are also a step closer to having a unified software infrastructure with reusable services. They have shortened turn-around time from request to delivery - and providing high quality and high impact applications.

Last but not least - the new architecture, approach and tools have enabled consistent data across all divisions through integrated applications - a very important aspect in the clinical trial process!

Have you had any experience of combining Agile and Waterfall methods? What did you think of the XDx team's solution to the QA challenge?

 

Eric ten Harkel, founder and manager of COOLProfs, started this really insightful and humorous look at some provocative reasons a company shouldn't use Model Driven Development: 

  • You want to hide behind technology
  • Producing hours is all that matters
  • Methodology over delivery
  • Your most important goal is management attention
  • Your marketing manager is color blind
  • You are not in the 21st century yet
  • High productivity is a threat

eric.jpg

With over 23 years of model based development using Agile-like methods, Eric took a look at how the industry has evolved and outlined his thoughts on opportunties for improvement. He discussed the outsourcing movement, but stated that the value of Agile and the need for business alignment will kill this for all but the most commodity-based applications.

Eric pointed out that development takes too long and is too hard with current tools like Visual Studio. Although new tools will help the development time, he made the point that the tools in themselves are useless without proper methodology. An answer to this was DSDM. This enabled doing the project in an iterative way, paving the way to Agile. Eric then talked about the psychology of Agile. He highlighted two main points that he believes make Agile successful: 

  • If you're worried and you share the worry, the worry decreases
  • If you're happy and share the happiness, the happiness increases

The winning formula for Eric consists in balancing the methodology, the organization, and the tools. And Eric says that in the future COOLProfs will be using OutSystems as the tool!

The reasons that make Eric love OutSystems are the platform stability, the customer involvement, the ability of the platform to handle large volumes, the scrum meetings, the ability to change systems on the fly, and the amazing quality of its support.

Miguel Barreto, CEO of Home Energy spoke to us next on "Launching a New Company in a Fast and Agile Way" Home Energy is a new company that's part of the Martifer, a Portuguese renewable group. Home Energy was established in May 2008 with a goal of being a market leader in a new space opened up by new regulations related to Energy Certification and Microgeneration (small photovoltaic panels for home use) for the domestic housing market. January 2009 was when the market was going to take off and Home Energy needed to be ready to support a 200,000 housing market.

homeenergie.jpg
A little explanation: new domestic home sales require an energy certification on the Energy Class of their home and measures/recommendations that can be taken for improving energy efficiency. E.g. solar panels, window types and insulation. The Energy Class is dependent how much energy a house requires to keep it comfortable as compared to established benchmarks.

The big challenge was to be ready for a January 2009 launch with a company that was started in May 2008! The Home Energy business plan and strategy relied on strong technical support and had a goal of having a live system in place by October 2008, with just 3 months for development.
 
Miguel described the Home Energy system where a client has to call the call center (or real estate agent partners send in clients through the website) - a team of 50 field agents/consultants are scheduled throughout Portgual to visit the client homes and assess their Energy Class. This information is uploaded to the servers and the experts at home office execute the process to establish the Energy Class - customers then pay for the assessment online, at which point the team is able to make the home's Energy Certification available.
 
While other potential vendors said they could not address all of Home Energy's requirements within the timeframe - the OutSystems Partner Reditus proposal using the OutSystems Agile Platform was chosen because of its ability to address the aggressive timetable, develop rapidly and change while the systems was in production - as new business requirements came up.
 
Although Miguel was initially skeptical on the flexibility of the tool and how easy it would be to change things -he was very pleased with how it worked in practice. He felt that the multiple sprint approach enabled the business team to get a really good feel for the application as it was being developed -allowing them to make improvements while it was being built and ensure it addressed their needs.

Miguel showed a number of very cool screenshots of their complete application - including  integration with GPS systems for home location and aerial pictures of the house; the ability for consultants to draw on house maps, and assuming enough information...almost automatic generation of the certificate for the clients. Built with a team of 8 people in the first 3 months, this fully integrated system went into production on time and Miguel and team were extremely happy with the outcome.

Miguel wrapped up with a set of their key findings:
  1. A good RFP that focused on key user needs was critical - even though things have changed since.  Approx 70% of the original RFP was implemented - the other 30% were "wish list" items that the team realized they didn't really need...and were subsequently replaced by another 50% that came from market changes after the initial system was implemented.
  2. Short rounds (sprints) of demos with key users were extremely important, establishing a good working relationship and interactions between users and technology team.
  3. Flexible tools facilitate and enable entrepreneurial flexibility - a very important point that underlies the overall success of this case study.
  4. "Custom is better and more efficient than standard approaches" - Miguel's past experience with a packaged or standardized approach is that it became very difficult since the package too much functionality than was needed for the business users - but he felt that custom builds were possible without huge expense - even though they meant potential rough starts.
  5. The development team was dedicated to this project and their spirit and proactivity was very important for ultimate success - where they focused on the end result and drove overall success.
This is the second case study where we've heard about how changes in economy or regulation open up new market opportunities - for those who are the most innovative and nimble (the other was Andries Schilt at Main Energie) - are you seeing the same thing happen in your industry? What technologies are you using to take advantage of the opportunities?

Nuno Teles, Service Operations Director at OutSystems, launched the afternoon here at track 2 by talking about the challenges of scoping and sizing an Agile project. Agile projects are not based on lengthy specifications and piles of documents. Instead, they are focused on a clear business need and on understanding and designing the simplest effective solution to address it. The challenge consists of sizing a project based on fuzzy and high level requirements.

At this point Nuno did a demo of the OutSystems Agile Network, where he showed an entire project scoped in the web interface. To illustrate how scoping works, Nuno added a new story and some features to the project. When it came to sizing, everyone was amazed at how easily Nuno selected key parts of the story text and turned them into planned action items.

teles.jpg

According to Nuno, OutSystems uses a long proven sizing methodology, developed, refined, and revised over 3 years and more than 400 projects. The methodology process consists of gathering requirements, organizing them into modules and drilling them down just enough to get an accurate sizing with an acceptable risk. To ensure transparency and alignment, all steps are made in close cooperation with the customer.

Nuno also added that having customer participation from day one is also a great way to ensure the Agile Methodology kicks in. The collaborative discussions during the sizing process naturally flow into backlog and sprint management performed during the project. At this point he urged the audience to try the sizing tool for themselves, by registering for a free trial of the OutSystems Agile Network!

Next up at NextStep - Marteijn Mout who is the project managers of the 'New meter market model' at E.ON Benelux. E.ON is one of Europe's largest Energy providers with over 30 million customers in 30 countries.  E.ON Benelux has around 270,000 customers and they have been a customer of OutSystems since 2004.

eon.jpgThe project that Marteijn talked to us about during this session was to support the new Government regulation which demands that Suppliers will be responsible for the collection and validation of meter data of smart meters from 2009 and for traditional meters from 2010. He shared a great deal of information about how E.ON developed their solution using Agile and working with OutSystems, SAP and other partners.

Describing the team's experience of using OutSystems Agile approach he told us that:
  • They started with 5 iterations (sprints), with a period length of 2 weeks
  • Sprint 6 was added to address new change requests
  • Weekly progress reports with 2 demo's after every sprint and 2 week testing periods after demos
  • Change Management requests were registered in OutSystems Agile Network (OAN), ECT and assumptions documented
Key challenges that the experienced:
  • They were initially skeptical of the OutSystems size and scope estimate for the project - but happy that the results were delivered as expected.
  • Intensive collaboration - Marteijn quipped that "I'm not sure how many emails I received from and sent to the OutSystems team - but there were a LOT. It wasn't bad - but was an indication of the degree of collaboration!"
  • "We had some initial challenges on combining Waterfall and Agile methods - especially in planning - we were lucky that OutSystems' approach was flexible on that front, and we were able to combine planning into a single planning/test plan."
  • The greatest issue was they found was the temptation to keep adding new requirements - and it was important to keep that reigned in where possible.

End results of the project were a success!

  • The Customer Portal and underlying SMDR "engine" meet all requirements and more!
  • OutSystems were a good sparring partner for architectural and functional matters
  • OutSystems were flexible as promised (planning/adaptability)
  • Communication lines efficient, effective and sound - even with a LOT of emails ;)
  • Realistic planning/sizing and no budget overruns
  • The Agile approach and technology is a big success factor for the project!

How are you coping with the amount of inter-team communications that's required by Agile - what tools are you using?


This morning's last presentation on track 2 was delivered by Rui Afonso, OutSystems Channel Manager at Hyfas. The presentation was about Hyfas success story at Refrige. 

Refrige had a very complex material creation process, that spanned across 7 distinct departments. Communication was made by email and Infopath, and at the end of the process the IT department would copy the gathered information into SAP and BASIS. The IT department had to confirm all the data, and sometimes this resulted in having to request missing inputs from information owners.

hyfas.jpg
Hyfas considered both SAP and OutSystems technology to implement their solution. They picked OutSystems because it was faster (half the time of doing it in SAP, according to Rui), provided a reusable framework for future projects, and because everyone was talking about OutSystems and how good OutSystems applications worked!

Rui talked a bit about how the project went and mentioned that even though the process was still under construction, using OutSystems made this a non-issue. He also pointed out that the main trouble with the project resided in the integrations with SAP, and gave the audience some very good advices for such integrations. The advices included making sure that you have an SAP expert available, checking all the SAP processes and BAPIs both inside and outside the SAP environment, and being very careful with custom SAP developments.

For wrap-up Rui showed some screen shots of the application and explained how they extended the information available in SAP to overcome some shortcomings of the old system. He also share his experiences on using ECT, and gave some highlights on how ECT improved the final product:
  • End users had their requests met in hours
  • Bug fixing was much more effective
  • A number of issues were fixed before some users noticed the issue was there!
  • Central change management, without having to call or email the development team

Rui then gave the mic to Sérgio Almeida, Project Manager at Refrige, for his customer testimonial. Sérgio emphasized once more that SAP expertise is paramount. He also mentioned that he was very pleased with Hyfas commitment in, not only delivering a solution, but a solution that works really well for the customer. Sérgio ended up stating that the project went really well and shared some of his experiences with an Agile project. He finished up by staying "if it's up to me, I'll continue to do projects in OutSystems".
In this NextStep session Pedro Rosa Santos who leads the consulting services team for Keep it Simple, an OutSystems Partner, addressed how Dynamic Business Applications can play a big part in the Insurance industry.

Pedro described the quantum leap experienced in the Insurance industry from 2005-2008 as it tried to deal with market demand for new products, online self service, the need for real-time information exchange with agent & broker channels and the drive to invest in new technology in order to reduce costs. The problem, Pedro explains, is that this has created an extremely complex IT environment for most Insurance companies around the globe - and the goal of building an infrastructure that is responsive to market needs - actually started to have the opposite result - preventing responsiveness!  

kiss.jpgTo address the need for a responsive infrastructure and maintain low TCO - The Keep it Simple team are working with insurance companies to implement a Service Oriented Architecture (SOA) and build certain aspects of the systems as Dynamic Business Applications. They recommend to the insurance companies they work with (and which is probably applicable to the audience in other industries) the following:

Pedro describes Dynamic Business Applications as applications where you can change business rules or change the front-end extremely rapidly - in a couple of hours or a couple of days. In order to move forward in this way, Pedro recommended the following steps:

  1. Identify a back-office dynamic business application
  2. Migrate business logic and rules that can provide functionality to other services (like portal, CRM or BI)
  3. Portals, product pricing & management + claims management - adapt them to be changed easily, on a dialy basis and delivered to the end-user.
  4. Bring business process and business rules from the portal to the back-end, and make available to the portals and other apps.

"Portals should be built as Dynamic Business Apps, built with technologies like OutSystems - which can enable rapid change."

Pedro and the Keep it Simple team recommend that their customers and (probably applicable other industries)

  • Improve your organization's time to market
  • Use Agile methods get closer to end-user and address their needs
  • Identify which components should be embracing change. You don't have to change everything all the time, but some systems need to adapt to change faster than others.
  • Invest to consolidation of  IT IS around Dynamic Businss Applications.
Have you heard of Dynamic Business Apps and Lean & Agile Development - what do you think of it? Will it work for you?

Afonso Metello, founder and managing partner at Epopeia, kicked off his presentation by showing a video of the Report Studio, the tool that allows users to easily design their reports in the Agile Reporting Services solution.

epopeia.jpg

The Agile Reporting Services is a unified business reporting solution that covers the full report life-cycle, and it is seamlessly integrated with the OutSystems Agile Platform. This solution tackles a series of challenges other tools fail to address, in particular:
  • Fast change
  • Easy to use for non-tech users
  • Impact analysis (i.e. understand the exact consequences of publishing a report)
  • Self heal (i.e. adapt to changes in the underlying model)
Afonso explained how the Agile Reporting Services totally integrates with the Agile Platform, enabling users to design, deliver and manage reports in a environment familiar to  OutSystems users. He also showed some screen shots of an OutSystems application that included report and charting widgets provided by Epopeia's solution.

During Q&A, Afonso stressed that all reports are built on top of the data made available by the OutSystems platform. This means that - on top of built-to-change capabilities - the reports will also support easy staging from development to production.

The Agile Reporting Services solution is about to go to beta in some selected customers, and is currently undergoing OutSystems Certification.
The "Agile Delivery Experiences" track was kicked off by Rosa Mimoso, Director of Global & Support Systems of Caixa Seguros.  Rosa shared how Caixa Seguros e Saude,Portugal's largest insurance group used Service Oriented Architecture (SOA) and OutSystems Agile technologies to address their extremely large and complex business and technology environment (millions of customers & claims, 4 companies, 5 brands and hundreds of legacy apps.)  

caixaseguros.jpgRosa told the audience how they decided to break up their complex environment into 3 layers - Front-end, Services and Core Systems. They used the Agile Platform to enable their channel portals for customers and brokers. This was supported by existing services in the SOA architecture. OutSystems' Agile Platform is also exposing reusable services to other applications in their environment.

Rosa described the benefits that SOA & Agile brought to Caixa Seguros e Saude:
-A single point of access for all solutions
-Formally documented services supported by WSDL
-Real time control: centralized logs & reporting; performance indicators and alerts.
-Simplified management of multi-channel configurations, dynamic content and a common security model
-Faster component upgrade
-Simplified B2B Integration

Rosa wrapped up her presentations with the Caixa Seguros e Saude team's 5 key findings:
 
1.The systems in different layers need to be able to evolve at different speeds.
2.Integration needs to be independent from system evolution
3.New systems need to be introduced smoothly and without disruptions
4.This approach requires a paradigm shift in the core systems classification
5.Technology needs to allow Business and IT to be aligned.

Track 2 started with a great presentation by Pedro Gama, Account Manager of Glintt. The presentation focused on how Glintt used the OutSystems platform to deliver a factoring solution to Finanfarma, a Portuguese Factoring society created by ANF. (If you want more information about factoring, the Wikipedia is a good place to start)


glintt.jpg

Pedro began by handing the mic to Fernando Malosso, responsible for the commercial area of Finanfarma. There's nothing better than having the client talking for you! Fernando did an introduction to the challenges and complexity of the factoring business, stating that IT agility was paramount. As Fernando put it "each case has its own nuances".

Pedro returned to the podium and explained the major challenges Glintt faced for this project:  

  • Short time to market
  • Very dynamic and heterogeneous business model
  • The needed to quickly integrate with other systems
  • The ability to perform complex financial calculations

Glintt ended up delivering a very sophisticated solution, totally implemented in OutSystems. The numbers speak for themselves: 12 applications, over 100 web screens, more that 150 database entities, and a lot of very complex business logic was implemented to support this solution.

According to Pedro, the project had an initial estimate of 3 years with 6 consultants, assuming the use of traditional technologies. By using the OutSystems Agile Platform, the project was done in 1 and a half years, with only 2 consultants! One key point that Pedro mention is that this was only possible because of Finanfarma's strong commitment!

For wrap-up, Pedro Gama mentioned that the use of the OutSystems Platform simplified the implementation of the complex business logic, provided a way to quickly respond to business changes, displayed good performance when dealing with large volumes of data, and addressed continuous change in a very efficient and cost effective way.

Mike Jones and Carlos Alves of OutSystems got the audience's brains thinking with a discussion on "Changing The economics of Application Development" with a set of questions:

"Can a company really innovate in today's economic environment?" - they think "yes", and gave examples of how new ideas are coming up from the business, they are small but they are making a significant difference to business success - however, they may need custom built software (not packages) due to the need for speed and flexibility.

whatrole.jpg

*"Is it all doom and gloom?" *- the guys argued that NOW is the right time to innovate and get Agile. They challenged IT teams to be ready for whatever comes next with the economy -and suggested that the only way for the Audience and their businesses to not only survive but thrive, is to get more Agile.

"WTBWITD?" - Mike joked with the audience that this wasn't really easy to pronounce and needed some marketing spin - but "What The Business Wants IT Delivers" Carlos said, is the essence of Agile which is basically "a systematic approach to accommodate innovation"

"What is Lean?" - the process to making sure IT delivers what the business needs - Agile is the secret to becoming Lean.

"What is Agile and how is OutSystems different?" -Industry agile projects: iterative development with 4-6 week sprints, continuous business participation and deliver vertically integrated solutions at the end of each sprint.

-The OutSystems Agile Approach: able to pre-size the project with high accuracy; time-box principle, smaller up-front analysis and more prototyping; 2 week sprints that deliver vertically integrated solutions at the end of EACH DAY. Leverage SCRUM practices.

A great question came from the audience about how to become MORE agile when your team is on the other side of the world and difficult to reach - they are doing 3 month sprints...which is not Agile, its waterfall.

Answers from the OutSystems team: The first issue is likely to be the lack of commitment from the business side to attend the regular weekly sprints. The second is that they need to have a business sponsor with authority who attends the regular sprints. Final suggestion - to ensure that an Engagement manager is local to the business-team, and that the Delivery Manager and the Engagement Manager are in constant communication.

Wrapping up, Mike and Carlos challenged the audience on "What role will you play in today's economy? You have two choices: put your head in your hands and hope it all goes away or take the opportunity to embrace change and innovate."

Wise words that we can probably apply to all our lives in these uncertain times.

Welcome to day 2!

| No Comments | No TrackBacks
Day 2 of the Next Step is about to start! The weather is great and people keep streaming into the show floor, waiting for the 1st morning sessions.

Maysoon and I will be blogging from today's track sessions which are split into those about the "Agile Delivery Experience" with customers and partners talking about their Agile projects and learnings - and the "Agile Platform Techniques" track which is more focused on technical best practices, hints and tips.

We'll keep you posted!

ccb_flags.jpg

Andries Schilt, Operations Officer of MAIN Energie, gave us an inspiring look at how their company, which started from scratch in 2003, and has gone from nothing (an old kitchen table and a second hand laptop) to an award winning, 100 Million Euro, Energy provider in the Netherlands, servicing 45,000 customers with just 30 hand-picked employees and extremely savvy use of technology!

On hearing this - you could see the audience all lean forward to learn how they had achieved these impressive results.

andries.jpg
Andries told us that they are one of the remaining privately held Dutch Energy companies who found a niche market - providing Energy related services to the Real Estate market in the Netherlands. This market has some specific needs which other Energy companies have not been able to address, allowing Main Energie to step in with both business and technology agility - the power of Agility2.

So - how did they do this? Andries spoke about 2 key ingredients for their success:

1) Business Agility - where they took risks, learned from mistakes and adapted quickly to changes in the market. Having business agility in their blood means that the Main Energie team are willing to do things differently from their competition, and are constantly innovating.  "Business agility is in our DNA, otherwise we would never be able to survive."

2) IT Agility - Andries told the audience that Business agility is not enough because an agile business demands that its IT is also agile. IT agility for Main Energie means having a team of qualified professionals who strive to win - who have the right tools, environment, agile processes and procedures, and of course agile IT - which, in turn means fast time to market. Delivering new IT services and applications in weeks instead of months or even years. In an example he told us of a Sprint (#8) that was due out in July this year...it was to manage their energy portfolio. Due to the sudden changes in oil prices however, almost overnight, the business priorities were changed, and this became a high requirement - and moved to Sprint #3. The OutSystems & Main Energie team has just completed sprint # 2! Well, Andries credited the Agile Platform, the agile OutSystems delivery team and the Main Energie business agility to the fact that this important application is now almost complete and ready for production.

The real learning to be derived from the Main Energie experience is that Business Agility combined with IT Agility is where their REAL power comes from - adding a new dimension to Agile - Agile2.

I loved this quote from Andries "If someone says that Agile is not right for my business - then they have something wrong with their business."

Paulo Rosado, CEO of OutSystems, kicked off the conference with a thought provoking keynote arguing the idea that ‘IT doesn’t matter’ and is just a commodity was incorrect and described how and why IT is in fact the source of competitive advantage for many leading companies. He also warned the audience that because every good idea is eventually copied -eroding any competitive advantage - continuous innovation is imperative.

paulo.jpg

He cited several interesting examples of companies using their IT systems to create distinct competitive advantage: a mass retail company using IT to develop customer intimacy; an Insurance company decentralizing 98% of its business transactions through their IT systems - resulting in fully empowered agents, and in turn attracting the best agents in the market; and he introduced Main Energie, the next keynote which we will also be blogging on…who is the epitome of a company using IT for competitive advantage.

At this point, Paulo turned to 4 industry trends which he believes will reinforce the notion of IT as a source of competitive advantage and which are key to the OutSystems go-forward vision and strategy.

I’m pretty certain this will take a white-paper to describe - but here are some highlights…

#1 - the acceleration of Agile adoption: citing many examples of the Agile adoption ramp in the market, defining “Agile” and addressing the common “Agile is OK, but not for me” statement. An interesting discussion here on the difference between 1. software product organizations with established budgets, product managers, stable teams and planned design - who are doing well with Agile, and 2.Enterprise IT organizations with limited budgets, business users, shifting teams and unpredictable requirements. Paulo described how the OutSystems approach to Agile has been developed around the very different needs of Enterprise IT and how to make Agile practical in their environment - resulting in WTBWIWID (What The Business Wants Is What IT Delivers)

#2 - the rise of Business-savvy IT and IT-savvy Business users: Paulo described how a new generation of tech savvy business people are now forcing IT to become more business savvy and driving a trend toward new roles in the IT App Dev world…which Agile is further consolidating. This trend is being addressed at OutSystems through the Agile Academy and Agile training & certifications.

#3 - the world is flat (and getting flatter everyday): Paulo gave us an example of a customer who has development teams spread around the globe and looking to expand the team to the Asia. Probably a more and more common scenario. This flattening demands a different type of approach to Agile and different technology enablers. Here Paulo hinted at the Cloud and how that would figure into OutSystems’ upcoming releases of its Agile Platform.

#4 - the Process-driven Enterprise: the fourth and probably most significant trend, Paulo said is not a trend, but a reality. Enterprises have to address how business process fits into their IT strategy and he told us about how OutSystems has been working with its largest process-centric customers for the last 18 months to figure out the best way to help address process within the context of Agile. Here Paulo indicated that the upcoming releases of the Agile Platform are likely to tackle some of the key challenges of traditional BPM (i.e. big-bang approach with large upfront investments, and the disconnect between process & applications which prevents rapid adaptation to change.)

There you have it - 4 trends that are supporting how IT can be a source of competitive advantage…and the audience all seemed to agree with all the vigorous nodding of heads!

Lisbon is beautiful and sunny - and 257 (and counting) registrants just streamed into the CCB auditorium for the first keynote presentation of the OutSystems NextStep ‘09 conference!! It really is shaping up to be a huge Agile event!

More very soon…

handout.jpg

nextstepPANORAMICA.jpgWelcome to the OutSystems About Agility blog!

We decided that a good launch point for this blog would be our Annual User Group conference, nextstep'09, where we are bringing together Agile practitioners from across the globe to discuss all things Agile.

This year's event is taking place on April 15 and 16 in Lisbon - and since the economy has curtailed many people's travel plans, we want to keep everyone up-to-date on the conference proceedings no matter where they are in the world.

With over 300 attendees already registered, this Agile event is shaping up to be a cracker!

The conference will be a unique opportunity to learn about Agile in practice - tools, techniques, best practices, case studies and the latest in Agile technology. We will be blogging in real-time from the keynotes and all the tracks and sessions which are being presented by customers, partners and the OutSystems team.

If you cannot attend the event, we're sorry to miss you in Sunny Lisbon, but hope that we can bring you some flavor of this year's nextstep'09 through our About Agility blog.

Let us know what you think!

Stay tuned. More soon.

Agile Platform

Build your next great Web App today: Take a tour of the Agile Platform