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".
  • Story Workshops Explained - Integrum
    start the process then the actors directors and set designers make adjustments or even wholesale changes based off of the reality of the scene s already shot move this table over add more blood louder zombies or whatever is needed to fit the reality of the movie and how it has grown We treat our client software in much the same way We talk through the application at a high level with the client to really suss out the details of what they want their app to accomplish Then using our itterative methods we take those stories we write and use them as talking points to make the scene real move this button 10 pixels left make the logo bigger the user should be able to flow more like this through the screens etc Until you see the software movie pieces already built scenes already shot you won t know exactly what you want the next part to look like This gives our clients the best chance to build what they REALLY want in relation to the ever changing world around them PREVIOUS New Year New Site New Image NEXT This is how we do it Step up to the

    Original URL path: http://integrumtech.com/2009/02/story-workshops-explained/ (2016-04-26)
    Open archived version from archive


  • Episode #20 - What's Most Valuable in Agile? - Integrum
    we ve seen too on the flip side where we have seen projects where the projects are massive The immediate demands to build features or to go back and fix defects is so great that while we ve tried to implement a continuous integration solution it takes us six months or it takes six months and we re still not done It seems to me that even starting from no pairing experience at all getting people up to speed on pairing is much quicker than that I do think that depends a lot on the existing project and the existing situation Not in all situations is setting up continuous integration going to be so non trivial If you re doing a real simple app start off with continuous integration Why wouldn t you But with another app it might be a lot more difficult Chris Definitely right there That s one of those things where you try to pick the easiest thing that s currently a technical issue You try to pick that and you start to attack it If it is a huge build issue then that s the point where I would lay off and say Well do we pick where we can automatically deploy it to death Maybe we start there and we set up an auto deploy to that Maybe it doesn t run all the tests and everything else automatically but we start walking towards it That would be one of those instances where I would definitely look at it and go Well pairing does make sense here but let s work on this as a pair maybe and you can get that in there fast Or have people start having that discussion about What s going on What problems are we trying to work through Clayton Right Another thing about pairing too when we talk about culture is I bet there are a lot of places or companies that would be uncomfortable or teams who would be uncomfortable pairing where they re used to working alone by themselves with their headphones on whatever There s a lot of other places too where they want pairing where they feel like pairing is missing or they feel like they would be pairing if they were able to pair but they don t because they re supposed to be working alone I come from an experience where I used to not do any pairing and I really wanted to do pairing On the few chances where I was able to do pairing I felt like a total productivity increase It was awesome to be able to communicate with my teammate We got things done quick Also looking at that from that culture perspective too where people are needing and wanting pairing Roy I think something that s also like what Drew brings up as far as the siloing is that we have gone into companies before where everybody does work in their own cubicle with their headphones on and nobody actually communicates When you start pairing at the very least you start having those conversations of This is a pain in the ass The other guy goes Really I ve been thinking that too I just didn t want to say anything right You start recognizing some of the problems and realizing that you re not the only one who has them that it s not due to your ignorance or your incompetence These are legitimate problems that everybody s facing and then you can start to work together as a team I think for a lot of teams too it finally gives them an opportunity to almost meet their team members because they haven t been working with them at all Clayton What do you say to the proponents of a continuous integration system that would say it s like maybe a testing where you could make the argument that if you don t have automated builds that anyone on the team can run at any point in time if you re not doing that then there s no confidence in the system Maybe you ve developed all these fantastic features You did pair programming Everything s great and the team all loves the features But when it comes time to deploy them it s a total guessing game Everyone in the organization gets very concerned and it turns into a two day process of making sure everything went right Drew I can completely empathize with that I have definitely experienced that a ton in exactly that type of situation I ve also experienced where doing the deploy has been extremely strenuous even when you re using continuous integration although it s much less likely to be so I definitely agree that that s a really a bad situation to be in and it is something that should be addressed I just think it s the next thing on the list Clayton You think it s more important to have paired features than it is to have confidence in the build Drew I d say you gain a lot of confidence in what you re building when you know that you built it with somebody else Like if I build a particular feature I think Well I may have messed up or I may have been approaching this all wrong While that s still possible with a pair at least you re discussing it and thinking about it differently I find that it s much less likely that you ve done that Chris Also from the development side of this so we re talking a lot about the pairing and developers working talking and getting through this But in Scrum the idea is that we want to build a better team all the way around not just with the developers themselves but also with the product owners with the people that we re building software for That s one of the things I like about the

    Original URL path: http://integrumtech.com/2011/06/scrumcast-20-whats-most-valuable-in-agile/ (2016-04-26)
    Open archived version from archive

  • Episode #58 - Personal Kanban with Gerry Kirk - Integrum
    Running a Transparent Consultancy with Chris Sims 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 the blog Hungy for More

    Original URL path: http://integrumtech.com/2012/05/episode-58-personal-kanban-with-gerry-kirk/ (2016-04-26)
    Open archived version from archive

  • Special Episode : Greg Kirk Phoenix Scrum User's Group Sept 2011 - Integrum
    Experience Design with Agile Process 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 the blog Hungy for More Info Agile

    Original URL path: http://integrumtech.com/2011/10/greg-kirk-phoenix-scrum-users-group-sept-2011/ (2016-04-26)
    Open archived version from archive

  • New Year, New Site, New Image - Integrum
    a Good Thing NEXT Story Workshops Explained 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 with many extraordinary opportunities To accept the challenge is to lead the way to a new future made from embracing our humanity and engaging our spirit to succeed Subscribe to the blog

    Original URL path: http://integrumtech.com/2009/01/new-year-new-site-new-image/ (2016-04-26)
    Open archived version from archive

  • Episode #21 - Is It Responsible to Not Test? - Integrum
    without tests Is it OK to go 10 weeks without tests Is it OK to go 90 days without tests Is it OK to only have 10 percent coverage or only have the value items covered I mean there is a point and you could say the same thing even not on Lean Start ups When you re in large enterprises that have millions of lines of code with no test and you want to do new development and it s not reasonable to go back and write tests for every line of code that s already written at some point you have to make trade offs to say What s the acceptable amount of testing that is responsible That s a word we use a lot but we drop real quick when we get into our wars when it s all testing all the time no matter what We drop the whole like What s responsible Maybe we could talk about What are some of the things that we see that are responsible or maybe better what we see that is irresponsible Chris For me I really embrace the core idea that BDD a behavior driven development is less about test coverage and the percentage of testing but more as a technique to help me discover the problem I m trying to solve So when I approach it from that angle I m not really interested in necessarily ensuring that every single line of code is covered I m more concerned about Am I creating a quality design that is good enough to solve the problem that I m trying to solve There s a bare minimum level of test coverage that you can implement when you re going down that path that is going to cover you in 90 percent of cases especially as your software continues to grow and add new features You have some level of confidence that you re not completely destroying the application by changing a few things around So when I m testing in Rails I really like to do acceptance testing some more outside in testing I m coming in as a user and following the path and making sure that things are working the way I anticipate them but I can change around a lot of the implementation details behind the scenes without having to go back refactor all my tests and worry about this whole gigantic test suit There s a bare minimum level of coverage that you can get where the testing is pragmatic and simple but good enough for the time being It really comes down to risk How much risk are you willing to take and how much risk can the product or project that you re working on afford to take If you have a hundred thousand dollars for the start up and it s make it or break it you can take a lot of risk with your software because the bigger risk is that you don t deliver anything If you spend all your money and engineering time doing testing you re not going to get to market anyway and it was just a waste of time Derek On your thousand dollar example if you treat it as a prototype people readily acknowledge that you should build the prototype and throw it away If you can be responsible to do that you should also recognize that maybe doing a full testing is irresponsible because that s something you re going to throw away At the same time I m kind of torn because I know that when you get to a certain point I acknowledge that there are benefits that you get from say TDD that are like architectural decisions You get other benefits that are not really what you re specifically testing Those are harder to get and more people think that they understand those and get those than they do I could see a lot of people saying Well you know I do TDD because I have to test everything because we ve got all these great TDD benefits when maybe they re not really getting those and it s a prototype that they should be throwing away anyway Chris How many people do you think have the discipline to actually throw away that prototype Jade None Derek None laughter Jade To me where the argument comes in is what s that time frame I mean I would argue To me personally it s probably in the four to six week time frame so you can lie to yourself that it s kind of a prototype for four to six weeks Once you get beyond that sixth week if you think of it really in terms of technical debt like financial debt I might bootstrap a start up with credit cards and that becomes irresponsible to a certain dollar figure Is that dollar figure 50 000 Is it 100 000 Is it 200 000 I don t know it s going to be different for everybody It s kind of the same thing If you re doing an application without tests you re incurring a certain amount of technical debt or you re making it more difficult to pay down technical debt that you do occur At some point whatever that time frame is it s pretty damn short I want to say less than six weeks but it really depends on who you are but then you re just lying to yourself Chris How could you gauge that How could you find that limit that threshold between test all the effing time and no testing at all How do you as a team determine what that pain threshold is Jade For me after playing with a bunch of test frameworks lately and really pushing through most people feel that testing makes them slower When you re comfortable with your framework that s simply not true Testing often makes you faster not

    Original URL path: http://integrumtech.com/2011/07/scrumcast-21-is-it-responsible-to-not-test/ (2016-04-26)
    Open archived version from archive

  • Episode #57 - Performance Reviews with Kane Mar - Integrum
    some part of it Kane Yeah maybe ego absolutely Ego is probably a very big factor in that sort of decision making as well absolutely Derek In an environment in which you rate the team instead of individuals how do you choose individual pay How are people s salaries going to work Kane Everyone should have a based on individual pay to be honest because everyone is different We all have different skills and different skills are valued differently in the marketplace I have no qualm about individual pay and individual pay being different for every individual on the team That is a real reflection of the real world In that regard I don t have an issue with that at all Any incentives on top of that however need to be done on a team basis In other words if the team is successful in meeting their accomplishments whatever those accomplishments shall be they should be rewarded as a team rather than on an individual basis There should be some element of individual compensation but there should also be some element of team based compensation Derek How do you decide which individuals make what Like if you re going to have individual compensation how would I choose to pay one developer or one employee more than another Kane My favorite way of doing this is to make it totally open In other words to have compensation transparent I admit that s a totally radical for most organizations that is a totally radical suggestion However having said that if you make it totally transparent then the notice is on the individual to justify his or her salary Say if you have a developer that is making twice as much as a tester unless they can justify that then maybe they shouldn t be making twice as much Derek I ve seen that A couple of instances too where as we move into 21st century work we have to challenge what we consider compensation I have seen a lot of employees choose potentially more time off or more flexible schedules or various other forms of incentive or compensation that they prefer over pay They actually would take a lower pay to have a more flexible schedule or be able to work on product or projects that are more meaningful to their direction in life and we are just scratching the surface when we re talking about preference problems and the sense of incentive performance and compensation are all going to be in a pretty serious flux in the next decade or two as the market heats up for talented creative knowledgeable workers and the supply is not there for the demand I am curious as to see where it s going to go I guess are you seeing some weird things out there in the organizations you are working with Kane Absolutely It s not only things you have mentioned and those absolutely will be impacted but there are also things

    Original URL path: http://integrumtech.com/2012/04/episode-57-performance-reviews-with-kane-mar/ (2016-04-26)
    Open archived version from archive

  • Special Episode : Chris Scripca - Game Programming for Fun and Keeping Thousands of People Happy - Integrum
    September 15th and 16th of 2011 During the event we had the chance to be able to interview some of the attendees and talk to them about the Open Space that they had just facilitated Open Space Technology conferences are great events where the attendees get to create and completely control the content of the conference Enjoy this video as we talk to Chris Scripca about his Open Space on Game Programming for Fun and Keeping Thousands of People Happy For more information on this event or their sister event Agile Open Northern California check out the site at www agileopencalifornia com PREVIOUS Special Episode Ainsley Nies Agile Chartering NEXT Special Episode Greg Kirk Phoenix Scrum User s Group Sept 2011 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 the blog Hungy for More Info Agile Weekly is a quick way to stay up to date with the latest news

    Original URL path: http://integrumtech.com/2011/10/chris-scripca-game-programming-for-fun-and-keeping-thousands-of-people-happy/ (2016-04-26)
    Open archived version from archive



  •