Wagento News

  • Acquia/Magento partnership: content and commerce combine

    Editors note: This blog post was first featured on DBM.today and was originally posted on November 3rd, 2016

    Acquia and Magento Commerce have joined forces to integrate Acquia’s digital experience portfolio with Magento’s commerce and fulfilment solutions.

    This integration of open-source content and commerce solutions is intended to enable global brands and merchants to take control of the customer journey and deliver highly personalized, content-rich experiences across every touchpoint.

    “Acquia and Magento combine the best attributes of open-source development — agility, speed, innovation and security,” explained Acquia CEO Tom Erickson. “Together, we’re putting the power back in the hands of merchants and brands to allow them to control every pixel of the experience throughout the customer journey.”

    The partnership is promoted as offering B2B and B2C merchants:

    • Personalization at scale: Contextually optimized real-time experiences across the entire customer journey, regardless of device or channel
    • Speed to market: Rapid deployment and management of content-rich commerce experiences
    • Empowered marketers: Allows marketers to own the customer experience and collaborate more closely with merchandisers
    • Flexible integration: Unlimited flexibility to meet any market need or technology configuration

    Magento Commerce CEO Mark Lavelle commented: “The combined power of our respective technologies and our thriving global ecosystems will allow our customers to drive unbridled innovation, engage consumers like never before, and pave the way for the commerce experiences of tomorrow.”

    To enable the solution, Acquia and Magento will integrate the Drupal CMS and Acquia Lift solutions for personalization with Magento’s commerce and order management products to unify content, commerce and context across the customer journey.

  • Things Change - The Fix Bid Project

    ever-changing-project

    Things Change

    by Brent W. Peterson Directory of Customer Experience.

    A continuation of my Customer Experience series. At the end of the day, the client wants to have their website completed in the way THEY want it. The trick is when you start your project things change. Things change and whoever starts a project as a fixed bid and will hope to come to the end of a project with what they started is only fooling themselves. Things change from the client perspective and things change from the agency perspective. The bottom line is that these changes will affect your project and the sooner you can wrap your head around this concept the more successful your project will be.

    The Basics

    Client wants something -> Agency delivers something

    The success or failure of a project resides in the middle of these two things. What we can do now is to continue to break down the high-level items in any project. From these items we can ask questions about what is important to getting from A to B. How we navigate that road and how we report where we are and the road blocks involved will determine the success of the project. Let me add that the length of the road and the amount of work that needs to go down the road will also contribute to the success of the project. If the project is projected to last 2 years there is a much higher probability of failure than a project that will last only 2 weeks. The ratio of work to time is an important number to look at. The risk of a lot of work and a short amount of time is that something has to be given up. One cannot simply deliver everything in a given time when it is impossible to do everything in that time.

    Let's break down the project at a high level

    • Client wants something
    • Client communicates to agency what they want
    • Agency digests what they want to communicates back to client what they will do and how long it will take to do it.

    The “want” in a project is not always 100% to everyone. The “want” is sometimes all determined at the beginning but most likely wants will trickle out during the project. This is the biggest reason why Agile is the best approach for project management. So the next question is “How do I translate what the client wants into what we are going to do?” This communication is the key to the success of the start of the project, but continued communication and a partnership point of view is how the project will finish successfully.

    The how long it takes to do it is a number that will cause great contention later in the project. Why? Because what the client expects will be done may be different than what the Agency thinks they want. To further complicate things we have time that is lost because people need to eat and sleep and we have weekends and vacation. So 80 hours of work doesn’t necessarily mean it will be done in two weeks. It is the responsibility of the agency to communicate that the time to complete the 80 hours will be compounded by the fact that there may be a time that work goes through Q/A and the Q/A team will need time to review and look at tickets. (This is just an example, but there are many other factors that will contribute to this time) What we do know is that we can come up with an average of how long it takes to complete 40 hours of work. An example is the following:

    40 hours = 5 man days. The 5 man days will take unto 15 days to complete because each item that makes up those 8 hours of daily work must be reviewed by a project manager, worked on by a developer, Q/A by a technician, code pushed around by a DevOp and reviewed by the client. All these steps assume that everyone will take them in serial order. The client can argue that the agency can simply put more developers on a project. So theoretically a 40-hour job could be done by 5 people in one day. This assumes that the client also has enough people to review the work being done in that day and that the work CAN be done in parallel. It is at this point that the agency has the responsibility to communicate truthfully to the client that something CAN’T be done in the timeframe the client requests.

    Next week we will dive into the Client.

  • The Wagento Approach to Customer Experience

    customer-experience The Customer Experience

    Wagento’s Approach to Customer Experience

    by Brent W. Peterson Directory of Customer Experience.

    To start off this will be a series of blog posts that will last a number of weeks. The title is not meant in anyway to say this post is the end result of all our customer experience!

    To this we have learned our first lesson. Aligning Expecations. When I first published this I was told that the complete guide surly can't be a couple of paragraphs! So to help everyone understand what I am doing and what I am trying to accomplish we will walk through a number of stages in the experience and then dig deeper to see what we can learn. Along the way I would be eager to hear your feedback. This will help to shape our experience together so it is not just Brent's experience but the experience as a community. I did notice I say this at the end of this post, but some of you may stop right now and not read any farther.

    For the last couple of years I have been fixated on making the customer experience better and more specifically making it better within a project and with our project managers. It started back in 2014 when I gave a presentation at Meet Magento NYC about the idea of an open source agency. This theory looked at the idea that we share our knowledge on open source software, then why can’t we share our knowledge with our process for running an agency. Were there so many things that were proprietary that it meant we couldn’t talk about these things? If you would like to see my talk in Germany here it is:

    The talk lead me to start asking questions of our own process and my next presentation was wrapped around the “Awkward Conversation.”  When I gave this presentation at MagentoLive Germany I thought I would address it to merchants who would like a better understanding of how a developer or agency interacted with them. If the success of a topic can be measured on questions asked, my topic was successful. In fact, my wife was sitting in the audience and a merchant leaned over and mentioned that he had not thought about this but this is very helpful. What was more surprising was that the majority of the questions from the audience came from developers.

    For Magento Imagine in 2015 I submitted the same idea with a slight twist. I would focus equally on the merchant and the agency. Giving each equal weight. With this balanced approach, I thought I could speak to both the merchant and the developer/agency and hopefully raise some ideas that would resonate to everyone in the audience. After this presentation nearly all the questions came from developers. This could be the audience that I was put in, but what it told me is that there is a disconnect in what we as developers or agency leaders think customers want and what the customer wants.

    Over the next weeks, I will outline my thoughts on Customer experience within a project.   I would like to foster an open conversation on what works and what doesn't work. You can comment freely on the post or email me privately.

  • We Are Magento: Imagine 2016 Highlights And Recaps

    Magento Imagine 2016 has wrapped and it appears that everyone survived! Albeit a little bit tired and a little less money in the bank, it was otherwise a success and a great time! The theme this year was "We Are Magento" and it was embraced by all who attended. This was Magento's first Imagine as an independent company so it was exciting that they celebrated the diversity, creativity, and shared passion of the thriving global community of engineers, entrepreneurs, investors, and inventors—from the trailblazing merchants who know exactly the kind of customer experience they want to create, to the technologists and innovators who help them realize their vision. Magento made some important announcements about how Magento Commerce continues to innovate to support this global community. Of course Magic Johnson wowed the crowd Tuesday night, and the parties are always fabulous, but here are other key highlights. Enjoy!

    Magento News

    Recognizing Excellence Across Our Ecosystem

    Imagine is all about recognizing the best among our merchants, partners and developers. We kicked off with awards for our incredible Magento Masters, representing the 20 most active members of the Magento developer community. Our very own Brent Peterson is right in the middle of the picture in a bright blue shirt!!

    Magento Masters

    At Imagine 2016 we talked a lot about the trailblazers of commerce. We honored the winners of the 2016 Imagine Excellence Awards, recognizing the exceptional creativity, innovation and success of merchants across the global Magento ecosystem. These trailblazing merchants who are conquering the wild country of commerce with Magento inspire us all.

    Fun Stuff and Events

    #PreImagine Cocktail Party hosted by @interactive4’s @ignacioriesco, and @magentogirl Fun was had by all!

    The Big Dam Run - which was hosted by Wagento. Rumor has it that the run was the best part of Imagine ;)

    Big Dam Run

    Lots of exciting things are happening with Magento over the next year - Cloud, B2B, Magento 2.1 (to be released in June), plus lots more! Everyone walked away from the conference with an energy and an excitement to improve Magento further and bring better technology and features to our clients sites. Here's to 2016 being an amazing year for Magento and our clients and always looking forward the next Magento Imagine! :)

  • Magento Marketplace – the Official Magento Extension Store

    Magento is excited to announce that Magento Marketplace, the new Connect – and home of all things extensions related, is now live!

    Did you know that Wagento Commerce helped launch the new Market Place portal?! Yup, that's right. HUGE thanks and shout out to our AMAZING Developers, Project Managers and Leadership, otherwise none of this would have happened without you :)

    What’s new in Magento Marketplace?

    • Less cluttered store and smarter search and browse functionality to find extensions faster and easier
    • Curated user experience to create more opportunities for your products to be discovered
    • Technical, Marketing, and Business Value reviews to ensure quality extensions
    • Better inventory management and more exposure to customers
    • Additional promotions and demand generation provided by Magento

    When we set out to build Marketplace, we had core principles that we wanted to achieve. We wanted to show off the amazing work that the ecosystem of Magento developers have created over the years. We have worked hard to ensure that Marketplace represents the best that the Magento community has to offer.

    To learn more about how to submit your extensions on Marketplace click here. We are looking forward to working with you to make Marketplace a success.

  • Magento 2.0 Delivers Significant Performance and Scalabilty Gains

    New white paper shows Magento’s next generation platform handles up to 39% more orders per hour and delivers nearly instant server response times for catalog browsing.

    Magento 2.0 was designed to meet an ambitious set of goals: offer unmatched flexibility, enable a faster time to market and easier upgrades, reduce total cost of ownership (TCO), and provide new functionality, while also delivering better performance and scale out-of-the-box.

    Magento 2.0 achieved these goals with a more open and modular architecture and a comprehensive set of performance and scalability enhancements that:

    • Optimize web pages for faster delivery
    • Accelerate server response times for all site activities
    • Increase efficiency for backend operations
    • Boost database flexibility and scalability to handle peak loads

    Benchmark testing comparing out-of-the-box supported and recommended configurations for Magento Enterprise Edition 2.0 and Magento Enterprise Edition 1.14.2 show that the Magento 2.0 platform consistently outperforms the Magento 1.x platform across all metrics and use cases. A sampling of the findings reveals that Magento Enterprise Edition 2.0 can:

    • Process up to 39% more orders per hour
    • Deliver nearly instant server response times for catalog browsing
    • Enable up to 66% faster add-to-cart server response times
    • Provide up to 51% faster end-to-end checkout times

    To learn more about the Magento 2.0 performance and scalability enhancements, recommended product configurations, and benchmark tests, download our new “Magento 2.0 Site Performance and Scalability Optimizations” white paper.

  • Magento Pre-Imagine Race 2015

    Magento Imagine 2015 is just around the corner. We absolutely love being apart of the Magento community and love to engage the Magento community through running. That is why Wagento is, once again, organizing the 2015 Pre Magento Imagine run in Las Vegas. This year Findlay Chevrolet is holding a 5K run 1M walk called the Findlay Classic. If you are attending the Magento Imagine Conference we would love for you to join in on the run.

    This is a great way to get involved with the Magento running community and to get in your desire to exercise while traveling.

    Registration is a two-part process:

    If you would like to join us and get the Magento Running Team Race shirt sign up here. Depending on the numbers we may be getting a bus or limo to the race. Please indicate if you will need transportation.

    To register for the race itself and for more information on the race details, including the course map and location information go to Active.com. Be sure to indicate that you’re a part of the Magento Running Team! This will allow us to pick up your race packet ahead of time. For more information on the Findlay Classic 5K, please visit this link.

    If you are interested in sponsoring this event and would like more information please contact susan@wagento.com.

    Magento Imagine Run 2015 Banner
  • Why no one should use FTP for team development

    FTP has been the most common way for developers to access a website but is it the best?

    Wagento uses a process called "Continuous Integration" This allows for a group of develpers to colaborate on a single project. Wikipedia lists the following advantages

    • When unit tests fail or a bug emerges, developers might revert the codebase to a bug-free state, without wasting time debugging
    • Developers detect and fix integration problems continuously — avoiding last-minute chaos at release dates, (when everyone tries to check in their slightly incompatible versions).
    • Early warning of broken/incompatible code
    • Early warning of conflicting changes
    • Immediate unit testing of all changes
    • Constant availability of a "current" build for testing, demo, or release purposes
    • Immediate feedback to developers on the quality, functionality, or system-wide impact of code they are writing
    • Frequent code check-in pushes developers to create modular, less complex code
    • Metrics generated from automated testing and CI (such as metrics for code coverage, code complexity, and features complete) focus developers on developing functional, quality code, and help develop momentum in a team

    In more simplistic terms it works like this:

    1. Developer works on their local Machine and they push updates to the repository.
    2. The work is checked out on the dev site for review - The Q/A team then reviews and approves for client to review. If things look for from here it goes to Staging.
    3. The code is deployed to Staging using DeployHQ where the client approves the work. Staging is the closest thing to production so we can see items in near real time.
    4. Once everything is approved on Staging then the code get deployed to live and checked again. The deployment process offers the ability to roll back if needed.

    In some cases, before a site goes live we may only use one or two places for testing. But once a site is live and in production the before mentioned procedure is used. Once the site goes live we turn off FTP and do not let anyone modify code on the live site.

    You may ask why? Why do we do this process?

    Scenario #1 (Most common) Third party developer installs feature on live site without putting code into repository. Wagento deploys a different feature to live and third party code is overwritten.

    Scenario #2 Third party developer installs something on live site that breaks lives site, then goes to bed. Client calls Wagento to tell them live site doesn’t work No one has any idea what was done and code is not in repository so code can not be tracked.

    Why do we care about any of this? The repository creates a real time audit trail of everything that has happened to your website. If there is ever a problem it can quickly be identified by the last submitted code and that code can be reverted or corrected. Once someone works outside the system the code is no longer valid. The integrity of the website is now in question.

    Why do we care about the integrity of the code? We have clients who every day are fulfilling 1000-3000 transitions and 10,000’s of products. If we don’t know what the state of the code is and how to resolve problems then we can not serve the client to the best of our abilities. In addition to integrity it can waste everyone time trying to figure out what a third party has done.

    Why do we use GIT?

  • Embrace Consumerization of IT and Stop Saying No

    One of the most important things you can do when dealing with the consumerization of IT in the enterprise is to train your staff to stop saying "no." Instead, IT professionals must seek to understand the problem the user has and seek a solution. That's the advice of Noah Broadwater, CTO of Sesame Workshop, the producer of Sesame Street.

    Posted by: By  on Thu, October 11, 2012

    Read Full Article

  • Unholycocktail

    TEST

1-10 of 13

Page:
  1. 1
  2. 2