Comments for Jason Little

Comment on 5 Big Takeaways from Lean Startup Machine Toronto by Jason Little

Jason Little — Fri, 03 Feb 2012 20:50:00 +0000

It was awesome! A community focused lean startup in the Sault would be amazing! I want to do one here too.

Comment on 5 Big Takeaways from Lean Startup Machine Toronto by Gerry Kirk

Gerry Kirk — Fri, 03 Feb 2012 19:13:00 +0000

Gee, wishing I had gone now, thanks for sharing. Makes we want to host a Lean Startup event here in the Sault. Some day…

Comment on 5 Big Takeaways from Lean Startup Machine Toronto by Thomasjeffreyandersontwin

Thomasjeffreyandersontwin — Wed, 01 Feb 2012 03:07:00 +0000

Jason,

Sounds like an amazing experience, I’m there next year…

Comment on People Create Your Culture by Jamie Dobson

Jamie Dobson — Tue, 24 Jan 2012 16:06:00 +0000

You said, “[this can be] an effective way to create awareness around an organization and it’s people to increase the odds of a successful change.” – I agree. This is what I’d call the radicalisation of a workforce.

Comment on Agile Software Development Sucks Ass by kc

kc — Fri, 09 Dec 2011 21:06:00 +0000

“Again, Agile focuses less on estimates and more on sizing and measurement. Size the stories, start sprinting and use your velocity to see how it’s going”

You are just playing with words. Which also happens to be one of the big problems with Agile – or any other management ‘flavor of the moment’. What, precisely is the difference between a time estimate and “sizing and measurement”. Why is stupid terminology like “stories” and “sprinting” and “use your velocity” needed to get a project done?

Comment on Agile Software Development Sucks Ass by kc

kc — Fri, 09 Dec 2011 21:06:00 +0000

“Again, Agile focuses less on estimates and more on sizing and measurement. Size the stories, start sprinting and use your velocity to see how it’s going”

Comment on Agile Software Development Sucks Ass by Unix

Unix — Tue, 22 Nov 2011 04:33:00 +0000

Working under the microscope has been part of the software engineering landscape for years. This is due to pointed headed bosses not valuing a software engineer the same way an electrical, mechanical or other type of engineer is valued. Scrum and agile are just trading the microscope for the colonoscopy scope. A long time ago someone figured out if you can write the user manual before writing the software you knew what your requirements are. You could develop your user interface as a prototype and get user feedback. People keep going to interviews and keep seeing the same crap – scrum, agile and no cubes. Everyone is writing little pieces of code outside of where it ultimately has to be integrated and tested. And these miserable people have to demo their code every two weeks. So instead of creating solutions to real problems they are creating solutions to looking good every two weeks. Software costs money and it’s too bad that companies can’t accept it. Many of us have moved on to better jobs in other industries where we are treated with dignity. Until doctors, and other engineers are having daily 8:30 AM kindergarten scrum meetings I’m happy doing other things in my life. It would be fine if the users want to keep creating stories and changing them, BUT someone is going to want a product delivered and the only thing that appears to be ready for delivery in scrum and agile is disjointed code fragments. Alan Holub said a long time ago that coding is only 10% of the software development lifecycle. Scrum or any magic can only save you a percentage of 10%. Uncovering more requirements sooner by prototyping the GUI using VB or other dialog box tool in real-time with users will allow you to see the design in the big picture and you spend less time in test which is 40% of the SDLC. “The sooner you star coding the longer the project will take.” It’s still true today.

Comment on You Don’t Need Agile … If… by Thoughts on Agile 2011 – Culture Matters | Jason Little

Thoughts on Agile 2011 – Culture Matters | Jason Little — Mon, 14 Nov 2011 16:02:20 +0000

[...] who was asking me how they could start using Agile, in particular Scrum, in their organization. You can read the details here and I can tell you that his department was one that “got it”. They are actually [...]

Comment on Culture, People and Systems Part II by Jason Little

Jason Little — Fri, 04 Nov 2011 15:32:00 +0000

Thanks Jim, I’m glad this was useful for you!

Comment on Culture, People and Systems Part II by Anonymous

Anonymous — Thu, 03 Nov 2011 21:25:00 +0000

Jason,
This post was very timely for me. My co-worker and I have recently been struggling to work together effectively. We both have the same values but little things keep coming up that make our interactions difficult. After reading this article, I thought about what his type is (ENTP) and what mine is (ISTP). This new perspective got me thinking about the fact that my co-worker does have a lot of great ideas. That awareness has led to my hearing those ideas now, where before I was too focused on the immediate task at hand and discarded them.
Thank you Jason.
Jim