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".
  • SQL Server, Rails 3, Ruby 1.9, oh my! - Integrum
    Ruby 1 9 oh my Jay Fajardo says June 2 2011 at 7 18 pm Well done fellas Reply Scott Henderson says June 3 2011 at 8 42 am Woohoo The Gordian Knot of the dev Nice job Reply Step up to the mic Cancel reply Your email address will not be published Comment Name Email Website About the author Jade Meskill Chief Revolutionary Officer The new normal presents us

    Original URL path: http://integrumtech.com/2011/06/sql-server-rails-3-ruby-1-9-oh-my/ (2016-04-26)
    Open archived version from archive

  • Episode #61 - Is the Process the Problem? - Integrum
    a problem Do you know what I mean Derek I think a process lets you know what challenges you face within a team or an organization I think the reason that waterfall has been universally shunned over or shown to be not so effective is it s feedback cycle is way too short It does have the ability to tell you that things are wrong and to deal with them However the time frames that that are in are generally in months or years as opposed to days or weeks I think when I look at why most agile processes do fairly well is because they re very iterative which means they ve got much much smaller feedback loops I would almost argue that a lot of teams I see doing scrum are really doing mini waterfall Their teams are still very siloed They re doing two or four week sprints In whole they have iteration zero and they have a hardening sprint They have all these smells but they are getting feedback in a much tighter loop than if they said Hey we re going to do this 12 month project and we re not really going to do a postmortem until month 12 Clayton Just to clarify I think you meant to say that they have a longer feedback cycle Derek Yes longer feedback cycle I m sorry Drew When people have resistance to part of the process like Oh we can t spend all this time planning or This standup is just getting in our way Why don t I just get my work done part of a lot of agile processes are ceremonies that may be uncomfortable for people who are trying them to start What are ways you guys think to overcome those type of awkwardness of starting a new ceremony that by their culture they ve never done before Roy I think a lot of it is providing value in those ceremonies I see way too many organizations institute a standup or a planning meeting They are pretty much dog and pony shows in the sense of they are there only because some scrum book or some scrum master or some coach told the team they need to do that but the teams get no inherent value out of them I think the key is getting the information out in the ceremony dealing with it reflecting on it and improving the ceremony every time Otherwise what s the point There s been several times I ve told teams Why do you even bother having a stand up because what you re doing is not valuable to yourselves or anyone around you Clayton Going back to the article about Don t just change the process when do you guys think it s OK to change a process How far does it matter to team maturity Or if you get to try it for a certain period of time how would you know now is the right time to change things and do something different even just as an experiment How would you know how far to go with that If you keep that for a longer period of time is it OK to change process How would you know that Drew One example that I have it s just maybe a change of not necessarily a process but a practice is we were trying to get our stories smaller We had a problem of having stories that were too big I remember during planning once we argued forever or discussed for a long time Should the stories be broken up or not At that point we decided OK Let s just put it into this sprint Let s not talk about it more We can move on and figure out if it was too big or not But I think sometimes because of a time constraint you can just move on and maybe just skip some of those things that maybe you know you should do but as a team you don t have consensus Derek I think it s all about data I would ask Why did the team think they needed to break the story down to a smaller story What behavior or what symptom or what data made you think Hey we should potentially break this down Drew In that experience I think it was more of just people saying Hey we should break this story or people saying Big stories are bad and smaller stories are good That was all the data that we were going off of Later on we actually learned that ourselves when we learn that Hey it s getting near the end of the sprint and we have no story signed off How can we fix that problem Derek To me it s all about data If you say Hey the problem is the data that s coming up is that we re not getting stories into pending until the end of the sprint we should change something Once you change something you should then be able to measure Once we did that change did the problem of not getting stories into pending until the end of the sprint go away If the answer s yes then that was probably a good process change or a potentially good process change If the answer s no then you say Hey that s not had anything to do with it let s either go back to what we were doing before or let s find what the real problem is Roy It sounds like in that type of situation you d want to be very careful to make only one change so that you know which change caused your measurable effect Doing a process swap like you had asked when is it appropriate It sounds like doing a whole process swap is very difficult because sure you can measure whether or not there was a successful change but you

    Original URL path: http://integrumtech.com/2012/05/episode-61-is-the-process-the-problem/ (2016-04-26)
    Open archived version from archive

  • Episode #96 - A Backlog of Topics - Integrum
    teams interacted with them Is that really fair to call that a working agreement Derek I think it s fair to make a working agreement on how that team reacts to other people interacting with them For example if I have a team that is constantly getting interrupted by crosstalk sure and we had a problem where some of our team members will give in to it and we ll go and help them out and hurt our sprint because of it I could totally see us having a working agreement within the team saying If we get interrupted you need to bring it up with the entire team you can t just make the call on your own to go and spend the time helping that stake holder The fact that it needs to be discussed with the entire team I think that s a totally fair working agreement That would affect how you interact with outside people Ray To me this is largely about how things are communicated If the three of us are all on a team and we agree that we all don t like interruptions we want to do xyz do little flags or do something that we re busy and if somebody comes in If we re going about our work we put our flag up and somebody comes in and I say I m sorry we re going to have to tell you in 15 minutes that we will deal with your problem but right now we need to stay focused on this then we have a working agreement What we re doing is signaling to somebody else We can t help you right now and if they question it We ve got this internal working agreement that we ve agreed up on this that would be really great when the three of us say We re going to have a working agreement that works like this and we re going to send it out to everyone in the company and say By the way when you work with us this is exactly what you re going to do and you re going to like it This is our new working agreement Us collectively that s bullshit The reason it s bullshit is because you didn t ask of the other people that are coming to interrupt you to say that When you interrupt us it really bothers us and we would like to come up with a way to do that how would it work best for you I don t think that the internal working agreement is a bad thing but if you go out and you sell it as This is how we re now doing business here s the memo read it and abide by it by law and then call it a shared working agreement among everybody that s bullshit If you say This is our working agreement that we ve agreed upon and we ask that you please respect that with us I think that s a little bit different Clayton Next up back log gardening Back log grooming Is this something that is avoided or people don t do enough and you do a certain workshop and generate a whole bunch of stories and you sit there and think you re just going to work on them Derek Grooming on back log is done in the middle of planning right While you re trying to give your team stories Clayton Typically by the book it s more done before hand where you re going through making sure things are prioritized and Derek So you re saying you shouldn t spend the first hand on planning or reorganizing everything Clayton That s probably a sign that you re not doing any kind of gardening right Ray That means you re Advil if you do that Derek That s true Clayton That s right At the drop of a hat you can reorganize everything Ray The reason I said gardening instead of grooming is when I look at grooming that s cutting the hair that s picking the nits out of the lice off of your head et cetera I think that that s how most people view backlog grooming which is most people have the problem of I ve got an enormous amount of crap or features that I want to deliver and most of my effort is trying to pull stuff out that they don t really want to do or to get more details to clean up and prettify and get it ready But I think that a lot of organizations on existing products they have a much different problem Their problem is one of we don t know what features to actually be adding We don t know how to talk to our customers We re just adding crap that doesn t matter so what happens is this is like Oh I m not really sure it s like Who called this last What were they pissed off about Let s throw that into the product instead of actually saying Hmm have we already plowed that field before and is it going to fallow if we keep planting on it What kind of vegetables do we think people are going to If you take more of the gardener s approach of Hey let s be strategic about what we re planting and the cycles of it I think it s a little bit deeper than just saying Hey we ve got more stuff in the backlog than we can see Let s trim the fat I think it s about really doing it is about trimming the fat but it is also about what you re planting what you re putting in all of that tending to it It s hard work Clayton Interesting I think from a perspective of if it s a new product you obviously you re going to have the

    Original URL path: http://integrumtech.com/2013/01/episode-96-a-backlog-of-topics/ (2016-04-26)
    Open archived version from archive

  • Episode #29 - "How Rigid is Scrum" - Integrum
    15 minute time box and the idea that each person was going to say their piece and move on didn t really let spontaneous knowledge sharing occur It was hard to have a 15 minute time box because the team would be going in a certain direction that they thought was a productive direction and they were having a good conversation and then the stand up had to be over Is that a misapplication of the stand up rules Or is that the purpose of the stand up to keep that stuff short and maybe not everyone benefits from that or not everyone agrees that they were going on the right path Roy I think that s a good example where the stand up rule should have applied It makes actually a lot of sense because there were certain members of the team having a great discussion that they felt was really productive What you don t know is either two or three or four or however many members of the team felt that this was wasting their time because it touched something that they had nothing to do with So I think that the 15 minute stand up would have allowed it to come up so everybody who s interested is aware of it or everybody who feels like they ve something to contribute is allowed to become part of that spontaneous interaction Then push it towards offline so you stick to your 15 minute time box and immediately after stand up continue the discussion Only with the people that want to be part of it and feel that they re able to contribute Drew Yes For example today with our team we had a spontaneous you could call it a meeting but it was more like a team conversation where we even pulled in more stakeholders and it was spontaneous Just because the scrum framework doesn t prescribe any spontaneous meetings per se it doesn t mean you can t do them Clayton asked if that was a misapplication Let s say if there was a legit purpose for extending a morning meeting longer that didn t follow within a stand up you can call that just another meeting I would say I do agree with your point Roy that if something is uncomfortable to have a rigid stand up it doesn t mean you shouldn t do it Try to do the uncomfortable parts of Scrum because it might expose issues You really have a great point there probably two or three of those people aren t getting anything out of that extended stand up Clayton Is there a chance that some people might confuse regardless of the agile methodology having a rigid system or the system being inflexible with something that s maybe exposing a bad behavior that they currently have on the team Something that they re used to doing that maybe they shouldn t be doing but it feels wrong not to do it

    Original URL path: http://integrumtech.com/2011/10/scrumcast-29-how-rigid-is-scrum/ (2016-04-26)
    Open archived version from archive

  • To Pair Program or Not Pair Program? Is that a Question? - Integrum
    positive factors higher than the negative factors and get the most productivity out of pair programming Standards Switch pairs regularly Switch drivers minimum every hour Small breaks more frequently Identify follow up information for later study Ask why Don t assume More distributed skill experience levels in pair selection Identify strengths to pair appropriate to the task at hand Identify weaknesses and address via books groups brownbags etc Have empathy for your pair Same person should be solo consistently if uneven numbers Odd man out should be doing research simpler tasks etc All unpaired code requires peer review You will be shot if you are without a pair for more than 1 hour Does your company pair program What are your restraining factors What are your driving factors Do you have standards guidelines written or informal on what is expected of programmers pairing PREVIOUS This is how we do it NEXT Rattlebox Jackie Testimonial 2 thoughts on To Pair Program or Not Pair Program Is that a Question RailsJobs In says February 26 2009 at 2 27 am I ve pair programmed before Specifically on bits that were complicated SQL cross tabulation queries for example Pair programming seems like quite an expensive luxury though Do you have any ideas on the ROI Do projects need to be a certain size before pair programming makes sense Incidentally looks like you have a really cool thing going at Integrum I m part of a group of six web freelancers who share office space and work It s so awesome to have geeks to hack with Looks like you have the same thing going on over there Reply Swedler says February 27 2009 at 12 06 am I was just commenting today that when I first started hanging around with the Integrum guys

    Original URL path: http://integrumtech.com/2009/02/to-pair-program-or-not-pair-program-is-that-a-question/ (2016-04-26)
    Open archived version from archive

  • Work Queues with Ruby using Redis (Resque) - Integrum
    key value store It is similar to memcached but the dataset is not volatile and values can be strings exactly like in memcached but also lists sets and ordered sets All these data types can be manipulated with atomic operations to push pop elements add remove elements perform server side union intersection difference between sets and so forth We have been using Redis quite a bit lately especially for iphone applications using Ruby on Rails backend systems It allows for greater scalability and better management for jobbing various processes Chris Wanstrath has put together a great redis backed library called resque He lays out our position pretty much spot on If you need a background job system do yourself a favor and check out Redis and Resque PREVIOUS Testing Multiple Versions of Internet Explorer NEXT Plot Points on Google Maps Painlessly With Ruby on Rails 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/2009/12/work-queues-with-ruby-using-redis-resque/ (2016-04-26)
    Open archived version from archive

  • How to Build a Ruby Gem - Integrum
    echoe gem 1 gem install echoe 2 touch hello world Rakefile 3 Add this code to hello world Rakefile require rubygems require rake require echoe Echoe new helloworld 0 0 1 do p p description A gem that illustrates how to build a gem p url http github com tombombadil hello world p author Chris Young p email beesucker nospam gmail com p ignore pattern tmp script p development dependencies end Now you can type rake T and get a bunch of tasks to help you manage your gem Create a manifest and gemspec A manifest just lists which files should be included in your gem and the gemspec has everything gem needs to manage versioning Echoe is partial to rubyforge but this didn t keep me from being able to use it with github 1 cd hello world 2 rake manifest 3 rake build gemspec Install your gem locally Let s make sure the gem works Running this command will install your gem on your computer so you can test it 1 rake install helloworld gemspec 2 start irb and test irb require rubygems require hello world HelloWorld say hello hello world It works Create a certificate We ll sign the gem with a self signed certificate For some reason the install moved the gemspec to the pkg directory Let s create it again 1 rake build gemspec 2 gem cert build youremail example com 3 Important Move the gem private key pem file to a secure location Update the gemspec with the certificate information Add this code to hello world gemspec use your own paths of course s signing key Volumes Secure Certificates gem private key pem s cert chain gem public cert pem Create the gem Now we re getting close This command will build the gem

    Original URL path: http://integrumtech.com/2010/01/how-to-build-a-ruby-gem/ (2016-04-26)
    Open archived version from archive

  • Episode #18 - Cost of Interruptions - Integrum
    Server Rails 3 Ruby 1 9 oh my NEXT Episode 19 Vision Join the conversation on Facebook Subscribe to the podcast Make your mark Get involved with the Agile Weekly Podcast by volunteering to be a guest recommending a speaker submitting a question or suggesting a topic Step up to the mic Build up your toolkit Learn new tips and tricks for empowering your team and transforming your business See

    Original URL path: http://integrumtech.com/2011/06/scrumcast-18-cost-of-interruptions/ (2016-04-26)
    Open archived version from archive



  •