archive-com.com » COM » I » INTEGRUMTECH.COM

Total: 312

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Savage Love: Not your average app - Integrum
    and Roy Van de Water had no idea what they were in for The Savage Love mobile application allows fans of the column by the same name to access Dan Savage s unique discussions from any platform You d never know what you d read or see each day said Roy It made the development process interesting to say the least Kyle and Stewart tested on an Android phone with development taking only two weeks Savage Love shows the power of mobile browsers said Roy Savage Love proves it s a viable medium for Android applications Additionally the sleek design of the application by Goldman Designs assisted in keeping development time short We were fortunate to work with a company that provided great design said Kyle The Savage Love application is currently in beta and will be available XXXX PREVIOUS A peek inside Retrospective NEXT Good to Great Step up to the mic Cancel reply Your email address will not be published Comment Name Email Website About the author Crew Subscribe to the blog Get inspired with an Agile Weekly Podcast Derek Clayton and Chris slowly remember what they were talking about Oh ya Culture Fit Including mono cultures hiring

    Original URL path: http://integrumtech.com/2011/01/savage-love-not-your-average-app/ (2016-04-26)
    Open archived version from archive


  • Valley Metro Improves Usability - Integrum
    notice updates to the interface to make it more user friendly with a redesign by IMP Designs This project is a chance to make the system more about the customers and userbase as well as correct any issues said Steve PREVIOUS Integrum joins Chandler 100 NEXT A peek inside Retrospective Step up to the mic Cancel reply Your email address will not be published Comment Name Email Website About the

    Original URL path: http://integrumtech.com/2010/11/valley-metro-improves-usability/ (2016-04-26)
    Open archived version from archive

  • Gangplank anchor becomes client - Integrum
    idea for Authority Labs at a Gangplank event in October 2008 as well as secured funding from Gangplank LLC for his venture Chase has seen his business grow over the last year and when it came to expand he looked inside the Gangplank community to Integrum Due to such tremendous growth and attracting large client deals Chase needed expand his core infrastructure to offer new web services and scalability for his clients Jade Meskill had already developed much of the infrastructure that allowed the site to achieve such rapid growth AuthorityLabs and Integrum have worked to design an easy SEO software that s simple enough for the small business but scalable enough for the enterprise Integrum and AuthorityLabs have also created features that make the software perfect for agencies A lot of the growth has to do with the simplicity of the design said Chase The fact that the system is flexible enough that an enterprise can pull insights out of the volume of data that they have PREVIOUS Windows Phone 7 NEXT Integrum joins Chandler 100 Step up to the mic Cancel reply Your email address will not be published Comment Name Email Website About the author Crew Subscribe

    Original URL path: http://integrumtech.com/2010/10/gangplank-anchor-becomes-client/ (2016-04-26)
    Open archived version from archive

  • Agile Lean Coffee - Integrum
    its south meeting in Gilbert Along with the great evening offerings there will now be a morning event in a different format We will use the Lean Coffee format that encourages discussion of many topics in a rapid fire and focused way Do you want to be better at what you do Are you using Agile or Lean and hungry for deeper conversation Need your questions answered or just want to talk about how you can get better or change your organization for the better Join us for Agile Lean Coffee We will be using a Lean Coffee format to collect ideas and have rapid fire discussion When Thursday August 30th 2012 7 00am Where Paradise Bakery 101 and Ray Road More Information https www facebook com events 351342351612145 PREVIOUS Episode 73 Less Everything with Steven Bristol NEXT Special Episode Agile Success with Woody Zuill Step up to the mic Cancel reply Your email address will not be published Comment Name Email Website About the author Crew Subscribe to the blog Get inspired with an Agile Weekly Podcast Derek Clayton and Chris slowly remember what they were talking about Oh ya Culture Fit Including mono cultures hiring diversity of ideas

    Original URL path: http://integrumtech.com/2012/08/agile-lean-coffee/ (2016-04-26)
    Open archived version from archive

  • Stair Step Burndown - Integrum
    however your iteration looks 1 Ruler 1 Sharpie 1 Green marker 1 Red marker Instructions Get the team s capacity by day Draw a horizontal line on each day of the sprint indicating how much of the team s capacity is left in the sprint Label each horizontal line with the number of hours left This makes it much easier to update the chart throughout the week What this does Here is an example of a regular straight line burndown chart Eveything looks great right The team fell behind at first but is starting to catch up and is now only an hour or two behind It would be totally reasonable to for the team to believe that they will make up those two hours and should have little problem hitting their commitment One thing the team has forgotten though is that two of their team members will be gone at a conference on Thursday and Friday The stair step burndown tells a completely different story Now we see that the team is actually 16 hours behind and the team only has 24 hours of capacity left in the entire sprint This realization while harsh is much better to have on Wednesday midway through the sprint than on Friday afternoon This way the team has the time to warn the Product Owner and figure out what needs to be removed from the sprint The Product Owner is able to use that advance warning to plan for the following iteration taking in to account that some of the work that was originally thought to be done this week is actually going to take up a sizable portion of next week as well In retrospect this is a very minor adjustment to the existing burndown chart There is something about burndown charts

    Original URL path: http://integrumtech.com/2013/06/stair-step-burndown/ (2016-04-26)
    Open archived version from archive

  • Interruption Balloons - Integrum
    balloon and start blowing it up while they explain the problem If they ask what you re doing explain that you re trying to track time spent not working on the iteration Blow up another balloon for every 15 minutes spent interrupted Blow up a balloon for every interruption Even if it is just 5 minutes blow up a balloon Most interruptions require you to context switch so even a 1 minute interruption will require several minutes to switch gears to deal with the interruption and another few to switch back Leave the balloons lying around the team space What this does By the end of the iteration it is not uncommon to have the bullpen so polluted with red balloons that it becomes difficult to freely walk around This highlights the devastating effect that a number of individual interruptions have on the iteration By adding up the total number of balloons and multiplying by 15 minutes the team can gain a pretty quick approximation of the actual time spent on all interruptions PREVIOUS One Hour Iterations NEXT Episode 111 Inspiring Personal Growth in Agile Teams One thought on Interruption Balloons michele mccarthy says September 16 2014 at 4 01

    Original URL path: http://integrumtech.com/2013/06/interruption-balloons/ (2016-04-26)
    Open archived version from archive

  • One Hour Iterations - Integrum
    Instructions First define a minimum set of features that the team can deliver in one hour The features must add value at the end of the hour They can not be dependent on future features to work Set and start a timer for 42 minutes Have the planning session for 10 minutes The Scrum Master should be very strict about maintaining a 10 minute timebox Have a quick standup We like to use the Check In Protocol Set a seperate recurring timer for 6 minutes Every 6 minutes fill in a box on the task card see Extreme Timeboxing 42 minutes in to the hour deploy if you haven t already You must ship within the first iteration and continue to ship every iteration after that Facilitate an 8 minute retrostpective Since time is so limited try to stick to a format that everyone can understand with minimal explanation Start Stop Keep works well for this Take a 10 minute mandatory break No programming allowed It helps to move around a bit and physically leave the development space Just make sure everyone is back on time because you can t afford to waste a minute Now that the product is live the Product Owner should show it to as many people as he she can This is where the on hand customers come in Try to collect as much feedback as you can before the next planning meeting The schedule looks like this 12 00 Planning Tasking 12 10 Standup 12 12 Timebox 1 12 18 Timebox 2 12 24 Timebox 3 12 30 Timebox 4 12 36 Timebox 5 12 42 Retrospective 12 50 Break What this does By releasing every hour the team starts to build a lot of confidence in their ability to ship As they gain

    Original URL path: http://integrumtech.com/2013/06/one-hour-iterations/ (2016-04-26)
    Open archived version from archive

  • Extreme Timeboxing - Integrum
    in one black box on the task card If the time elapsed exceeds the amount of time estimated for the task draw a red box instead Reset the timer and continue with the task When the pair is done with the task fill in the remaining time left on the original estimate in green boxes on the task Repeat until the sprint is done What This Does By marking the time spend on each task the pair gets immediate feedback on which tasks went over and which went under This makes it painfully obvious when a task goes way over the estimate because you ll see a wall of red boxes that can be spotted from across the room The team will be able to measure how much time they actually spent on the tasks by adding up all red and black boxes up at the end of the sprint It is not uncommon for a team to find that their capacity is actually far less than they thought it was Each time the timer goes off during the sprint the pair is essentially asked Did you work on this task for the last 15 minutes It becomes very difficult to mark a box if they know that they spent those 15 minutes talking to a manager looking at YouTube videos or being distracted in some other way You ll generally find that teams are actually pretty good at estimating tasks generally only deviating by one box on other side Be wary though because teams will generally perceive more red boxes than green boxes even if there are exactly the same amount of each Red boxing presents the pair with a great opportunity to ask for help Many teams that try this end up making a rule for themselves that

    Original URL path: http://integrumtech.com/2013/05/extreme-timeboxing/ (2016-04-26)
    Open archived version from archive



  •