Skip to Content

Many of you want to know best practices for create Visual Composer Applications in an efficient way, but as Mario Helger say in his book, “Modeling is an art, with any art, there are many ways to do something … “ so, now a question come into my mind, which is the most efficient way to develop a VC application ?

There is no answer for it, Visual Composer is a wide open tool that allows developing highly customizable Portal applications rapidly and without writing code, at the end a Web-based visual modeling tool provides the chance to “paint” your application as well as you see it in your mind.

Until now you have the best way to develop the application in your mind, now you need a methodology that help you to deliver it on-time, by passing all the quality controls, performance checks and fulfill the end-user expectations, for this purpose i recommend you to use SCRUM, why do I recommend it to you?, because we use it and the results are excellent!

Thanks to Hamid Shojaee, now you can have a look on this video and understand SCRUM in less than 10 minutes, I really hope you like it and based in my experience I can tell you that this is the best way to deliver a Visual Composer based application on-time.

Enjoy the video:

 

To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Twan van den Broek
    Hi Luis,

    Thanks for sharing the video, good stuff.

    This week I started the next phase of our project, we are applied the Scrum approach as well (SAP Scrum: An agile approach to deliver what is really required).
    I am interested in your experiences within SAP projects. For example: How to deal with all the SAP specialists in a team who probably did not have a full time job in a sprint?
    Or any other experiences that are typical for doing Scrum in a SAP project.

    Kind regards
    Twan

    (0) 
    1. Luis Felipe Lanz Post author
      Hi Twan,

      SAP is doing SCRUM since 2006 as part of PIL (Product Innovation Lifecycle) , we have several (more than 200) projects experience, and use some tools that helps to get the right implementation of it.

      However the usage of SCRUM at SAP deserve it own blog, so let me go directly to your question:

      – How to deal with all the SAP specialists in a team who probably did not have a full time job in a sprint?

      As SCRUM Master you should take into account those cases, if more than 25% of your staff is in this situation you are in a critical path, if less you have to make shorter cycles to get less task and make an effective usage of the members.

      So you can use the List of all (six) Scrum phases with them and enable a direct communication channel, trying to check it on the daily meetings.

      Hope this helps.

      Cheers,
      Luis

      (0) 
      1. Twan van den Broek
        Hi Luis,

        Thanks for your answer. Initially I was thinking to plan sprints of 4 weeks, due to complexity. But taking into account ‘dealing with future changes’ and your recommendation, I now think of planning 2 week sprints.
        Next week we will deliver the product backlog and then we will start our first sprint. I feel a blog coming up 😉

        Kind regards
        Twan

        (0) 
  2. Dagfinn Parnas

    Whilst the video is a good introduction to Scrum, I disagree with some key points in it. I am myself a certified scrum master, am involved in introducing Scrum in a large company and currently working in a Service Management scrum project. Whilst I do not consider myself in expert in this area, I’ve had enough philoshopical debates to have a strong belief in Scrum and understanding of the core reasons why Scrum has proven itself.

    (0) 

Leave a Reply