Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 12 years ago.
Improve this question
I would like to know if Scrum methodologies can be used in electrical engineering development.
Scrum is just an iterative process, so it can be pretty much applied to whatever you like.
Yes.
I would like to know if Scrum methodologies can be used in electrical engineering development
Yes you can.You can do whatever you want as long as it benefits your organisation.
Pardon me if I am being presumptuous but are you really meaning to ask the below question?
I would like to know if Scrum methodologies would be beneficial in electrical engineering development?
Do you have the following? 1. a product or final product vision 2. a cross functional team who builds that product 3. product requirements which can be converted to bit sized shippable product user stories 4. and it is technically possible to work in as less as 2 weeks to 1 month iterations 5. a collocated team
If you have most of the above in your favor then it should work great for you, even if you don't, there is nothing that stops you from using Scrum in EE Development.
Can you use 'standard project management' methodologies in Electrical Engineering? If the answer is "yes", then you can use Scrum. Scrum is "a team-based framework to develop complex systems and products”. Scrum is not a 'silver bullet'; it will not magically resolve the issues the Team and Organization have. What it is is a 'silver mirror' that will reveal dysfunctions, and provide a framework and processes to help resolve them. The Scrum Alliance site has a wealth of information available; A good initialization might be http://agileanarchy.wordpress.com/2009/09/20/simple-scrum/
Many non-Software (and non-Engineering) groups are adopting Scrum.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
My team is making the transition to Scrum.
I am facing an issue I still not found on the various Scrum resources I've been studying: how to manage training?
I express myself by example:
my team has 4 developers, 2 of them know nothing about Test Driven Development
the project must be done using TDD
Should I create a backlog item "Study TDD" and use the first sprints so that the untrained developers learn TDD?
Or should I remove the developers from the project until they completed the training? Which is the best practice in this case?
Just send them to the training, and continue your sprints as normal. While they are in training they won't contribute to the velocity, the same as if they were sick or on vacation or just having a bad day. The velocity isn't a goal so much it's an indicator.
You can create a story for training if you want, but it isn't necessary. If creating the story helps, by all means do it. Don't do it just because you think you're supposed to. I've been on teams that liked to track non-product tasks, and teams that didn't. Do what your team decides to do.
In your question you wrote:
the project must be done using TDD
I hope that's because the team decided that, and it wasn't something that was decided for them. The whole point of scrum is to build a team that can make these decisions for themselves.
Well, I will answer YES.
you need to create back log
you need to define test cases and follow TDD
you need to do stand-up meetings and daily follow up
you need to define a team member as scrum master who have best understanding
further, you can engage an online training of transformation expert
Like, I know these guys regarding Agile/Scrum Transformation. http://sparklegenius.com/solutions/agile-transformation/
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
We are a team of 30 people, consisting of business managers, developers and software testers.
Our developers are on different projects that have partially different - partially the same products. They help each other where ever they can. As we are all in the same room this is quite easy.
Now I asked why we do not use Scrum.
One answer I got is: Because we are all in the same room and we are helping each other. This goes quite quick and so we might not need scrum. Some of our products are developed only by 2 people. So this would be kind of weird to have a standup meeting with only two of us. Also our colleagues come to work at different times and some are doing home office sometimes.
Is it true that in such a setting Scrum is not feasible or does not bring any value to the company?
Hope for your comments, ideas, thoughts...
Best,
Marc
As literature states (see here) ideal Teamsize is between 4-8. Smaller Teams should use XP.
My persional Opinion is, yes do scrum, even if you are a single developer!
Scrum is about your customer and team and about the way how they communicate. You always talk about your team. But even more is important how is the communication with the "customer/stakeholder", how is the project management done. If you have a customer involved than have a look at these processes if they are also that good as within your dev team. Most of the problems of softwaredevelopment lay here (requirements specifiction, customer expectations, being in budget/time...)
Some aspects you loose not using scrum (and therefore I would suggest using scrum even in a team of 2). You also have to not pick everything but only theparts you like
Backlog (what is planned in the next x weeks) and its documented!
Burndown Chart (where are we standing at the moment)
Continouus improvements (in Scrum you capture impediments, you reflect what was good and bad..)
Daily Scrum (makes even sense for a single person reflecting what I did and do the next day! and what problems happened.)
Most other apsects of scrum...
I am currently starting to implement/use all this for me as a single person/developer and I can only say it makes my work and me better as a programmer. And I am even saying this, being my own customer and PO (I develop my own products/business for me)! And even than it makes sense. The advantage is, that this is with scrum all extremely lightweight (no overhead).
The Scrum Guide suggests a team size of 3-9 people.
There is a reason for the lower limit. Teams smaller than 3 people have less interaction and may lack the skills to deliver a potentially releasable increment in a sprint. It can be a challenge to keep the Product Owner engaged when you have a very small team.
My personal experience is that 4 people is a more realistic lower limit due to the impact of holidays and other absences on a team.
It is also important that a Scrum team is consistent over time. One of the benefits of the Scrum approach is it lets us calculate the capacity of the team and this is complicated by frequently changing team members.
Team members working from home and having different core hours should not be a major problem when working with Scrum. This is common in a lot of Scrum teams and can be mitigated with careful synchronisation and the use of technologies such as messaging applications and voice/video conferencing.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
Recently, I am working on my course project, the topic is the creation of a new hybrid software process model by integrating Scrum and Team Software Process (TSP). Integration of these two models will be based on the SEMAT Essence Kernel Framework.
I am wondering:
Which steps should be followed for this integration (like
determination of the roles and artifacts in these two models)?
What should be the criteria to decide on good sides?
Thanks in advance!
The best way I think I can answer this question is by quoting the agile manifesto.
"Individuals and interactions over processes and tools"
Agile is about people, teamwork and craftsmanship. It's about involving the customer closely to figure out what really is needed - and delivering that, in small increments of working software. Agile is inspect and adapt, based on experimental delivery and the feedback and evidence that comes from that.
Trust yourself. Work closely together and you can do this. The best learning often comes from doing. :)
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I'm currently involved in a scrum project for a small organization.
Some events have led us to believe the organization doesn't understand their role in the scrum process. We've already gone as far as arguing about the size of the development team which, in my opinion, shouldn't be something for them to worry about (negative conclusion to this project has little to no impact on their end and large impact on us).
Learning the lingo as they go, they've asked us if they could see our backlog.
I don't have a ton of experience with scrum but is it wise to show it?
I fear we might get a lot of negative feedback because they don't understand the process all that well.
(Additional context: we are students and this situation is not covered by our classes, our teacher hasn't responded to our e-mails yet.)
Scrum is transparent. Everything the team does is open and visibile to all interested parties. Regular showcases are held to demonstrate completed work and both the sprint and project backlogs are public.
If you are following the Scrum framework then you will have a Product Owner who represents the business and is fully engaged with the team. It is the Product Owners responsibility to engage with stakeholders (i.e. other business users) to explain the contents of the product backlog.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
Is there a legitimate reason why the majority of society (beyond CS-educated persons) should know about the abstractions we become familiar with in CS/programming (such as data abstractions, computer systems abstractions, etc)? Or does it truly not really matter to anyone but programmers, scientists, and engineers?
There is absolutely no reason why the majority of society should know about CS concepts. This is not the way society works, IMO. To be honest, a much stronger case could be made why the majority of the people should know about first aid then about CS.
There are a lot of professions out there which are crucial to maintain the standard of living we have now. Computer science is one of them, I'll give you that, so are doctors, engineers, mechanics, teachers,...
The majority of the people already know how to use computers because it's useful to them. Just like you know how to live in your house, you probably don't know how to build one from the ground up.